v0.1.0 · Phase 1 · Public draft Apache-2.0
A common language for the robot economy.
A six-year-old can describe what a robot should do. A roboticist needs three weeks to make the robot do it. URML is the shared, open vocabulary that closes the gap, written down before every vendor ships their own dialect.
End users See it run → Builders Read the spec Robot makers List a product starts a compliance review
SUBSTRATE-AGNOSTIC
Sits above ROS 2, PX4, OPC UA, and vendor SDKs.
REGULATOR-ALIGNED
Default policy maps to US federal robotics regulation.
OPEN FOREVER
Spec stays Apache-2.0. No vendor capture.
The compliance path
~14 days end-to-end
1
Apply
Submit org + product. One form.
2
Self-report conformance
Run the conformance suite on your CI.
3
Manifest review
Capability + provenance audited by the WG.
4
Policy alignment
NDAA §889 · FCC · EO 14307 cross-checked.
5
Listed
Appears in the public directory with badge.
Regulatory alignment
The default validator policy is mapped to current US federal robotics regulation.
NDAA §889 / FY26
Procurement restrictions
Covered-foreign-country components refused at validation, not at audit.
FCC Covered List
Effective 2025-12-23
DJI, Autel, and other listed entities flagged in the manifest pass.
EO 14307
Unleashing American Drone Dominance
Default profile aligns with the executive order's deployment posture.
ASRA
American Security Robotics Act
Tracking the bill. The policy file will update on enactment.
Non-US deployments can override the default with
urml validate --policy file.yaml, or
disable the compliance pass entirely with
--no-policy.
What compliance gets you
Discoverable, verifiable, federally-ready.
Verifiable badge
Embed on your product page. Links to a live, signed conformance report.
Learn more →Directory listing
Discoverable by procurement teams searching for URML-compatible robots.
Learn more →Federal readiness
Self-reported NDAA / FCC / EO 14307 alignment in one consistent format.
Learn more →How URML works
Five layers, five validation passes, one program.
ARCHITECTURE
Every program runs through five passes (args → caps → envelope → bindings → policy) before any actuator moves.
EXAMPLE · BRING ME THE RED MUG
VALIDATES ✓
# program.urml.yaml
sequence:
- move_to: { room: kitchen }
- detect: { object: red_mug, frame: kitchen }
- grasp: { target: $detected }
- move_to: { room: living_room }
- release: { surface: side_table }
# pass 1 ✓ argument typing
# pass 2 ✓ capability declared in manifest
# pass 3 ✓ inside safety envelope
# pass 4 ✓ variable bindings resolve
# pass 5 ✓ compliance policy (NDAA §889, FCC)
$ make demo-run
→ Executed (mock TurtleBot 4 · 18 actions)
20
intent primitives
5
validation passes
765
tests passing
124
conformance fixtures
380
RFCs filed
Compatible runtimes & partners
Self-reported, public, free. Add your organization.
Browse directory →urml-ros2-runtime
home · industrial
urml-px4-runtime
drone
urml-industrial-arm-runtime
industrial
urml-cobot-runtime
industrial
urml-legged-runtime
industrial
urml-humanoid-runtime
industrial
SCHUNK
DE
Ouster
US
SICK
DE
Festo
DE
Zivid
NO
Hokuyo
JP
Phase 1 · 14 reference runtimes + 15 compliant parts listed · 0 manufacturers. Yours could be next.
Start the application
Make your robot speak URML.
The compliance review is free, opt-in, and self-reported. Your manifest stays yours. Listing is permanent until you de-list.
Apply for compliance review →
Talk to the working group
REVIEWED WITHIN 14 DAYS · NO COST · NO MARK YET (PHASE 4)