Deployment Overview

Supported today: local Docker Compose is the primary, demo-ready deployment path in this checkout. The hosted split is now: application surfaces on Azure Container Apps, public docs on Vercel. The Azure path is still preview-grade until it is exercised end to end in a real environment.

Deployment Targets

Target	Guide	Best For
Docker Compose	Supported today	Local demo, self-hosted, private cloud, on-premises
Azure Container Apps	Preview	Infrastructure iteration, hosted app rollout, future managed SaaS deployment
Vercel (packages/docs)	Supported today	Public docs site, branch previews, lightweight static/content deployment

What Runs Today

Service	Image	Purpose
orginabox-api	orginabox-core:<git-sha>	Hono REST API on port 8787
orginabox-worker	orginabox-core:<git-sha>	Job drainer (same image, different CMD)
orginabox-sandbox	orginabox-sandbox:<git-sha>	opencode runtime + noVNC
orginabox-web	orginabox-web:<git-sha>	Next.js dashboard on port 3000
orginabox-platform-web	orginabox-platform-web:<git-sha>	Platform admin app on port 3002
orginabox-tenant-web	orginabox-tenant-web:<git-sha>	Tenant admin app on port 3003
orginabox-docs	Vercel project rooted at packages/docs	Public docs site and preview deployments
postgres	pgvector/pgvector:pg16	Database (managed by Azure in prod)

What Azure Provisions Today

• api, worker, sandbox, web, platform-web, and tenant-web Container Apps
• Azure PostgreSQL, Key Vault, Log Analytics, and ACR
• a shared runtime Azure Files volume mounted into the API, worker, and sandbox
• build-once CI that publishes unique image tags, smoke-tests those exact images, deploys Azure staging on main, and lets prod promote the same tag manually
• a docs URL contract (ORGINABOX_DOCS_URL) so the main web app links to the Vercel-hosted docs site instead of an Azure docs container

What Azure Does Not Yet Provision

• The multi-sandbox pool topology described in longer-term architecture notes
• A live-validated Azure demo path from this checkout alone; you still need real secrets, domains, and a first deployment pass

Vercel Docs Notes

• The public docs site is a separate Vercel project rooted at packages/docs.
• The effective Vercel project config lives in packages/docs/vercel.json for the docs app itself.
• The repo-root vercel.json is intentionally minimal; it exists for schema validation and future monorepo-level Vercel metadata, not as the authoritative docs deployment config.
• In the Vercel dashboard, set:
  • Framework Preset: Next.js
  • Root Directory: packages/docs
  • Include files outside the Root Directory in the Build Step: Disabled
  • Skip deployments when there are no changes to the root directory and its dependencies: Enabled

Pre-deployment Checklist

See the Environment Checklist for a complete list of required environment variables per deployment target.