Natural Language Postgres

nl-postgres

Vercel's Natural Language Postgres — a question about a table of unicorn companies asked in plain English, the SQL a model writes for it, the rows, a chart of them and an explanation of the query: one page and four server actions — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare, its SQL written by Workers AI through the Worker's AI binding and run as a read-only database role, its table a Supabase project's database reached through Cloudflare Hyperdrive, both provisioned by Terraform through Orun and the schema applied by Orun's db-migrate, the way the rag-chatbot 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 template's code is the code. What the port changes is what the Workers runtime, a fresh unattended deployment and SQL written by a model force: the database client is built per call over the Hyperdrive binding (lib/db.ts); the model is Workers AI's (lib/ai/models.ts) — the platform brokers no AI vendor, and the Cloudflare account the app deploys into already is one — with upstream's OpenAI model behind an optional key; and the model's SQL runs only as query_reader, a role that can read the one table and nothing else, through a function it cannot step out of (migration 040_read_only_queries), with the template's own string check kept in front. The template's data is CB Insights' list, which each owner downloads; a fresh product starts with sixty fictional companies in its shape, and a tool turns the owner's CSV into a migration. 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/nl-postgres 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/nl-postgres
cd nl-postgres
orun new --blueprint repo-blueprint.yaml --out ~/products/acme-sql --run-hooks --resume \
  --set reponame=acme-sql --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 → nl-postgres → 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 AI vendor key is asked for: Workers AI needs none, and OpenAI is the owner's to add afterwards (the product's README, "Use OpenAI instead").

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 + opennextjs-cloudflare build → apps/web/.open-next
pnpm --filter @saas/db run manifest:check

The build needs no database, no model and no Cloudflare credential. Running it locally — a Postgres on localhost:5432, pnpm --filter @app/web db:migrate:local, wrangler login for Workers AI, 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