Roadmap
What we are building.
And what we are not.
Our first value is showing the work, so the roadmap is public rather than something you extract from a sales call. Read it as a statement of intent — dated by quarter, ordered by conviction. Nothing on this page is a contractual commitment. Dates move, items get cut, and when they do we change the page rather than quietly delete the row.
The list
Shipped, building, next, later, undecided
Five buckets. The first one is the only one you can rely on today — everything under it is a plan, and plans are worth exactly what plans are usually worth.
Projects and the board
Connect git repositories, build a team of specialists per project, and file requests that are typed, prioritised, reorderable and archivable.
Project Manager planning
A request becomes a plain-English plan and a task graph with owners and depends_on dependencies. You approve it, edit it, or send it back.
Fourteen specialist roles
From Executive Director to Android Developer, each governed by an editable Markdown contract you can read and change.
Isolated worktrees and branches
Every task runs on its own branch in its own git worktree. Parallel work cannot collide, and an abandoned task is a deleted branch.
Dependency graphs
A task that depends on another waits for it. The graph is visible on the board rather than implied by task order.
Review gates
Flag any role as requiring human review and dependent work stops until a person approves it — at every autonomy level.
Three autonomy levels
Manual, Supervised and Autonomous. Start where nothing runs without you and move up when the plans stop surprising you.
SSH deployment targets
Define a host, a deploy path, a deploy command, a diagnostics command and a rollback command. Your server, your commands.
Health checks
A deployment run is not healthy until your health check says so. The output is kept with the run.
Automatic rollback
A failed health check restores the last commit known to be healthy, without waiting for anyone to wake up.
Production investigations
Failure opens an investigation. The agent reads logs and diagnostics at read-only access, writes a summary, and can open the follow-up request itself.
Live run streaming
Watch a task work as it happens — the commands it runs and the output it gets back, streamed rather than batched.
Design previews
Front-end tasks produce a shareable preview link, so people can look at the change before it merges.
Role contract editor
Tighten a role, loosen it, or write your own. Behaviour is a document, not a hidden prompt.
GitHub and GitLab native app
A first-class app rather than a git remote and a token. Richer checks, cleaner authorisation, fewer setup steps.
Slack notifications
Plans awaiting approval, review gates, failed health checks and opened investigations, delivered where your team already is.
Cost controls per project
Per-project budgets and clearer usage reporting, so a runaway project is visible before the invoice is.
Investigation write-access hardening
Tighter scoping and clearer audit around the moment an investigation is raised from read-only to write.
SSO (SAML)
Single sign-on through your identity provider. Not available today at any price — see the pricing page for the full list of what we are missing.
Audit log export
Export the record of who approved what, when, and what changed as a result — to a file you keep.
Scheduled and recurring requests
Dependency upgrades, weekly housekeeping and the maintenance nobody remembers, filed on a schedule.
Multi-region deployment targets
Roll one deployment run across several hosts in order, with the health check gating each step.
Public API v1
File requests, read runs and reports, and drive the board from your own systems. There is no public API today.
SOC 2 Type II
We hold no certification today and we will not imply one. When an audit is complete, the report will say so and this row will move.
Custom role marketplace
Share and install role contracts written by other teams, on the same editable Markdown the built-in roles use.
On-prem runner
Execute runs inside your own network. Today every run happens on our infrastructure against your repositories.
Uptime SLA
A contractual availability commitment with remedies attached. We do not offer one now. The status page reports observed uptime and promises nothing.
Enterprise tenancy
Dedicated tenancy and the procurement motion that goes with it. Until then, the Enterprise tier is a waitlist and says so.
Mobile app
Approve a plan and watch a deployment run from a phone. Useful, unproven, and easy to build badly.
Jira and Linear two-way sync
Mirror requests into the tracker your company already argues about. The hard part is deciding which side wins a conflict.
Terraform provider
Declare projects, teams and deployment targets as code. Waiting on the public API landing first.
Self-serve model keys
Bring your own model keys below the Business plan. Today that sits on Business only.
Influence
How this list actually changes
Roadmaps drift towards whoever shouts loudest. These are the three routes that reach us, in the order they carry weight.
How we decide
The six questions every item has to survive
We build for the stretched builder: the person who ships the product, runs the servers and carries the pager. These are the tests an idea has to pass before it gets a quarter.
Does it make a gate stronger?
Review, approval, health checks and rollback are the product. Work that hardens one of them starts ahead of work that adds a surface.
Who asked, and how often?
We count distinct teams, not messages. Four teams describing the same workflow independently beats forty upvotes on one thread.
Does it fit the mechanism?
Requests, tasks, runs, deployment targets, investigations. If a feature needs a new concept beside those, it usually needs a rethink.
Can we support it at 3am?
Anything that touches your production hosts has to be operable by a small team under pressure. If we cannot, we do not ship it.
What does it widen?
Every integration and every access grant enlarges the blast radius. The security engineer's view counts as a veto, not an opinion.
Can we describe it honestly?
If a feature only sounds good when described vaguely, it is not finished. Copy that survives the security page is the bar.
Questions
The awkward ones about roadmaps
Will you commit to a date?
No. The quarters here are our current best estimate and they move.
Nothing on this page forms part of a contract, an order form or a renewal, and no salesperson can convert it into one. If a purchase depends on a capability existing, buy the product as it is today and treat everything below Shipped as a bet you have not paid for.
Can I pay to have something prioritised?
No, on any plan. We do not sell roadmap position, and we would rather lose the deal than build a product shaped by whoever spent the most last quarter.
Paying customers do get heard more clearly, because they use the thing every day and their descriptions are better. That is influence earned through use, not through invoice.
What happens to items under Considering?
They stay genuinely undecided. Some get scheduled, some get closed, and some sit there for a year while we wait for enough teams to want them.
An item under Considering has no quarter attached because we have not decided to build it. When we do decide either way, we say so on this page rather than removing the row quietly.
How do I request something?
Post it in the feature requests channel on the community page, or write to us at our contact form if it is commercially sensitive.
Useful requests describe a workflow: what you are trying to do, what you do instead today, and what it costs you. We will tell you which bucket it landed in, including when the answer is no.
Something moved out of Now. Why did nobody say?
We rewrite this page every quarter and note what slipped. If an item moved and you were waiting on it, that is a failure of communication on our side — tell us and we will write to the people affected the next time it happens.
Is the roadmap the same as the changelog?
No. The changelog is what has already landed, with dates. This page is what has not. When something ships it moves from here to there, and the Shipped bucket above is a summary of the changelog rather than a second source of truth.
Missing something you need? Tell the community — we read every thread.
Argue with this roadmap
The list gets better when the people using the product push back on it. Join the community, post what you are stuck on, and turn up to office hours.
Monthly office hours · Feature requests read weekly · No paid prioritisation