Deployment options

@norbital-ai/pod is the authoring SDK and runtime. Deploying a workspace means getting its git source built, its database provisioned, and its bundle served. Norbital Core is the managed platform that does all of this for you.

Core (managed)

Core takes your pod workspace git repo and operates the full lifecycle:

Sandboxed builds — every commit is compiled in an isolated microVM; no build box to run
Checkpoints — versioned releases, preview and live environments, sync, go live, rollback
Per-tenant databases — Neon Postgres provisioned per org, with schema migrations validated on a throwaway branch before touching live
Agent — in-workspace AI assistant (docs)
Source store, Workspace Studio, auth, billing, and multi-tenant operations

Builder / Executive / User licensing plus metered storage and AI. Enterprise adds a forward-deployed Norbital engineer.

Host-agnostic by design

Pod declares its dependencies as facility ports — Postgres, object storage, and an ai provider — rather than hard-wiring them. Core is the reference host that implements those ports. The same workspace source is portable because only the host bindings change, never the application code.

How a deploy works on Core

You edit workspace source in Workspace Studio (or push to the org repo).
Sync builds the staged tree in a sandbox, validates DDL on a preview database branch, and migrates it — giving you an isolated preview environment.
Go live rebases onto main, runs the unified deploy (build, DDL validation, live migration), and advances the live checkpoint.
If any step fails, the previous checkpoint keeps serving — deploys never break live operations.