About
About Gantry
A desktop AI workspace that keeps your keys, your data and your decisions on your own machine. Source-available, built in the open.
Why it exists
Chat clients, coding agents and integrations have mostly grown up as separate products, each with its own account, its own subscription and its own copy of your data on someone else's server. Gantry puts the three in one desktop window and makes the opposite bet: you bring the keys, the app runs where you are, and nothing about your work leaves your machine unless you send it.
That bet shapes everything else. Models are reached with your own API keys, so you pay the provider directly and switch freely. The agent works in folders you attach, shows every edit as a diff and every command with its output, and asks before it does anything risky, with four permission modes so the amount of asking fits the chat. Connectors follow the Model Context Protocol so the catalog can grow without the app growing, and none of them installs itself.
Where it stands
Gantry is being built from a written plan, in public, by a very small team. The order of work, roughly:
- Foundation. The app shell, local storage, encrypted keys, and chat with the first providers.
- The agent. Files, editor and shell, the activity feed, the permission engine and the guard model.
- Connectors. The MCP client, OAuth sign-in, the catalog, and the first third-party connectors.
- Projects, artifacts, skills and memory. The pieces that make a workspace rather than a chat window.
- Releases. Windows and Linux first, and this site's download buttons lighting up. macOS follows once there is a signed build to offer, and signed Windows installers after that.
Progress is visible in the repository and summarised in the changelog once releases start. Design decisions are written down in the plan documents next to the code, so the reasoning is as open as the source.
The licence
Gantry is released under the Functional Source License, FSL-1.1-ALv2. You can read, build, modify and share it, use it at work, and ship things you make with it. The one reserved use is offering Gantry itself as a competing product. Two years after each release, that release converts to Apache 2.0 with no strings at all.
Follow along
- The repository on GitHub: code, plan documents, issues and discussions.
- The changelog, with an RSS feed, for releases.
- The blog for the longer notes on how things were built and why.
- A connector request if the service you need is not in the catalog.