AI writes the code now. It still has to get through your review.
Eightclientprojects.Threeseniors.Nothingstuck.
Every client project in one queue. An AI agent that picks up the volume tickets on your own runner and hands you a finished pull request. And every hour — human or agent — on the board of the client it belongs to.
- Hosted in Germany
- DPA in the standard contract
- Agent on your machine
- Nordwind Logistik12 · 3 · 2Agent PR waiting for review26/40 h
- Kessler & Partner7 · 2 · 018/30 h
- Vitalis Health9 · 1 · 382 % of budget · notify client41/50 h
- Brandt Industrie4 · 2 · 112/25 h
- Lohmann Retail15 · 4 · 1blocked for 2 days28/45 h
- Sander Mobility6 · 1 · 222/35 h
Your developers aren't the bottleneck. The two who know everything are.
Every ticket a junior can't finish alone ends up with a senior — as an explanation, as a question, as a review. Across eight parallel client projects that stops being a staffing question and becomes a queue: hiring makes it longer at first, because the new person has to go through those same two people. And the agents your developers already use don't relieve that point — they fill it faster.
Everything runs into the same two or three senior lanes. It piles up in front of them.
Some of it arrives as a finished pull request straight in the review queue. Same inflow, less waiting in front.
We're the agency we built this for.
At Coding 9, every client project runs in Spedy: its own board, its own monthly budget, its own client login. The agent picks up the volume tickets on our own runner, and we review and merge.
- Every client project on its own board, with its own monthly budget
- The coding agent runs on our own runner, with our own key
- Agent hours are approved by a human here before they count
- Client logins in every project — free and unlimited
"We built Spedy because we need it ourselves every day. Every client project sits on its own board with its own budget, the agent works on our runner, and the hour it books is approved by a human here. What you see on this page is what we actually run — it isn't a demo setup."
Your developers already have agents. What's missing is somewhere the work lands.
An agent in the terminal doesn't know which of your eight clients this is, which budget sits behind it, or who has to review the PR. It leaves no trace your client can see, and no hour on the project it worked on.
You paste the ticket, the client context and the docs into the window by hand.
It gets the ticket, the client context and the wiki without copy-paste.
The pull request sits on GitHub. There's no record of who's supposed to review it.
It reports the pull request back to the ticket, into your review queue.
After "changes requested" someone has to kick the agent off again. Same for a red pipeline.
It can keep working after "changes requested" without a new nudge, and fix red pipelines itself.
At month end, not one of its hours shows up on the client project.
Its hours land as a draft in your approval queue, on the right client's board.
- NORD-214Caching for the product list3.0 hvia MCPApproveReject
- VITA-88Form validation1.5 hvia MCPApproveReject
- LOHM-31Checkout test coverage2.25 hvia MCPApproveReject
Ticket in, pull request out. On your runner, with your key.
The ticket hits the trigger status and the job goes to your runner. It clones the repo, plans, implements, tests, commits and opens the pull request — which lands back on the ticket as a comment, and the status moves on.
So you don't hear it for the first time in the demo: you need Docker on a machine you control, and your own Anthropic key or your Claude subscription. Client code never leaves your building. Included on every plan — even Free.
- 01
The ticket gets an agent team
You assign an agent team to the ticket, or drag it into the trigger status. That's all — the job goes to your runner automatically.
Nordwind Logistik
NORD-214Caching for the product listReady for agent- Agent team #1
- Linked wiki: caching strategy
- Estimate 6 h
- 02
The runner works through the stages
Clone the repo, plan, implement, test, commit. All on your machine, in an isolated container, with no production secrets. The log streams live on the ticket.
Runner job #482self-hosted · isolated- Repo cloneddone
- Plan createddone
- Implementeddone
- Tests runningrunning
- 03
Pull request back on the ticket
The PR lands on the ticket as a comment and the status moves to review. An epic spreads its sub-tickets across a shared branch in waves — several sub-PRs run in parallel.
PR #143+127 −12opened by the agent · just now
Ready for agentIn reviewwaiting for your review
3.0 h tracked · waiting for approval
One board per client. One team across them. One login for the client.
Every client project gets its own board with its own budget, its own wiki and its own permissions — your team works across all of them, in one workload view: who's on track, who's blocked, what's sitting in review. The client gets a login that points at exactly their board and can neither delete tickets nor see internal comments. And that goes for everyone working on the client project — engineering, project management, design, account.
- Mira3 boards
- Jonas2 boardsblocked
- Leon4 boards
- Sina2 boards
Client logins are unlimited and free — they never count as paid users.
- Monthly budget
- 40 h
- Used
- 33 h
- Carryover from September
- +4 h
- Threshold alert
- 80 %
NORD-214estimate 6 h · tracked 9.5 h
At month end, the client's board shows what actually went in.
A monthly budget per client board, with a threshold alert — and with carryover: billable hours you haven't invoiced yet roll into the next period instead of disappearing at the edge of the calendar. Per ticket, the estimate sits next to the actual time. Billable or not is a field, not a memory, and can be flipped retroactively for a whole board. Agent time is listed separately and approved by a human before it shows up anywhere.
What Spedy gives you is hours — the amounts stay with your invoicing software.
Cancel Linear, Confluence and Toggl. Keep MOCO.
Spedy replaces the delivery side: tickets, wiki, time tracking on the ticket, PR status. It explicitly does not replace the invoicing side — your tracked time syncs across to MOCO, and quotes and invoices stay where your accounting already has them.
List prices per seat per month, without annual discount. As researched — check your own contracts.
Agent included · client logins free
And in the agency-software category: MOCO from €15, awork from €12, ZEP from €18 — without Git, without pull requests, without an agent.
€90 a month for ten people. Client logins are free.
Free is a single seat to look around — that isn't enough for an agency, and we'd rather say so up front than afterwards. Pro is €9 per person per month with unlimited users, the coding agent is included at no extra cost, and every client login is free.
Client logins unlimited and free.
At a DACH senior rate of €120 to €160 an hour, €90 a month is at most forty-five minutes.
All plans in detailMigrate one client project. Two weeks. Then you decide.
Create a board, import the Jira or YouTrack project with field and user mapping, run the first agent PR. Import works for Jira, YouTrack, GitLab and CSV; export any time, no lock-in.
Create one board
One client project, not all of them. Attach a budget, invite the client login — that costs nothing.
Import
Jira, YouTrack, GitLab or CSV, with field and user mapping. Statuses come along; comments and attachments with Jira and YouTrack.
Run the first agent PR
One volume ticket, one runner job, one pull request in your review queue. That's what you decide on.
What Spedy can't do
So there's no disappointment in the demo.
- No invoicing your clients — that stays with MOCO, Teamleader or your accounting.
- No hourly rates in the system. Spedy counts in hours, not in euros.
- No margin or utilisation reporting. We deliver the hours cleanly per client; the valuation happens in your invoicing software.
- Who migrates 2,000 tickets across eight client projects?
- You migrate exactly one first. The importer pulls Jira, YouTrack, GitLab or CSV projects including field and user mapping; the remaining clients only follow once the first board is running. If you like, we'll do the first import together on the call.
- We already use GitHub. Isn't this duplicated?
- No. The code stays in GitHub and Spedy hangs off the PR: tickets are linked to pull requests, the status moves along (open → in review → merged), and the agent opens its PRs in your repo. Spedy doesn't replace Git.
- What happens to our MOCO time?
- Time tracked in Spedy can be synced to MOCO per board. Quotes, invoices and hourly rates stay in MOCO — Spedy delivers the hours, cleanly split by client and by billable or not.
- Can we get back out?
- Yes. Time exports as CSV any time, the wiki fully as Markdown, tickets and comments via the REST API. There's no contract term beyond the month and no export you have to ask us for.
20 minutes, one real ticket from your backlog.
No slides. You bring a ticket from a live client project, we create the board, attach a budget, let the agent open the PR and show you where the hour ends up.
We take care of the infrastructure, you get back to the day-to-day. Need a feature, missing something? Let's talk — it becomes a ticket in our backlog.
Access currently opens off the waitlist — first come, first served. On the call you get yours right away.
You don't build software for clients?
For product teams building their own product, and for in-house dev teams with compliance requirements, we have separate pages — with different arguments.