TaskNebula / final-source architecture
The original work graph remains inspectable.
The final TaskNebula source used Next.js, PostgreSQL, Redis, realtime collaboration, optional LiveKit and Docker Compose. This is a historical architecture record; N-Task is the current N-N product with its own scope and terms.
Final OSS 0.17.3MIT sourceFormer roadmap
- Next.js
- PostgreSQL + pgvector
- Redis
- Realtime collaboration
- next-intl
- Docker Compose

- Current product
- N-Task
- Final OSS release
- 0.17.3
- Legacy source license
- MIT
- OSS support
- Ended
01Stack map
A conventional stack, arranged for self-hosting.
The final TaskNebula source placed AI-agent governance over Next.js, PostgreSQL, Redis, optional LiveKit and Docker Compose.
Backend
Data
Realtime
Ops
Trust
02System model
Realtime work graph, not a super-app.
The former TaskNebula roadmap kept the work graph central. Its choices are historical and should not be read as N-Task's current product direction.
01
Next.js standalone web
The final TaskNebula source packaged a standalone Next.js web container with App Router, React, route handlers, and Docker-first runtime assumptions.
02
Postgres-centered work graph
The former roadmap positioned TaskNebula as a self-hostable work graph centered on PostgreSQL, with a limited infrastructure footprint.
03
Realtime without exotic sync
The final source used SSE with Redis pub/sub for issue events and an in-process fallback for single-instance installs. Yjs supported 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 surface.
06
Roadmap is honest
The roadmap names shipped, partial, and open work, including tenant isolation, API-key auth, pagination, MCP, importer depth, 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
03Former roadmap
A record of what had shipped and what had not.
These were TaskNebula's plans before maintenance ended. Unfinished entries are not current N-Task commitments or an active open-source roadmap.
Foundation
Work-graph foundations
Labels, components, release records, resolution, issue rank, workflow enforcement, boards, structured queries, notifications, tenant isolation, API keys, pagination, and scale floor.
Next
Developer workflow and AI-native differentiation
Deeper code-host links, importer improvements, release notes, semantic search, Ask-AI completion, agent approval queues, MCP expansion, and coding-agent handoffs.
Longer term
Premium-gated OSS wedge
Custom hierarchy, field schemes, permission enforcement, portfolio plans, SLAs, configurable dashboards, proactive risk detection, and agent builder direction.
04Evaluation notes
Known constraints stay visible.
Documented gaps remain part of the final TaskNebula record. No further TaskNebula fixes are promised; assess N-Task under its separate current documentation.
Built but still being wired
Ask/RAG, embeddings, MCP, agent engine, analytics, and importer work have visible roadmap follow-through.
Trust hardening track
Tenant isolation, API-key scopes, pagination, type-safety restoration, and governance completion are named as platform prerequisites.
Product direction
Self-hostable Linear, control plane for AI agents, Postgres-first operations, and no super-app sprawl.
Continue with N-Task
The work has a new product home.
Explore N-Task for current project, task and team-documentation workflows. The TaskNebula repository remains a final, unsupported MIT source record for existing users and researchers.
