For people running more than one thing
Every project moving. One inbox.
Your SaaS, your side project, the tool you keep meaning to open-source — each in its own workspace with its own repos, all building at once. ampm shares your agents fairly across them and brings every decision into one queue, so switching projects stops costing you an afternoon.
A kanban board with four lanes — Ideating, Planning, Building and Shipping — carrying tasks from a fresh idea through to a pull request waiting for review.
Have a poke around
Three projects, one board, one inbox
Invented data, real mechanics. One card per repo, building side by side. Approve a plan for one project and answer a question for another without switching anything.
Scroll a little further to load the demo
The board
Every piece of work, at the exact stage it's in. Positions aren't decoration — a card's column IS its state.
The inbox
One queue of everything blocked on you, each ask carrying the plan, the diff and the transcript behind it.
Activity
Who's working right now, on what, and what each run cost — live, with every finished run still on the record.
Engineer from anywhere
Every project, in your pocket
Three projects, one inbox, one phone. Answer whatever is waiting, wherever you are, and every project keeps moving.
From a beach chair
Scroll a little further to load the demo
Built for a portfolio
Context-switching is the job ampm takes off you
A workspace per project
Each project keeps its own repos, rules and backlog, isolated by construction. Nothing from one leaks into another.
Fair share of your agents
Work is scheduled across workspaces, so one busy project can't starve the others of your subscription.
One queue for every decision
Every project's plans, questions and merges arrive in one inbox, labeled with where they came from.
Pick up exactly where it was
Every task carries its plan, history and transcripts, so coming back to a project after two weeks takes a minute, not a morning.
The inbox
Nothing merges unless you want it to.
The decisions that matter — the plan before anyone writes code, the call only you can make, the merge into your main branch — wait for your yes. Not because the agents are asked politely to stop: the board simply has no way past them without an answer. Hand off the ones you trust it with; keep the rest.
Every ask arrives in one queue with its receipts attached: the plan, the diff, the PR, the full transcript of what the agent actually did. Approve it, send it back with a reason the crew has to answer, or just reply to the question. Then close the laptop again.
- planplan · diff · transcript
Is this the right approach before anyone writes code?
- questionplan · diff · transcript
Keep the old endpoint alive for a release, or cut over now?
- mergeplan · diff · transcript
Does this change go into your main branch?
Questions
Are projects kept separate?
Yes. Each project lives in its own workspace with its own repos, rules and backlog, isolated by construction.
Will one busy project starve the others?
No. Work is scheduled fairly across workspaces, so every project keeps moving.
Which coding agents does ampm work with?
Claude Code and Codex. ampm runs them on the subscription you already pay for — no API keys and no second bill for tokens — and when one account hits its usage limit, work moves to a backup account without losing anything.
Does ampm merge code on its own?
Nothing merges unless you want it to. Plans, questions and merges wait in your inbox with the plan, diff, pull request and full transcript attached, and you decide which decisions to keep and which to hand off.
Where does the code run, and is my repo safe?
Every task runs in an isolated sandbox on its own worktree, on workers you choose — your laptop, a server you own, or a cloud machine — and can only push to a branch. The output is always a pull request into your repo.
How is this different from chatting with a coding agent?
A chat forgets everything when you close the tab and needs you watching it. ampm keeps every task in a database with its plan and history, runs a real process — plan, implement, test, review, merge — and only asks you when a decision is actually yours.
Can one workspace cover several repos?
Yes. Add the repos agents should change, and add more as read-only context — a design system, an API they call, product docs — so their work matches what's around it. One change can span several repos as one piece of work.
How do I get access?
Join the wait list with Google or GitHub. We're letting people in a few at a time, in the order they joined, and we'll email you when it's your turn.
Early access
Keep every project moving
We're letting people in a few at a time. Join the wait list with Google or GitHub and we'll email you when it's your turn. Run it on our cloud or on infrastructure you control — your repos, your subscriptions, workers on machines you choose.