A world where
robots build robots.

Robots and agents decide what is needed, build it, and keep it working. They learn, repair, and reuse—forming the roles and knowledge each task needs.

Gantry is the shared foundation: software and hardware data, actions, and decisions in one place, so agent teams can build on what came before.

EXPLORE THE DEMO ↗

Paste into your coding agent. Review the setup it prepares.

An abstract painted landscape: many streams join a river beneath an evening sky.
LEDGER / CREW

Two services.
One shared workspace.

Ledger connects data, changes, and decisions. Crew uses that history to move work forward. Review and guide both in Studio.

Gantry Ledger

The record behind
every decision.

Keep software and hardware changes, results, and reasons together. Review new work against that history to choose the next step.

Try a change review
Sample review
Gantry Crew

Your agent team.
Learning as it works.

Give your team a goal and scope. Its members work on their own, in parallel, and discuss changes together. They learn from results and take your direction.

Explore agent work

See the agents and the work each one owns.

Project activity map · Illustrative demo · Not live

Use Ledger or Crew on its own, or connect both through your project history.

GANTRY STUDIO

See the work.
Guide the next step.

Studio brings Ledger and Crew into view. Review changes, follow progress, and give your agents direction.

EXPLORE THE DEMO ↗

Interactive sample · No live agents

01

See how the project fits together.

Find the parts, software, and work behind a change.

02

Understand what changed.

Compare versions before choosing the next step.

03

Keep the reason with the work.

Discuss the exact part or code line in question.

Bring your tools into the work.

Connect selected records and changes to your project’s shared history.

CONNECTION GUIDE ↗

Design & CAD

  • Onshape
  • SOLIDWORKSExperimental
  • CATIA V5Experimental
  • CreoExperimental
  • SOLIDWORKS ElectricalExperimental
  • AltiumExperimental
  • Cadence AllegroExperimental

Code

  • GitHub
  • GitLab

Tasks

  • Jira
  • Linear

Docs & data

  • Notion
  • Confluence
  • Google Drive
  • SharePoint
  • Google Sheets
  • Excel

Communication

  • Slack

Each connector covers selected operations, not full sync. Cloud connections await live-account testing; desktop connections are experimental. See coverage and limits →

GET STARTED

Start with
your agent.

Copy the prompt into your coding agent. Tell it your project, goal, and tools. It will help you choose Ledger or Crew and prepare a setup plan for you to review.

VIEW FULL PROMPT
Help me choose and set up Gantry for this robotics project. Use the official repository: https://github.com/fourn9/gantry-oss. Read README.md, docs/SERVICE_SPLIT.md, docs/AGENTS.md, docs/BOT_DEVELOPMENT.md, docs/CREW_ORGANIZATION.md, and SECURITY.md. Ask whether I want Gantry Ledger, where I direct development with recorded evidence and review, or Gantry Crew, where a persistent agent team develops within my delegated scope. Do not set up both unless I ask. Check prerequisites and install Gantry as documented. Identify my project, tools, agent client, goal, and completion conditions. For external tools, read docs/EXTERNAL-INTEGRATIONS.md, docs/EXTERNAL-WRITES.md, and docs/NATIVE-DESKTOP.md. Check the current connection route and limits for each tool I use, distinguish experimental support, and prepare the smallest useful first capture. Keep service credentials out of chat and configuration files; guide me to set them locally. Do not change external records without my approval. For Ledger, prepare a scoped local connection with gantry-ledger connect PROJECT_PATH --client CLIENT --prepare, using the actual path and supported client name. For Crew, follow its onboarding docs and show me the proposed roles, permissions, tools, runtime, and inference use before activation. Keep owner credentials private and preserve existing client settings. Leave activation, worker startup, and paid inference to my approval. Show me what will change and how to verify it.