TaskNebula is the open-source, keyboard-first alternative to Jira and Linear. Boards, sprints, and docs that run on your own Postgres — with a built-in MCP server so AI agents work the backlog right beside your team. MIT licensed, self-host with one Docker Compose.
Switch projects, drag issues between stages, and keep details close without fake motion or noisy chrome.
No tool-hopping between a tracker, a planning doc, and an agent console. The work moves through a single surface — humans and agents on the same timeline.
TaskNebula Board
Workspace preview
The flow
Refine launch page hierarchy
Backlog
Plan the sprint in place
To Do
Build alongside agents
MCP tools for agents
Review approved
In Review
Ship and track the outcome
Shipped
Tighten hero, simplify copy, and make the landing feel more premium.
AI and agent features are optional, configuration-dependent, and some remain in preview.
Ask searches issues and docs today. Semantic retrieval needs an organization-safe embedding provider.
AI suggestions are preview features and depend on configured provider credentials. Review every suggestion before applying it.
Preview: the source-built MCP package supports 11 tools with organization-bound API keys. OAuth, per-call audit, and public package delivery are not finished.
One command starts a small Compose stack. Core data lives in Postgres, export is a pg_dump away, and nothing phones home by default — no vendor lock-in by design.
One Postgres, one web image
One command starts a small Compose stack. Core data lives in Postgres, export is a pg_dump away, and nothing phones home by default — no vendor lock-in by design.
Migrations run on boot
The image applies every database migration at startup. Upgrading is pulling a newer tag and restarting — nothing manual.
Health you can probe
GET /api/health returns 200 when the app is ready — wire it to your load balancer, uptime checks, or compose healthcheck.
Pin the version you trust
Set TASKNEBULA_IMAGE=neuraparse/tasknebula:X.Y.Z to lock a release, or follow :latest for the bleeding edge.
$ mkdir tasknebula && cd tasknebula$ curl -fsSLo compose.yml https://raw.githubusercontent.com/neuraparse/tasknebula/main/docker-compose.desktop.yml$ docker compose up -dThe web image waits for Postgres, runs migrations, then serves on http://localhost:3000 — open it and finish the first-run admin wizard. Image: neuraparse/tasknebula.
No sales gate, no asterisks. If yours is missing, open a GitHub issue — public answers beat private threads.
Yes — the whole app is MIT licensed: boards, sprints, docs, analytics, the AI surfaces, and the MCP server. No open-core split, no paywalled tier, no per-seat fee. Self-host it and run it forever for unlimited users; fork it if you want to.
Self-hosting is the default path. Bring Docker and start a small Compose stack with Postgres 16 and pgvector, Redis 7, the neuraparse/tasknebula web image, and the bundled or optional services you enable. Migrations run on boot, GET /api/health is the probe, and the quickstart opens at localhost:3000.
AI is optional. Bring provider keys; budget controls reduce risk but do not guarantee a spending cap.
AI suggestions are preview features and depend on configured provider credentials. Review every suggestion before applying it.
Preview: the source-built MCP package supports 11 tools with organization-bound API keys. OAuth, per-call audit, and public package delivery are not finished.
Bring work into TaskNebula from a CSV file, Linear, Jira, or GitHub Issues. CSV is fully supported today; the other sources are in preview and may not import every field.
The core tracker — issues, boards, sprints, docs, search, REST API, and OpenAPI spec — is self-hostable. OAuth login still needs a DB adapter, so use credentials auth for now. Realtime collaboration is plumbed through Docker/Compose, but your deployment still needs a reachable URL and a live smoke test. AI and MCP remain preview. We track the gaps in docs/STATUS.md.
Self-hosted application data uses your Postgres. Access controls exist, but coverage still needs review; optional integrations send data only when you configure them.
Still unsure? Ask on GitHub or read the live status in the docs.
Create a workspace in minutes, or run the whole thing on your own box tonight — either way, the code is yours to read.