Hi all — I've been building NextBlock, an open-source CMS for Next.js 16 + Supabase, and I'd like to put it in front of people who actually run things on Vercel.

What it is: a single Next.js 16 app that serves both the public website and the authenticated CMS, backed by Supabase Postgres. Content blocks are rows with a jsonb content column, so user-defined block types can be created in the admin UI and render without a rebuild. There's a Tiptap-based visual editor, live draft mode for in-page editing, and multilingual routing.

Why I'm posting here rather than the template gallery: I understand new template submissions aren't being accepted right now, so the Deploy Button in the README is the route — which turned out to be an interesting problem in itself.

The deploy path, since it may be useful to others: the button uses the stores parameter for the native Supabase Marketplace integration, so Vercel provisions the database and injects credentials before the first build. That timing matters, because the app applies its own forward-only migrations during that build via an Nx run-commands prebuild step. The result is a deploy with zero environment variables to fill in — you click the button, pick a database region, and the only remaining step is creating your admin account in the browser.

Two things I learned the hard way and would happily be corrected on:

• integration-ids and stores are both current, but only stores documents creating the store as part of the deployment. For a build-time migration hook that needs POSTGRES_URL to exist during the build, that distinction is the whole ballgame.
• In an Nx monorepo the build hook has to be wired into the Nx target, not just the npm prebuild script — Nx doesn't trigger npm lifecycle hooks.

Stack: Next.js 16 App Router, React 19 Server Components, Supabase (Postgres + RLS + Auth + Storage), Tailwind, Nx monorepo, Vitest.

Licensing: AGPL-3.0-or-later, open-core. Premium modules (commerce and Cortex AI so far...) are published publicly under the same license and gated at runtime by license key.

What I'd value: feedback on the deploy flow from anyone who tries it, and contributors. There's a CONTRIBUTING.md covering setup and the repo's sharper edges, plus a Code of Conduct and a security policy.

• Repo: NextBlock Github
• Live sandbox: https://cms.nextblock.dev (demo@nextblock.dev / password, resets daily)

Happy to answer anything about the architecture or the Supabase integration.