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 handoff to your agents, is independent of it.

What do we need for our agents?

The agent you already use — Claude Code, Codex, Cursor or any other MCP client — and a personal access token from Spedy. Spedy runs no agents; yours run on your side, with your own key. 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.

Yes. Time as CSV, the wiki as Markdown, tickets and comments via the REST API — any time and without asking us.

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 your own AI agents connected via MCP. In one place, instead of spread across three subscriptions.

Request a demo How does Spedy fit us? ↓

Client boards6 active · October

open · in progress · in review · Hours against monthly budget

Nordwind Logistik12 · 3 · 2
26/40 h
Agent PR waiting for review
Kessler & Partner7 · 2 · 0
18/30 h
Vitalis Health9 · 1 · 3
41/50 h
82 % of budget · notify client
Brandt Industrie4 · 2 · 1
12/25 h
Lohmann Retail15 · 4 · 1
28/45 h
blocked for 2 days
Sander Mobility6 · 1 · 2
22/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.

Your agents, with Spedy as their context

One click opens the ticket in Claude Code, Codex or Cursor — with context, branch name and repo. The agent reads the wiki and knowledge base via MCP, books its time and opens the PR, which lands back on the ticket, linked. It runs on your side, with your own 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.
Handoff to Claude Code & co.
One click in the ticket, full context as the prompt, PR back on the ticket. Included on every plan.
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.

Request a demo See all plans →

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 handoff to your agents, is independent of it.
What do we need for our agents?: The agent you already use — Claude Code, Codex, Cursor or any other MCP client — and a personal access token from Spedy. Spedy runs no agents; yours run on your side, with your own key. 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.

Request a demo See pricing