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

Getting started

What New Orange CMS is

A Sanity-compatible content platform that runs entirely inside your own Vercel and Supabase accounts, with a real Sanity Studio as its editor.

New Orange CMS is a content management platform with three properties that are usually mutually exclusive:

  • It is compatible with the Sanity ecosystem. The editor is a fork of Sanity Studio v6, the query language is GROQ, and @sanity/client connects to it unmodified.
  • It is entirely yours. There is no hosted backend in the middle. Documents live in a Postgres database in a Supabase project you own; asset bytes live in a Vercel Blob store you own.
  • It installs itself. One Deploy Button provisions the infrastructure, and the first build migrates the schema, creates an administrator and seeds a working dataset.

What that gets you

The practical answer is: the Sanity developer experience, on infrastructure you can inspect, back up and take with you.

  • Schemas are ordinary defineType definitions, and the Studio's structure builder is the real one.
  • Content is queryable with GROQ, including projections, joins and functions.
  • The database is a Postgres you can open with psql, join against your own application tables, and dump.
  • Nothing about a deployment talks to a hosted service you do not control.

What it is not

It is not a proxy in front of Sanity's Content Lake, and it is not a re-implementation of Sanity's hosted product. Scheduled publishing, releases, Canvas, the hosted Media Library and Sanity's SSO are out of scope by design, and the compatibility page names them rather than leaving them to be discovered.

It is also not a general-purpose "headless CMS in a box" that hides its database. The schema is in the repository, the migrations are plain SQL, and the row-level security policies are readable.

How the pieces fit

text
your Vercel project
  ├── /            the public site (Next.js, your own frontend or this one)
  ├── /admin       the Studio (a fork of Sanity Studio v6)
  ├── /api         the Sanity-compatible HTTP API
  ├── /images,/files  asset delivery
  └── Supabase Postgres + Vercel Blob (both provisioned for you)

The API is the seam. The Studio talks to it, your frontend talks to it, and anything else that speaks the Sanity protocol talks to it too.

Where to go next