A small, senior team
Engineers from developer tooling, distributed systems and interface design — people who have shipped IDEs, build systems and infrastructure that others depend on.
Company / why this exists
The tools didn't change. The job did.
Writing code stopped being the bottleneck. Deciding what should be written, checking what came back, and keeping a system coherent while several agents work on it at once — that's the job now. We're building the environment for that job.
01 / the bet
Delegation is a skill. Our tools should make you good at it.
We spent the last two years watching very good engineers get worse at their jobs in a very specific way: babysitting a single agent in a chat window, re-reading generated prose to find the three lines that mattered, and losing an afternoon when a run went wrong at step nine with no way back.
None of that is a model problem. It's an interface problem — the same one we solved for compilation with build systems, and for collaboration with version control. Agents need their equivalent: isolation so work can happen in parallel, review so output can be trusted, and history so mistakes can be undone.
Commanda is our answer. Not a chat window with a file tree bolted on — an environment designed from the premise that you'll be directing several capable, fallible workers at once, and that your judgement is the scarce resource worth optimising for.
02 / principles
Five commitments we're willing to be held to.
01
The developer stays in command
Automation that can't be inspected, corrected or reversed isn't leverage — it's a liability. Every agent action is visible, interruptible and undoable. No magic, no hidden state, no "trust us".
02
Your code and context are yours
Local-first by default. We don't need a copy of your repository to build a good product, so we don't take one. If we ever change what leaves your machine, it will be an explicit, opt-in choice.
03
No lock-in, at any layer
Model-agnostic, editor-agnostic, host-agnostic. Blueprints and skills are plain files in your repo; traces export as JSON; output is git commits. Leaving should cost you an afternoon, not a quarter.
04
Boring where it counts
Sandboxes, permissions, allowlists and audit logs aren't features we market — they're the floor. Autonomy is only useful when the blast radius is knowable in advance.
05
Honest about what's built
This site describes a product in development. Where something is planned rather than shipped, we say so. You'll always know what you're getting before you commit a team to it.
Distributed, deliberately
We work asynchronously across time zones, in writing, with our own product in the loop. If the workflow doesn't hold up for us daily, it doesn't ship.
Private beta, waves through 2026
Onboarding a handful of teams at a time so each gets real attention. General availability follows when the beta stops finding sharp edges.
03 / contact
Talk to us.
Early access, a demo for your team, enterprise requirements, press, or a strong opinion about what we've got wrong — it all reaches the same inbox, and a person reads every message.
hi@commanda.ai
- Early access
Tell us your stack and repo size. We'll say honestly whether the current build is ready for it.
- Enterprise
Self-hosting, SSO, procurement and security review — we'll send the documentation we have and be clear about what's still in progress.
- Press & partnerships
Integrations, MCP servers and model providers: we're actively looking for partners for the beta.
- Response time
Usually within one business day. Always from a human.
Ready when you are.
Free through the beta, onboarded personally, and shaped by the teams who join early.