Skip to content
All comparisons
Confluence alternative

Spedy as a Confluence alternative: team wiki right next to the tickets.

Spedy is a ticketing system with a team wiki for agencies and development teams that work for clients. Wiki spaces with folders and pages, linked to a project if you like, an editor that writes Markdown, versions per page and an MCP server through which your coding agents read and write the wiki. Pages are written in the Markdown editor or arrive as a Markdown ZIP in a space.

Confluence is the wiki and documentation tool made by Atlassian.

Wiki · Nordwind Logisticslinked to project NORD
  • Architecture / Caching strategyv7
  • Architecture / Deploymentv3
  • Operations / Staging accessv12
  • Client / Contactsv2
Client role: read
What Spedy brings

What Spedy brings for wiki and tickets.

In Spedy the documentation sits next to the tickets it describes; clients read the linked wiki, and coding agents read and write it via MCP.

Spaces, folders, three roles
A wiki space has folders and pages nested as deep as you need. Access is per space: admin, editor or reader, for people or whole teams. Clients of a project read the linked wiki by default; write access is granted explicitly.
Write like in a document, store as Markdown
The editor handles headings, lists, tables, code blocks and @-mentions, with a toggle to the Markdown source. Every change creates a version, and earlier states can be viewed and restored. A whole space exports as a Markdown ZIP with its folder structure.
Tickets right next to it
Every client project gets its own board with its own prefix and running numbers (NORD-214), Kanban or list, epics, subtickets and custom fields. A # in the editor searches tickets and wiki pages you can access and inserts a reference.
Coding agents via MCP
Spedy runs no agents. You bring Claude Code, Codex, Cursor or any other MCP client; it fetches ticket, wiki and knowledge base through the MCP server, stores what it solved and reports back to the ticket.
Moving

Moving to Spedy: Markdown for pages, CSV for tickets.

For pages there is no direct importer: if they exist as Markdown files, you import them as a ZIP into a space, folder structure included. Everything else you write anew in the Markdown editor. For tickets there is the CSV import, one project at a time. Code stays in GitHub, GitLab or Bitbucket.

Pages as a Markdown ZIP or in the editor
A Markdown ZIP imports into a wiki space with its folder structure. Whatever does not exist as Markdown is written anew in the editor, with help from your coding agent via MCP if you like.
Tickets via CSV
Tickets from other tools come in via the CSV import: a one-time migration with statuses and people mapped, no ongoing sync.
Code stays where it is
You connect GitHub, GitLab or Bitbucket to the Spedy project. Commits and pull requests land on the right ticket.
Import into space Nordwindnordwind-docs.zip
  • Folder structurekept
  • Pages as Markdown38 created
  • Accessadmin · editor · reader
  • Agents via MCPread and write
No direct importer for pages from other tools

When Spedy is not the right choice

So there are no surprises in the demo.

  • You need real-time co-editing, comments on wiki pages or page templates: Spedy has none of these.
  • You need per-page permissions or public share links: in Spedy, permissions exist only per space, and there are no public share links.
  • You need wiki search in the browser: in Spedy you find pages through folders and # references, and full wiki search is available only via MCP.

Frequently asked questions

How do our pages get in?
There is no direct importer for pages. If your pages exist as Markdown files, you import them as a ZIP into a space, folder structure included. Everything else you write anew in the Markdown editor, with help from your coding agent via MCP if you like.
Is the export a complete backup?
No. It contains every page of a space as Markdown with the folder structure, but no images or attachments. There is no PDF or Word export.
Can our coding agents use the wiki?
Yes. Spedy runs no agents, but any MCP client such as Claude Code, Codex or Cursor reads and writes the wiki through the MCP server, searches it and creates entries in the knowledge base.
Where is our data stored?
On Hetzner servers in German data centres, separated per organization. Content goes to no external AI provider. The DPA under Art. 28 GDPR is concluded separately with the contract; bring it up in the demo call.

Let us talk about how you work.

Spedy is only available through a demo call. Request a demo or book a slot directly.

Confluence alternative for team wiki and tickets | Spedy