Where we're going

Vision.

Three horizons for the DeesseJS main app — what's shipping today, what we're building toward next, and where we want to land eventually. Revised as the roadmap moves.

Last updated: 2026-08-04.

Now

Shipping today

What you can pull from the registry and the CLI today.

Curated template registry
Templates covering SaaS, AI, and landing surfaces, each contract-validated against @workspace/contracts before publish.
End-to-end stack defaults
Next.js, Better Auth, Drizzle, shadcn/ui, Tailwind v4 — wired and ready to run on day one.
Public CLI with offline cache
deessejs init / list / info — works offline, ships with retry and a local ETag-keyed cache.
ISR-backed marketing surfaces
The marketing site renders the catalog server-side, contract-validated, with tag-based revalidation.

In flight this quarter

What we are actively building toward. Subject to revision.

Agent-aware template metadata
Each template carries machine-readable capabilities, compatible agents, and install hints — so a coding agent can pick and run one without human nudging.
Categories + frameworks filter
The catalog becomes browsable by type and by framework, with multi-select URL state and per-template counts.
Multi-tenant auth as a first-class package
An opt-in package that brings row-level multi-tenancy to new templates without rewiring the auth flow.
Vercel preview + CI
Every PR runs lint, typecheck, unit tests, integration tests, and a Vercel preview deploy. Merges are gated green.

Beyond

Aspirational

Where we are heading if everything else goes well. No dates.

Templates that ship themselves
An agent reviews the diff, runs the smoke tests, opens the PR, and waits on a human reviewer for sign-off. We write the reviewers.
A registry as a marketplace
Authors ship templates through the same registry we use ourselves — opinionated defaults, versioned, contract-tested. Discovery, install, and update all in one tool.
Composable primitives, not stacks
Stop shipping monoliths. Users pull packages — auth, db, payments, observability — individually, with templates that demonstrate how they fit together.
Agent observability as a first-class concern
The traces, logs, and metrics of an AI agent running your stack are observable by default. We treat the agent as a first-class actor in the system, not a side effect.

Where we're going

Vision.

Three horizons for the DeesseJS main app — what's shipping today, what we're building toward next, and where we want to land eventually. Revised as the roadmap moves.

Last updated: 2026-08-04.

Now

Shipping today

What you can pull from the registry and the CLI today.

Curated template registry
Templates covering SaaS, AI, and landing surfaces, each contract-validated against @workspace/contracts before publish.
End-to-end stack defaults
Next.js, Better Auth, Drizzle, shadcn/ui, Tailwind v4 — wired and ready to run on day one.
Public CLI with offline cache
deessejs init / list / info — works offline, ships with retry and a local ETag-keyed cache.
ISR-backed marketing surfaces
The marketing site renders the catalog server-side, contract-validated, with tag-based revalidation.

In flight this quarter

What we are actively building toward. Subject to revision.

Agent-aware template metadata
Each template carries machine-readable capabilities, compatible agents, and install hints — so a coding agent can pick and run one without human nudging.
Categories + frameworks filter
The catalog becomes browsable by type and by framework, with multi-select URL state and per-template counts.
Multi-tenant auth as a first-class package
An opt-in package that brings row-level multi-tenancy to new templates without rewiring the auth flow.
Vercel preview + CI
Every PR runs lint, typecheck, unit tests, integration tests, and a Vercel preview deploy. Merges are gated green.

Beyond

Aspirational

Where we are heading if everything else goes well. No dates.

Templates that ship themselves
An agent reviews the diff, runs the smoke tests, opens the PR, and waits on a human reviewer for sign-off. We write the reviewers.
A registry as a marketplace
Authors ship templates through the same registry we use ourselves — opinionated defaults, versioned, contract-tested. Discovery, install, and update all in one tool.
Composable primitives, not stacks
Stop shipping monoliths. Users pull packages — auth, db, payments, observability — individually, with templates that demonstrate how they fit together.
Agent observability as a first-class concern
The traces, logs, and metrics of an AI agent running your stack are observable by default. We treat the agent as a first-class actor in the system, not a side effect.

Curated template registry

End-to-end stack defaults

Public CLI with offline cache

ISR-backed marketing surfaces

Agent-aware template metadata

Categories + frameworks filter

Multi-tenant auth as a first-class package

Vercel preview + CI

Templates that ship themselves

A registry as a marketplace

Composable primitives, not stacks

Agent observability as a first-class concern