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 PATHSFrom one shared record, many paths of work and knowledge can grow.
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.

01 / KEEP

Shared record

State, actions, and decisions across software and hardware.

02 / QUESTION

Independent review

Agents talk, challenge choices, and guide what happens next.

03 / ACT

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 project. Use the official repository: https://github.com/fourn9/gantry-oss. Read README.md, docs/AGENTS.md, and SECURITY.md first. Check prerequisites and install the latest release as documented. Identify my project and agent client, and clarify the goal and completion conditions. Use gantry connect with --prepare and the matching --client to show a plan covering files, test commands, permissions, expiry, and limits. Show me how to approve and activate it myself. Keep owner credentials private. After activation, help me enable the generated MCP entry and verify project status. Keep setup local, preserve existing client settings, and use Gantry's scoped tools for work within the approved plan.