Shared record
State, actions, and decisions across software and hardware.
open source
One
shared
history.
Software and hardware, in one place.
Gantry keeps the data, actions, and decisions behind every robot in one shared record.
ROBOTS BUILDING ROBOTS. scroll to explore
FIG. 01 / ONE SOURCE, MANY PATHS
01 / THE WORLD WE WANTROBOTS BUILDING ROBOTS
A world where
robots build robots.
Robots and agents see what work is needed. They define what a robot must do, find parts, build it, and keep improving the robots already at work.
They form the roles and knowledge each task needs, as people do.
02 / WHAT MAKES IT POSSIBLEGANTRY / SHARED HISTORY
One record.
Many paths.
Parallel work needs a shared account of what exists, who decided what, how far it has moved, and why the next step makes sense.
Independent review
Agents talk, challenge choices, and guide what happens next.
Connected work
Agents carry decisions into tools, digital twins, and real robots.
From sourcing and rule checks to testing and operation, results return to the same history and inform the next decision.
GET STARTEDGANTRY CLI / CODING AGENTS
Start with
your agent.
Paste this into any coding agent.
I want to use Gantry with this robotics project. Use the official repository: https://github.com/fourn9/gantry-oss. Read README.md, docs/AGENTS.md, and SECURITY.md first. Use a version that meets the minimum required by SECURITY.md. Check the supported prerequisites, then set up the local Gantry CLI and ledger as documented. Prepare a scoped agent identity request and MCP configuration for the agent app I am using. Keep the admin token private, do not activate agent access on my behalf, and keep the server local. Show me what you changed, how to verify it, and which owner-review steps I must complete next.