01Frontend
A conventional stack with agent-aware edges.
TaskNebula's technical story is strongest when it is precise: Next.js 15, PostgreSQL 16 with pgvector, Redis 7, SSE realtime, optional LiveKit, Docker Compose, next-intl localization, and public roadmap discipline.

FIG 01 · Realtime board — Kanban, sprint work, drag-and-drop planning, presence, and project status loops.
v0.7.11
Latest release
30
Locales
36
GitHub stars · 12 Jul 2026
MIT
License
The architecture reads like an operator can actually run it.
This is intentionally not a novelty stack. The repo's value proposition is a self-hosted PM control plane with AI-agent governance on top of infrastructure teams already know.
02Backend
03Data
04Realtime
05Ops
06Trust
Realtime work graph, not a super-app.
The public roadmap explicitly says what not to build: not a chat/video/wiki super-app, not a full standalone calendar, not native mobile first. The core is the work graph.
01
Next.js standalone web
TaskNebula ships as a standalone Next.js 15 web container with App Router, React 19, route handlers, and Docker-first runtime assumptions.
02
Postgres-centered work graph
The roadmap explicitly positions TaskNebula as a self-hostable Linear control plane that avoids sprawling infrastructure and centers the work graph around PostgreSQL.
03
Realtime without exotic sync
Issue create/update/delete events use SSE with Redis pub/sub and in-process fallback for single-instance installs. Yjs supports collaborative editing where wired.
04
Global product shell
The app ships 30 languages, browser/device auto-detection, native-name language switching, and RTL support for Arabic and Hebrew.
05
Trust and audit surfaces
RBAC, issue security levels, audit-log action types, signed webhooks, AGENTOWNERS, and approval gates are part of the public technical story.
06
Roadmap is honest
The roadmap names shipped, partial, and open work, including tenant isolation, API-key auth, pagination, MCP v2, importer v2, and governance completion.
- 01
Browser / PWA
localized app
- 02
Next.js route handlers
Zod + auth
- 03
PostgreSQL work graph
issues + embeddings
- 04
Redis fan-out
SSE events
- 05
AI / integrations / agents
opt-in BYOK
Architecture summary is grounded in the public README, docker-compose.yml, and ROADMAP_2026.md.
Shipped, partial, and open work are separated.
That is useful for technical buyers: it prevents overclaiming and turns the page into an honest evaluation surface instead of a glossy project landing page.
01Q3 2026
Work-graph foundations
Labels, components, versions, resolution, issue rank, workflow enforcement, boards, JQL v2, notification schemes, tenant isolation, API keys, pagination, and scale floor.
02Q4 2026
Developer workflow and AI-native differentiation
Deep GitHub/GitLab links, importer v2, release notes, semantic search, Ask-AI last mile, agent approval queue, MCP v2, and coding-agent deeplinks.
03H1 2027
Premium-gated OSS wedge
Custom hierarchy, field schemes, permission enforcement, portfolio plans, SLAs, configurable dashboards, proactive risk detection, and agent builder direction.
Useful constraints belong on the page.
TaskNebula should not claim finished enterprise parity everywhere. The repo itself documents gaps and staged work, which makes the public page more credible.
01Built but still being wired
Ask/RAG, embeddings, MCP, agent engine, analytics, and importer work have visible roadmap follow-through.
02Trust hardening track
Tenant isolation, API-key scopes, pagination, type-safety restoration, and governance completion are named as platform prerequisites.
03Product direction
Self-hostable Linear, control plane for AI agents, Postgres-first operations, and no super-app sprawl.
Pull the image, keep the data, wire your own AI keys.
TaskNebula is positioned as the self-hostable project-management control plane for teams that want inspectable operations, not another black-box SaaS.