FONTA ROBOTICS
Read the memo← Back
NORAMOTION INFRA · A FONTA ROBOTICS STUDIO COMPANY

The deterministic layer under robot foundation models.

Characterized joint modules, a 1 kHz motion domain controller, and the measurements that put both inside your simulator. You keep the model. Nora owns everything below the joint-level contract.

Become a design partner → Read the memo
DESIGN PARTNERS ONLY · 2026
01 · THE PROBLEM

Model companies are being dragged into hardware they never wanted to own.

The stack has split into brains and bodies. The brain companies run on other people's hardware, and their options are whole robots they re-characterize by hand, or bare components with no firmware, no measurements and no safety chain.

Autos solved this decades ago with the Tier-1: a supplier who designs the deterministic hardware under the software stack, stands behind it, and never touches the stack. Nora is that Tier-1 for the motion domain of robots.

02 · THE PRODUCT

Three parts, one contract.

MODULES
Joint modules that are the same joint, every unit, every revision

Motor, reducer, encoder and drive with Nora firmware: FOC and torque loops, safe torque off in the drive, a per-unit conformance record that ships with every module. Shenzhen and Suzhou supply, U.S. counterparty.

CONTROLLER
The box that runs your low-level policy deterministically

1 kHz executor with verified timing bounds, EtherCAT master, IMU and F/T with hardware timestamps, and an independent safety MCU carrying the functions a learned policy cannot.

MEASUREMENTS
Your body inside your training distribution

Per-joint dynamics measured on a rig, exported as Isaac Lab / MuJoCo assets validated against real trajectories. Deployed fleets re-identify themselves and flag drift.

CONTRACT V1 · THE LINE NORA NEVER CROSSES
Your policy sends joint targets and gains at 50 Hz. Nora returns state at 1 kHz. Everything above the line is yours; everything below is delivered characterized, versioned and safety-floored.
↓ q, dq, kp, kd, τ_ff @ 50 Hz
↑ q, dq, τ, temp, t_stamp @ 1 kHz
03 · SPECIFICATIONS

Preliminary. Final numbers ship with design-partner units.

Motion domain controller
Control loop1 kHz · verified timing bounds
Policy interface50 Hz joint targets + gains · 3 ms p99
BusEtherCAT master
SensingIMU · F/T · hardware timestamps
SafetyIndependent MCU · STO · protective stop · envelopes · fall handling
StandardsISO 13849 / 10218 patterns · tracking ISO 25785-1
Locomotion (optional)Delivered WBC + reflex layer, frozen and verified
Joint modules
IntegrationMotor · reducer · encoder · drive
Drive firmwareFOC · torque loop · STO in drive
CharacterizationTorque–speed · friction · backlash · delay · thermal · encoder noise
Per-unit recordEnd-of-line conformance, ships with every module
Sim assetsIsaac Lab · MuJoCo · validated against real trajectories
SupplyShenzhen / Suzhou · U.S. counterparty · path to U.S. integration
Torque classesAnnounced with design-partner units
04 · WHO IT IS FOR
Model-first labs

You train the policy and want a body that stays in-distribution across units and revisions without a firmware team.

Robotics companies going mobile

You started on arms and are adding wheels or legs. Locomotion arrives as a delivered capability under your policy.

Teams that need a U.S. counterparty

Asian sourcing with a U.S. entity and a path to U.S. integration, for deployments on both sides of the FCC line.

DESIGN PARTNERS · LIMITED

Nora is taking a small number of design partners for the first controller and module generation.

Become a design partner → Read the memo