Overview

VoidTrack is open source, self hostable issue tracking. It follows Linear's model: initiatives, projects, issues, teams, cycles, and estimates, without the bloat. It is built agent native, meaning the REST API and the MCP server are first class citizens. The web UI is just another client of the same API.

Status

VoidTrack is an MVP that is usable end to end today.

• Teams, issues, workflow states, labels, and priorities
• Projects and initiatives, with cycles and estimates at the team level
• A REST API with API key auth, plus an MCP server over stdio and streamable HTTP
• A web UI: issues list and board, issue detail, projects, initiatives, cycles, and live updates via SSE
• GitHub integration: PR linking, magic words, and auto transition on open or merge
• Passwordless sign in (email OTP) plus email invites
• Multi organization support: one account, many workspaces, an org switcher, and admin or member roles
• Media attachments on issues (images and video inline), stored on R2, S3, or local disk
• Markdown documents with a unified /docs view, linkable to any number of issues
• A Linear import script that preserves team keys and issue identifiers
• Local first reads: ElectricSQL syncs into a TanStack DB store in the browser for instant lists, boards, and command palette search
• Board drag and drop, and a command palette (cmd-K)
• Saved views for issues and projects, with filters and preset sorting
• Updates with automated health signals (target date versus progress) on projects and initiatives
• A personal "Private" space per member, since all teams are member scoped

Start here

• Quickstart: run VoidTrack locally in a few commands.
• Self hosting: Docker Compose, Railway, and the environment variable reference for production deployments.
• API overview: base URL, authentication, and response conventions for the REST API.
• MCP: connect an MCP client over streamable HTTP or stdio.

Go deeper

• GitHub integration: link pull requests to issues and auto transition state.
• Sync engine: how local first reads work under the hood.
• Fonts: configure the UI font without bundling anything.
• Importing from Linear: bring over an existing Linear workspace.
• The MCP tool reference lists every tool, its parameters, and whether each is required.

Data model

Workspace, then teams, then issues. Projects live at the workspace level, span teams, and roll up into initiatives. Cycles belong to teams. Priorities follow Linear: 0 is none, 1 is urgent, 2 is high, 3 is medium, 4 is low. Workflow states are per team and typed as backlog, unstarted, started, completed, or canceled, so tooling can reason about state types even while you rename the states themselves.

Licensing

VoidTrack is dual licensed. AGPL-3.0 is the default: free for everyone, including commercial use, with the catch that a modified VoidTrack offered to others over a network must publish its source under AGPL too. A commercial license removes that obligation, for teams embedding VoidTrack in a proprietary product or offering it as a hosted service without publishing their changes. Self hosting an unmodified VoidTrack for your own team never requires a commercial license. Contact aneeshbhat@devvoid.org for commercial terms.