# Real hardware.Controlled operations.

Plotune Nexus / Local-first appliance  Hardware + software

The agent meets the bench.



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 ↗](https://www.plotune.net/ai-readiness?entry_source=direct)

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

[See How It Connects →](https://www.plotune.net/nexus/connectivity)

NEXUS / hardware overview  Plotune Nexus appliance with a finned enclosure and physical connectors 

Plotune-defined hardware. Pre-integrated software. Managed lifecycle.

01 / System architecture  Request, operation, evidence

## One controlled surface.A physical result.

Architecture / request → result

01 / MCP  AI agent 

Requests a bounded operation

02 / Local appliance  Plotune Nexus 

Applies access and execution controls

03 / CAN · UART · ROS 2 / DDS  Physical 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 interfaces [Compatibility matrix ↗](https://www.plotune.net/docs/nexus/hardware-compatibility)

## Speak the languageof 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 →](https://www.plotune.net/nexus/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 evidence  A bounded workflow

## Discover. Execute.Record what happened.

- 01 

### Inspect the system

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

- 02 

### Run a bounded operation

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

- 03 

### Keep the evidence

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

[CAN / ECU testing ↗](https://www.plotune.net/solutions/can-ecu-testing)[ROS 2 / DDS testing ↗](https://www.plotune.net/solutions/ros2-dds-testing)[Stream integration ↗](https://www.plotune.net/nexus/stream)[View Use Cases ↗](https://www.plotune.net/nexus/use-cases)

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 →](https://www.plotune.net/docs/nexus)

[Security model ↗](https://www.plotune.net/docs/nexus/security-model)[Data handling ↗](https://www.plotune.net/docs/nexus/data-handling)[Protocols ↗](https://www.plotune.net/docs/nexus/protocols)

05 / Rent or buy  Launch 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.

[See rent & buy options ↗](https://www.plotune.net/nexus/pricing?entry_source=direct&from=nexus_pricing_band)

Start with your test environment

## Map Nexusto your bench.

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

[Get Your Integration Plan ↗](https://www.plotune.net/contact?entry_source=direct)[View Use Cases →](https://www.plotune.net/nexus/use-cases)

Source: https://www.plotune.net/nexus