Plotune Nexus / Local-first applianceHardware + software

The agent meets the bench.

Real hardware.
Controlled operations.

Nexus connects AI agents to physical engineering and test systems through MCP. Hardware interaction and first-write artifacts happen on the appliance; cloud services support routing, identity and export.

Check Your AI Readiness ↗

4 quick questions · about 30 seconds · no sign-up

See How It Connects →
NEXUS / hardware overviewPlotune Nexus appliance with a finned enclosure and physical connectors
Plotune-defined hardware. Pre-integrated software. Managed lifecycle.
01 / System architectureRequest, operation, evidence

One controlled surface.
A physical result.

Architecture / request → result
01 / MCPAI agent

Requests a bounded operation

02 / Local appliancePlotune Nexus

Applies access and execution controls

03 / CAN · UART · ROS 2 / DDSPhysical test system

Interfaces with connected equipment

Structured results & recorded evidence

Conceptual workflow. No hardware is connected.

Conceptual flow. Available operations depend on transport, connected hardware, access and configuration.

02 / Engineering interfacesCompatibility matrix ↗

Speak the language
of your system.

Use the supported transports on your bench, rig or vehicle. Check the documented native, container and scale-up tiers before choosing hardware.

Explore connectivity →
01
CAN / CAN FD
Linux CAN transports for bus interaction and capture.
02
UART
Serial interfaces, including RS-485 and modem-control lines.
03
XCP
CAN and Ethernet transports with different supported operations.
04
UDS / DoIP
Diagnostics through reachable network and CAN transports.
05
ROS 2 / DDS
Join an existing DDS domain, discover topics and record evidence.
03 / From requirement to evidenceA bounded workflow

Discover. Execute.
Record what happened.

  1. 01

    Inspect the system

    Discover the available interfaces and current state before requesting an operation.

  2. 02

    Run a bounded operation

    Use the relevant MCP tools and job controls within the configured access and execution limits.

  3. 03

    Keep the evidence

    Return status, metadata and retrieval paths for locally recorded logs, traces and artifacts.

04 / Read the engineering details

Know the boundary.

Local-first operation is documented alongside cloud dependencies, hardware compatibility and current constraints. Start with the architecture and security model.

Read the Nexus documentation →
05 / Rent or buyLaunch price

Rent it for a project.
Or keep it.

Monthly rental or one-time purchase, with full functionality either way. See the options and what they cost for your project.

Start with your test environment

Map Nexus
to your bench.

Not sure it fits yet? Tell us about your hardware, interfaces and first workflow.