Morphic

morphic

Vercel's Morphic template (miurla/morphic) — an AI answer engine with a generative UI: it searches the web and answers with its sources cited, quick and adaptive search modes, a model picker over OpenAI, Anthropic, Google and any OpenAI-compatible API, chat history and sharing, a library of notes and files, multi-user accounts with Better Auth — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare, its chat history and accounts a Supabase project's database reached through Cloudflare Hyperdrive, both provisioned by Terraform through Orun and upstream's schema applied by Orun's db-migrate — the way the Lumen baseline does it, and packaged as an Orun baseline: one command takes a new product from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing. The Cloudflare account must be on Workers Paid: the Worker is about 7.7 MiB gzipped, over Workers Free's 3 MiB.

The template's code is the code. What the port changes is what the Workers runtime and a fresh, unattended deployment force: the database client is built per request over the Hyperdrive binding behind upstream's own db (lib/db/index.ts); Better Auth's signing key is generated in the database by a migration instead of typed; the instrumentation loads OpenTelemetry only when Langfuse tracing is on; the fetch guard's undici dispatcher steps aside inside a Worker, which has no host network to guard; SearXNG's crawling route, which needs jsdom and TCP Redis, is not carried; and a final migration shuts Supabase's Data API out of every table. Models and search are the owner's keys, set as Orun secrets after the build — the platform brokers neither — so a fresh product serves with "No enabled model available" until they are. What the baseline adds is everything needed to make a copy of it somebody else's — built the way cirrus-baseline is. See specs/epics/morphic for the design, the milestones and the as-built status, including every departure.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/morphic
cd morphic
orun new --blueprint repo-blueprint.yaml --out ~/products/acme-search --run-hooks --resume \
  --set reponame=acme-search --set productname="Acme Answers" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → morphic → Build). Two phases: 01-product creates the repository, mints the five brokered credentials (Cloudflare and Supabase) and lands the whole product as one pull request, whose convergence on main provisions and deploys it per environment in a fixed order —

supabase ──▶ cloudflare-hyperdrive ──▶ db-migrate ──▶ web

— each edge mode: enforced on a push to main and advisory on a pull request; then 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

It creates two Supabase projects, <reponame>-stage and <reponame>-prod. Supabase's free plan allows two active projects per organization, so the connected organization needs room for both (BOOTSTRAP.md, §0).

The new repository receives the product only — the app, the Terraform roots, the migrations, the tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Worker, Supabase project and Hyperdrive config. None of this repository's machinery ships. No model or search key is asked for: the owner sets them as Orun secrets afterwards, with the address of the account that may sign up first (the product's README, "First steps").

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # re-render apps/web/wrangler.jsonc from its template (committed; this changes nothing)
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # next build --webpack + opennextjs-cloudflare build → apps/web/.open-next
pnpm --filter @saas/db run manifest:check

The build needs no database, no model, no key and no Cloudflare credential. Running it locally — a Postgres on localhost:5432, pnpm --filter @app/web migrate, a model key and a search key in apps/web/.dev.vars, next dev or wrangler dev — is in the product's README (.baseline/product/README.md), which is what a product built from here carries.

How it maps to Vercel

CI