Your stack, our orchestration
How Olon orchestrates Vercel, Supabase, GitHub, and Resend into a single sovereign deployment pipeline.
Free deploys.
Instant edits.
Free tenants deploy to Vercel's edge on every git push. Paid tenants get hot save to Supabase — content changes propagate in milliseconds without a rebuild. Both modes share the same codebase and the same contract.
We go down.
Your site stays up.
Olon never touches your production environment directly. Your Vercel deploy is independent of our platform. Your content is in your repo. If Olon disappears tomorrow, nothing changes for your users.
Your Vercel project
Your billing, your limits, your deploy settings.
Your GitHub repo
Clone, fork, or migrate at any time.
Your Supabase instance
Direct Postgres access. Open source. Self-hostable.
Your custom domain
We configure DNS. You control the registrar.
Your content in git
JSON files. No export needed. No migration cost.
Every page at /{slug}.json.
Always.
The machine contract is not a feature flag. Every OlonJS tenant serves a canonical JSON endpoint alongside the human UI — deterministic, typed, always in sync. AI agents, monitoring tools, and automation workflows operate on any tenant without custom integration.
/{slug}.json
Canonical endpoint on every page. Typed PageConfig with sections, meta, and slug. Deterministic structure across all tenants.
Zod schemas
Every section type has a validated schema. Build-time and runtime validation. AI agents know the contract before generating content.
Git history
Every content change is a signed commit. The git log is the audit trail — immutable, distributed, always available without Olon.
Scaffolds a production-ready OlonJS tenant with TypeScript, Vite, Tailwind v4, and all four integrations wired in.
Connect your Vercel and GitHub accounts in the dashboard. Supabase needed for hot save (Full tier).
Your stack, our orchestration.
Start with the free deploy tier. Upgrade when you need instant content.