Stack
Hosting, database, auth, queue, billing, observability, email, and ORM. Every template wires these in. None of them are locked in: each contract ships with a typed layer, so the same app runs against a different provider if you bring your own.
Default deploy target for DeesseJS apps. Preview environments per PR, production environments on main, and the cross-project preview links that bind apps/web to apps/app.
Visit homepageDNS, edge caching, and queue workers via Cloudflare Queues. Used where the request path benefits from running at the edge rather than the origin.
Visit homepageServerless Postgres we point the database package at for production deployments. Branches map to preview environments, autoscaling matches the request path.
Visit homepagePostgres plus object storage with signed URLs and presigned uploads. Drop-in alongside Drizzle when the contract needs object storage rather than a relational row.
Visit homepageThe relational substrate every DeesseJS app assumes. Drizzle is the typed layer; Neon, Supabase, or a local container provide the actual database server.
Visit homepage