Specivo

Your team's knowledge,
finally findable.

Issues, wiki, documents, and attachments — connected in one searchable knowledge graph, for your team and your AI agents.

  • Partial reads & edits — fewer agent tokens
  • Runs fully air-gapped
  • AGPL open source
See the live demo Self-host in 15 minutes
New · AI usage & spend

See where your AI budget actually goes.

Spend per person and per feature, collected automatically from Claude Code, Codex, Gemini CLI and OpenCode. Self-hosted, on your own server.

Explore AI usage tracking
Demo data: ACME Waste & Recycling (illustrative)

Where knowledge comes together.

A full tracker, a versioned wiki, hybrid search, and flexible metadata — one connected workspace for your team and your agents.

Specivo kanban board with New, In Progress, Resolved and Feedback columns; issue cards show refs like ACME-42, tracker types (Feature, Bug, Task), priority dots and assignee avatars.
Tracking

Issues & tracking

A full issue tracker — types, statuses, priorities, assignees, subtasks, and dependencies between issues. Plan with sprints, see the whole release on a roadmap, and switch between list and board views.

A Specivo team wiki — a Markdown page rendered with the page hierarchy in the sidebar, an on-this-page outline, and version history controls.
Knowledge

Team wiki

A versioned Markdown wiki with full history and one-click revert, page hierarchy, and cross-links straight to issues. Knowledge that outlives the people who wrote it.

Specivo hybrid search results page with a Hybrid/Keyword toggle and type filters for Issues, Wiki, Comments and Attachments; results show titles, project chips and matching snippets.
Search

Hybrid search

Keyword and semantic search together, across issues, wiki, comments, and attachments. It finds work by meaning, not just exact words — search “login flow” and it surfaces the page that says “auth sequence.”

An issue in Specivo showing typed metadata fields such as story points, git branch and severity attached alongside the standard issue details.
Metadata

Flexible metadata

Typed metadata schemas that hold whatever your team needs — story points, git branches, severity, content status — defined per project or per issue type. More flexible than rigid custom fields, without the bolt-on feel.

Coming from Asana, Monday, or Jira?

Here's why teams move their work into Specivo.

Self-hosted — own your data

Runs on your servers, even fully air-gapped. Nothing leaves your network.

No per-seat pricing

Add your whole team and your AI agents. You're not billed per user.

Open source (AGPL)

Inspect it, extend it, fork it. No lock-in and no black boxes.

Built for AI agents

A built-in MCP server lets Claude Code, Codex, and others work the same issues and wiki as your team — reading a single wiki section or updating one field instead of the whole page. Fewer tokens, and every action is audited.

One tool, not five

Tracker, wiki, search, and docs in one place — instead of stitching Asana, Confluence, and a search add-on together.

Everything's connected & searchable

Issues, wiki, comments, and attachments link together — and all of it is found by one hybrid search.

Migrations

Switch tools. Keep your history.

A migration tool exports your old tracker into an open import bundle. Specivo checks it, rehearses it and loads it — issues with their full history, sprints, wiki pages, attachments, people and logged time.

Available

Jira

Jira Cloud or Jira Data Center. Issues with comments and change history, sprints, custom fields, labels, attachments, work logs and users.

Read the guide →
Available

Redmine

Projects and members, issues with full history, relations and watchers, custom fields, wiki revisions, groups, attachments and time entries.

Read the guide ↗
Available

Request Tracker

RT 4.4, 5.0 and 6.0. Queues and tickets with correspondence, comments and history, attachments, time worked, links, custom fields and Articles.

Read the guide →
On the roadmap

Asana & more

Asana and other tools are next. The bundle format is open, so any tool — or your own script — can feed Specivo.

  • Validate before loading
  • Dry-run rehearsal
  • Catch up just before you switch
  • Big sites in parts
  • Report of anything left behind

All migration tools →

Built for humans and AI agents.

Most tools are built for humans. Some are built for AI. Specivo is built for both.

AI agents read the same wiki, update the same issues, search the same knowledge base. Every action is tracked — who did what, human or AI, with full context. When you need to know what happened, you don't ask. You search.

Works with your AI tools.

Specivo ships with a built-in MCP server. Tested with Claude Code and Codex. Works with any tool that supports the MCP protocol.

One config line, and the agent stops guessing and starts looking things up.

// Add to your AI tool's MCP config:
{
  "mcpServers": {
    "specivo": {
      "url": "http://localhost:8000/mcp",
      "apiKey": "spv_your_key_here"
    }
  }
}
Claude Code Codex + any MCP client

AI is optional. Always.

Specivo works perfectly without AI. When you're ready, enable it with one toggle—using a free local model or your own API key. Your choice.

Local

Ollama

Free. Air-gapped. No internet needed.

BYOK

Your API Key

Your OpenAI/Anthropic key. Your cost. Your data.

Single sign-on

Sign in with the identity provider you already run.

Specivo speaks OpenID Connect. Connect Keycloak, authentik, Microsoft Entra ID or any OIDC provider — several at once if your teams need them.

  • Accounts created on first sign-in, or linked to existing ones
  • Provider groups mapped to Specivo groups and the admin role
  • Required groups and an email-domain allowlist per provider
  • Signing out at the provider ends the Specivo session too
  • Every sign-in, link and group change in the audit log

Your data. Your server.

No per-seat pricing. No user limits. Your team of 3 or 3,000 — same cost: zero.

AGPL licensed. No cloud dependencies. Your infrastructure, your rules.

Self-host in 15 minutes Read the docs

From the Blog

View all →
October 2026

Specivo 0.12.0: repository integrations, webhooks, SSO offboarding and SCIM

Specivo 0.12.0 links commits, branches and pull requests from GitHub, GitLab, Gitea and Forgejo to issues, sends outgoing webhooks, cuts off people disabled at the identity provider, adds SCIM, Mermaid diagrams, a working timer and a Chinese user guide.

Read article →
October 2026

Specivo 0.11.0: migration tools, import bundles and tighter access checks

Specivo 0.11.0 moves migrations into import bundles and standalone tools for Jira and Redmine, and tightens access checks and issue history.

Read article →

Articles

View all →
Jira Data Center Is Ending: A Self-Hosted Jira Alternative

Jira Data Center Is Ending: A Self-Hosted Jira Alternative

Jira Data Center reaches end of life in 2029. If your project data has to stay on your own servers, here is a self-hosted home for it, with your history intact.

Read article →
Recurring Tasks in Project Management, Done Right

Recurring Tasks in Project Management, Done Right

Recurring tasks break the same way in every major tracker. Here's why, and how Specivo fixes each gap.

Read article →
Self-Host Specivo on Ubuntu - Docker Setup

Self-Host Specivo on Ubuntu - Docker Setup

Read article →

More from Specivo.

Open-source tools we build alongside the platform.

django-seo-suite

Django

A lightweight, extensible SEO metadata layer for Django — titles, meta tags, canonical URLs, hreflang alternates, JSON-LD schema, and Open Graph/Twitter cards across models and views, plus a versioned robots.txt. One consistent API, no extra dependencies.

GitHub Documentation