In comes what you already have. Out goes what others need.
You move existing projects over with status and people mapping. Jira and GitHub Issues can stay in sync, time goes to MOCO, and for everything else there is a REST API and webhooks.
- GitHub App (your-agency)connected
- Jira · live sync NORD3 min ago
- MOCO · time2 pending
- YouTrack import KESScompleted
Move one project at a time.
You move Jira, YouTrack and GitLab Issues over per project: statuses and people are mapped, and an import can be cancelled and resumed after an interruption. For every other tool there is the CSV import.
- Jira and GitHub Issues
- One-time import or live sync. In live sync, Jira status, assignee and comments flow both ways; for GitHub Issues, state (open/closed) and comments go back.
- YouTrack, GitLab Issues, CSV
- One-time migration with mapping, no ongoing sync.
- Map statuses7 / 7
- Map people9 / 9
- Tickets imported1,284 / 2,016
- Log3 notes
MOCO for billing.
Logged time goes to MOCO as activities; time logged by agents only once a person has approved it. Edits and deletions follow, and the “billed” status comes back via webhook.
- Budget in the MOCO project
- Optionally with an hourly rate per project, to set the MOCO project budget from the agreed hours.
- Transfers in view
- Pending or failed transfers are listed with their reason. Stuck transfers are retried, and the billing status is reconciled every hour.
REST API, tokens, webhooks, MCP.
Every organization has its API under its own subdomain, with access via personal access token or OAuth 2.0. Outbound webhooks report ticket, claim, PR and pipeline events with a signature.
- Rate limits
- By default 300 requests per minute per person; above that the API answers with 429.
- OAuth apps and MCP
- Spedy is an OAuth server: your own applications and MCP clients sign in with a consent screen. For coding agents there is the MCP server.
- deploy-bot · NORD, KESS only · readexpires 31 Dec
- reporting · all projects · readno expiry
- claude-nordwind · no deletingagent
What it does not do
So there are no surprises in the demo.
- No Slack, Teams, calendar or accounting integrations apart from MOCO.
- Jira sync does not create Jira issues from Spedy and carries titles and descriptions only from Jira into Spedy, not back; GitHub Issues sync does not create issues.
- No direct import from Asana, Trello, Monday or ClickUp; the way in is the CSV import.
Frequently asked questions
- Do we have to move everything at once?
- No. Import per project; the other clients stay where they are until the first board runs. With Jira live sync both systems can run side by side for a while.
- Do comments and attachments come along?
- That depends on the source. With Jira and YouTrack, comments come along; in the demo call we go through your source specifically.
- Where is the API documentation?
- In the Spedy documentation, which is available to signed-in users. There is no public Swagger UI.
- Are there browser and IDE extensions?
- Yes. The Chrome extension turns a spot on a website into a ticket with a screenshot, and the JetBrains plugin shows tickets in the IDE and recognises ticket keys in code. Both sign in via OAuth.
Let us talk about how you work.
Spedy is only available through a demo call. Request a demo or book a slot directly.