Catalyst

catalyst-commerce

BigCommerce's Catalyst (MIT, the storefront Vercel lists as Catalyst by BigCommerce) — home, categories, brands, faceted search, product pages with options and variants, a cart, the store's checkout, accounts, orders and wish lists, a blog and gift certificates, in several languages, every BigCommerce read cached in Next's data cache — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare, with the data cache in an R2 bucket and its route lookups in a KV namespace, both provisioned by Terraform through Orun, and the tag cache and revalidation queue in Durable Objects the Worker itself exports, and packaged as an Orun baseline: one command takes a new storefront from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing.

A fresh build needs no BigCommerce store: until its owner connects one, / says "Connect your BigCommerce store" and every other page goes there — never a 500. The owner connects a store by setting its hash and a storefront token (and channel) as Orun secrets and redeploying. The account must be on Workers Paid (the Worker is about 3.4 MiB gzipped). See specs/epics/catalyst-commerce for the design, the milestones and the as-built status.

Instantiating a product

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

Or, once the platform's registry lists it, from the Orun console (Baselines → catalyst-commerce → Build). Two phases: 01-product creates the repository and lands the whole product as ONE pull request — intent, CI, tooling, the R2 root, the storefront and its tests — and one convergence applies the R2 bucket on stage and prod and then deploys the storefront bound to it; 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

The new repository receives the product only — the app, its R2 and KV roots, its tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Cloudflare Worker and bucket and namespace names. None of this repository's machinery ships. Its owner then connects a BigCommerce store with two Orun secrets and a redeploy (the product's README, "Connecting BigCommerce"); the card asks for nothing of BigCommerce's, because the platform does not broker it.

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # render apps/web/wrangler.jsonc from the offline fixture
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # GraphQL types + next build --webpack + opennextjs-cloudflare build → apps/web/.open-next

pnpm --filter @app/web dev        # http://localhost:3000, Next's dev server (Node 24: URLPattern)
pnpm --filter @app/web preview    # wrangler dev over the built Worker: local R2, KV and Durable Objects

With no store hash and token both serve the "connect your BigCommerce store" page. To run against a store, put BIGCOMMERCE_STORE_HASH and BIGCOMMERCE_STOREFRONT_TOKEN in the shell you build from and in apps/web/.dev.vars. Offline, the e2e's stand-in answers every query from the schema: node testing/lib/fake-bigcommerce.mjs --schema apps/web/bigcommerce.graphql --graphql apps/web --port 4010, with BIGCOMMERCE_GRAPHQL_API_ORIGIN=http://127.0.0.1:4010 beside the store's settings.

How it maps to Vercel

Partial prerendering is off: @opennextjs/cloudflare 1.20 cannot run Next 16's Cache Components on workerd yet (a Cache Components page answers 500 and then hangs — opennextjs-cloudflare#1450), so the storefront keeps upstream's "use cache" reads through experimental.useCache and renders every route at request time. The epic's IMPLEMENTATION-STATUS has the evidence.

How the bucket reaches the Worker

infra/terraform/cloudflare-r2 ──apply (r2-data token)──► orun secret WIRING_CLOUDFLARE_R2 (stage, prod)
                                               │   (each deploy resolves it as it starts;
                                               │    a missing one fails the lane)
                                               ▼
apps/web  dependsOn cloudflare-r2 (enforced on main) · secretEnv WIRING_CLOUDFLARE_R2_<ENV>
  build:  tooling/wire/live.mjs → wrangler.jsonc with the environment's bucket name
          (dev, verify-only, renders the fixture) → next build → opennextjs-cloudflare
  deploy: workers-deploy token → <repo>-web-<env>, its Durable Objects migrated on first deploy

wrangler.jsonc is committed as the fixture render of wrangler.template.jsonc, because the deploy lane's verify-app-structure step checks the config exists before it builds; testing/e2e.test.sh fails if the two disagree.

CI