How opchain.dev is built.

Frontend

Static site, dark-first, hand-tuned typography. Astro is the assembler; nothing ships as a React SPA.

Backend

A single Cloudflare Worker behind opchain.dev. Static assets are served via the ASSETS binding; the JS handler picks up /api/*.

Integrations

Each one is opt-out via a flag — every flag's default keeps the site running if the integration goes away.

Hosting & DNS

Production and staging both run as Workers with custom-domain binding. Cloudflare manages DNS automatically on wrangler deploy.

Tooling

Most of these are themselves opchain skills. The site is the product's reference customer.

Hardware

Skills are Markdown — they don't care what they run on, but the workflow optimises for keyboard speed.

The recursion

Yes, this site was built with the very skills it markets.oc-app-architect ran the spec, oc-stack-forgepicked Astro 5 over Next.js, oc-ux-engineerowned the design system, and oc-code-auditorcatches type-safety regressions before merge. Every release is cut by oc-release-opsand shipped from a laptop viaoc-deploy-ops.

That dogfooding is why the changelog moves fast — there's no translation layer between "what we noticed" and "what opchain ships next."

Want to build the same way?Install opchain · build a pipeline for your stack.