The New Orange mark: a radial orange gradient on a dark square.New Orange CMS

Getting started

Deploy in one click

What the Deploy Button provisions, what you are asked for, what the first build does, and how to check the result.

Deploying is one button and one password. Everything else — the database, the storage, the schema, the administrator, the demo content — is provisioned or created for you.

What the button provisions

  • A Vercel project, cloned from the repository into your own account.
  • A Supabase project through the Vercel Marketplace integration, which syncs its URL, its keys, its JWT secret and the whole POSTGRES_* family into the project's environment.
  • A Vercel Blob store, which supplies the token asset uploads need.

All of those variables are present in the first build, before anything is compiled. That is what makes a self-installing build possible at all.

What you are asked for

One value: the password for the administrator account the build will create.

text
DEMO_USER_PASSWORD   the password for demo@neworange.cms

You are deliberately not asked for a Supabase access token. It would let the build close self-service sign-up on the new project outright, but the token is only obtainable from the Supabase dashboard — and a required dashboard visit is exactly the manual step one-click deployment exists to eliminate. The build warns loudly about the resulting posture instead.

What the first build does

  1. Applies the SQL migrations, under a Postgres advisory lock.
  2. Creates and confirms the administrator, exactly once, and never rewrites its password.
  3. Seeds the demo dataset and uploads its images — only into a dataset with no content documents.
  4. Asserts the sign-up posture and reports it.
  5. Builds the Next.js app.

When it finishes

  • Open / — the public site, rendered from the seeded dataset.
  • Open /admin and sign in with demo@neworange.cms and your password.
  • Open /api/v2026-07-26/data/query/production?query=count(*) — the API, answering anonymously.

If the site renders but the Studio cannot sign in, the environment is fine and the administrator step is what to look at; the build log prints each step's outcome as a line.

Redeploying

Safe, and unremarkable. Migrations are idempotent, the administrator is created once, and the content seed sees a non-empty dataset and stops before writing anything.