For product teams
One product, one board, one agent that picks up the volume tickets.
You build your own product, not client work. Tickets, wiki, pull requests and a coding agent on your own runner — in one place, instead of spread across three subscriptions.
- 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
What we hear
- Tickets in Linear, docs in Notion, time nowhere — and the agent in the terminal knows about none of it.
- The pile-up sits in front of review, not in front of implementation. The volume tickets stay put because nobody wants to touch them.
- Status drifts between the pull request and the ticket. What is on main is known only to whoever merged last.
- Public forms, releases and the roadmap hang off three more tools, all billed per seat.
How Spedy solves it
Concrete answers, no marketing promises.
Boards, wiki and PRs in one place
Tickets, roadmap, releases and the wiki live together — linked to your pull requests, with the status moving on merge. No subscription for docs, none for tickets, none for releases.
Coding agent on your runner
The ticket hits the trigger status and the runner clones, plans, implements, tests and opens the PR. Self-hosted via Docker, with your own Anthropic key. Your code never leaves your building.
Public forms and releases
Feature requests and bug reports come in through public forms straight as a ticket. Releases bundle your tickets — along with the linked pull requests that actually got merged.
MCP as a writing surface
Your assistant reads tickets and the wiki, sets statuses, comments and starts timers — over MCP, with three-tier authorisation. Not just reading, actually working.
What matters for you
Spedy does more than this. These are the parts that make the difference in your case.
Tickets, wiki, releases, roadmap
One tool instead of three subscriptions, with linked pull requests and a status that moves.
Coding agent included
On every plan, self-hosted via Docker, with your own key.
Public forms
Feature requests and bugs land straight on the board as tickets, with no tool in between.
MCP server
Read and write from Claude Code, the terminal or your IDE — with permissions.
Time tracking on the ticket
Estimate against actual, without a second tool. Useful even if you bill nobody.
GDPR, DPA, German hosting
EU hosting in Germany, DPA in the standard contract — in case your enterprise customer asks.
Our recommendation
Recommended: Pro — €9 per person per month
Free is a single seat. From the second person on you need a paid plan — for product teams we recommend Pro: unlimited users, coding agent at no extra cost. At eight people that is €72 a month, measured against a Linear plus a Notion subscription.
Frequently asked questions
- We're not an agency. Does this still fit?
- Yes, with one caveat: the commercial half — client boards, budgets with carryover, free client logins — is built for agencies and will simply sit idle for you. The rest, meaning tickets, wiki, PR linking, MCP and the coding agent, is independent of it.
- What do we need for the agent?
- Docker on a machine you control, and your own Anthropic key or your Claude subscription. The runner runs isolated, with no production secrets. Included on every plan.
- Does Spedy replace GitHub?
- No. The code stays in GitHub or GitLab and Spedy hangs off the pull request: tickets are linked, the status moves along, and the agent opens its PRs in your repo.
- Can we get back out?
- Yes. Time as CSV, the wiki as Markdown, tickets and comments via the REST API — any time and without asking us.
Are you something else?
One client project.Two weeks. Then you decide.
Create a board, import a live project, run the first agent PR. No rollout, no migrating eight clients at once.