Skip to content
NEURA PARSE

TaskNebula architecture

A conventional stack with agent-aware edges.

TaskNebula uses a precise, conventional stack: Next.js 15, PostgreSQL 16 with pgvector, Redis 7, SSE realtime, optional LiveKit, Docker Compose, next-intl localization, and a public roadmap.

Work graph on PostgresSSE realtimePublic roadmap

  • Next.js 15
  • PostgreSQL 16 + pgvector
  • Redis 7
  • SSE realtime
  • next-intl
  • Docker Compose
TaskNebula real-time Kanban board for self-hosted project management
FIG 01 · Realtime board — Kanban, sprint work, drag-and-drop planning, presence, and project status loops.
Latest release
v0.7.11
Locales
30
AI posture
Opt-in
License
MIT

01Stack map

TaskNebula places AI-agent governance over infrastructure many teams already operate: Next.js, PostgreSQL, Redis, optional LiveKit, and Docker Compose.

01
Next.js 15 App RouterReact 19TypeScript 5.7Tailwindshadcn/uiTanStack Query
02
Next.js route handlersAuth.js v5Drizzle ORMZod contractsPino logging
03
PostgreSQL 16pgvectorRedis 7S3-compatible uploadspg_stat_statements
04
SSE event busRedis pub/subYjs editingLiveKit voice rooms
05
Docker ComposePublished imageCron sidecarHealth checksReverse proxy ready
06
AES-256-GCM credentialsSigned webhooksAudit logsAGENTOWNERSApproval gates

02System model

The roadmap keeps the boundary clear: no chat, video, or wiki super-app; no full standalone calendar; and no native-mobile-first detour. The work graph remains the core.

01

TaskNebula ships as a standalone Next.js 15 web container with App Router, React 19, route handlers, and Docker-first runtime assumptions.

Next.js 15React 19Docker

02

The roadmap explicitly positions TaskNebula as a self-hostable Linear control plane that avoids sprawling infrastructure and centers the work graph around PostgreSQL.

PostgreSQL 16pgvectorDrizzle

03

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.

SSERedis pub/subYjs

04

The app ships 30 languages, browser/device auto-detection, native-name language switching, and RTL support for Arabic and Hebrew.

next-intl30 localesRTL

05

RBAC, issue security levels, audit-log action types, signed webhooks, AGENTOWNERS, and approval gates are part of the public technical surface.

RBACHMACAudit

06

The roadmap names shipped, partial, and open work, including tenant isolation, API-key auth, pagination, MCP v2, importer v2, and governance completion.

Q3 2026Q4 2026H1 2027
Operating flow
  1. 01

    localized app

  2. 02

    Zod + auth

  3. 03

    issues + embeddings

  4. 04

    SSE events

  5. 05

    opt-in BYOK

03Roadmap posture

Technical evaluators can distinguish available capability from partial implementation and open roadmap work without inheriting an inflated maturity claim.

01

Q3 2026

Labels, components, versions, resolution, issue rank, workflow enforcement, boards, JQL v2, notification schemes, tenant isolation, API keys, pagination, and scale floor.

02

Q4 2026

Deep GitHub/GitLab links, importer v2, release notes, semantic search, Ask-AI last mile, agent approval queue, MCP v2, and coding-agent deeplinks.

03

H1 2027

Custom hierarchy, field schemes, permission enforcement, portfolio plans, SLAs, configurable dashboards, proactive risk detection, and agent builder direction.

04Evaluation notes

Documented gaps and staged work remain part of the evaluation; TaskNebula does not claim finished enterprise parity across every surface.

01

Ask/RAG, embeddings, MCP, agent engine, analytics, and importer work have visible roadmap follow-through.

02

Tenant isolation, API-key scopes, pagination, type-safety restoration, and governance completion are named as platform prerequisites.

03

Self-hostable Linear, control plane for AI agents, Postgres-first operations, and no super-app sprawl.

Run it yourself

TaskNebula is a self-hostable project-management control plane for teams that want inspectable operations instead of another black-box SaaS.