Enterprise

Run Mech inside your own walls.

The chip, the rules, and the records all live on your hardware and your network. Deploy on-prem or air-gapped, prove every decision to your auditors, and ship humanoids your insurer will cover.

The stack

The chip, the rules, the proof.

Three layers ship together and run where you run. You bring the AI. Mechanical brings the safety.

01 / Mech-1

The safety core

The chip that gates the motors and clears each movement against your rules. Bring any model, and the rules stay the same.

02 / Mech Protocol

The control plane

Open software to set rules, assign roles, and watch every decision across the fleet.

03 / The seal

The proof

Certification a buyer, an insurer, and a regulator can verify on any unit.

Sovereignty

It runs where you run.

Mechanical stays inside your perimeter. Your network, your keys, your logs. Pick the footprint that fits your security posture.

01

On-prem core

The safety core on your own racks. Everything stays on your network.

02

Air-gapped

Runs fully offline. Rules, updates, and audit move on media you control.

03

"Mech Inside" module

The certified module on the platform you already buy.

04

Your own silicon

Run the core on your certified board. We seal it, you host it.

Built for the regulated edge

Safety you can prove.

Every line maps to evidence you can hand an auditor, an insurer, or a regulator.

ASIL-D silicon Formally verified Air-gap ready Tamper-evident seal On-device decisions Signed audit trail
The admin plane

See every decision.

The Mech console is one place for a fleet of humanoids. It shows what each robot planned, what Mech-1 cleared, and what it held. Replay any moment, and export the whole record.

  • [D]

    Decision log

    A timeline of every movement cleared and held, with the rule that applied and the state at the time.

  • [S]

    Sandboxed motion

    Each motion plan runs inside a bounded envelope, so one limb stays separate from the rest.

  • [K]

    Sealed identity

    Every robot carries a Sequence, a hardware-rooted identity that signs its own logs.

mech · fleet console FLEET · 312 Overview Decisions Rules Roles Export CLEARED · 24H98.4% UPTIME99.99% HELD · 24H1,408 LIVE DECISION LOG G1-0142 held force over limit12:04:31 G1-0067 cleared reach12:04:29 G1-0291 held speed in busy zone12:04:27 G1-0010 cleared walk12:04:25 stream to Splunk, S3, and syslogEXPORT
The Mech console. Live decisions across the fleet, signed and ready for your SIEM.
Traceability

Everything the robot does is on the record.

Decision log

Signed and append-only

Every movement cleared and held is written to a sealed log on the robot's own identity, then mirrored to your store.

Sandboxed

Bounded motion

Plans run inside hard limits on force, speed, and reach. Mech-1 enforces the envelope.

Vault

Encrypted by default

Keys, model weights, and operator data sit in an encrypted vault. Logs redact personal data before they leave the device.

Retention and SIEM

Keep what you need. Stream the rest.

Set retention windows per fleet and forward the live record to the tools your security team already runs. Configure it once in your rules, and it applies everywhere.

  • [30]

    Hot, 30 days

    Full-fidelity, instantly replayable decisions for active operations.

  • [1y]

    Warm, 1 year

    Queryable history for incident review and compliance reporting.

  • [7y]

    Cold, 7 years

    Sealed archive for liability and regulatory windows.

rules · retention hot30donline warm365dqueryable cold7ysealed forward to Splunk Datadog syslog status ● streaming · 312 robots · all delivered
Access control

Roles that match your org.

The people who write the rules are separate from the people who operate the fleet. Roles map to your org, and every privileged change is recorded and reversible.

  • [A]

    Administrators

    Write the rules. Every change is recorded, and weakening a safety rule needs two keys.

  • [O]

    Operators

    Run, pause, and teleop within the envelope the rules allow.

  • [R]

    Auditors

    Read the full record. Export, replay, and report.

roles AdminOper.Audit Edit rulesSet rolesOperate fleetOverride, two-keyRead decisionsExport audit ·· ·· ·· ½½· · ½ needs two-key approval
Forward deployed

Our engineers embed with your team.

We take a platform from moving to sealed, and we leave behind a system and the proof to underwrite it.

01

Assess

Map your platform, its hazards, and the envelope the robot should stay inside.

hazard model
02

Integrate

Wire Mech-1 onto the motors and bring up the admin plane.

Mech-1 live
03

Certify

Run the test suite, capture the proofs, and issue the seal.

sealed
04

Operate

Hand over the console, train the roles, and stay on as the fleet grows.

underwritable
Get started

Put Mech-1 on your robots.

Tell us what you are building. A safety engineer will walk you through deployment, certification, and earning the Mech seal.