Case study

The site you are reading is the demo.

We build websites, web apps, and AI systems for founders, so our own website has to prove it. Here is the architecture, design system, and AI publishing pipeline behind mettabyte.com.

Client

Ourselves

Build type

Marketing site + CMS + AI tools

Framework

Next.js 16

Hosting

Cloudflare edge

Everything described here is verifiable by using the site: the speed, the design system, the blog, the booking flow. No claims you cannot check yourself.

Problem

A studio site has to prove capability

Anyone can claim engineering quality. A studio’s own website is the one project where the client cannot hide the result.

Constraint

Built between client work

The site is built and maintained by the same small team that ships client projects, so every pattern has to be reusable and cheap to maintain.

Result

A living portfolio piece

The design system, AI pipeline, and performance work double as the sales pitch: visitors experience the quality before the first call.

What we built

The same systems we sell, running in production.

The site is a working example of our three service lines at once: a conversion-focused website, a CMS-backed web application, and an AI content pipeline.

A reusable design system

Glass surfaces, ambient light, and a consistent section language built as composable React components. Every page on this site is assembled from the same kit.

AI-assisted publishing pipeline

A private admin studio where drafts are generated with AI, keyword suggestions are automated, and every post is human-edited before it publishes to the Sanity CMS.

Performance as a feature

Static generation for content pages, lazy-loaded syntax highlighting, mobile-tuned animations, and view transitions between pages.

Edge deployment

Deployed to Cloudflare’s edge network, with per-route Open Graph images, a generated sitemap, and SEO metadata on every page.

How we work on it
Designed the section system first, then built pages from it instead of designing each page from scratch.
Wired the blog to a headless CMS so content work never requires a code deploy.
Built the AI drafting tools we recommend to clients, and used them on our own content first.
Audited and tuned the whole site at mobile viewports before shipping changes.
Kept the same delivery discipline we sell: scoped iterations, shipped in small verified steps.
Technical foundation

Design system

AI pipeline

Edge deploy

Next.js 16React 19TypeScriptTailwind CSS 4MotionSanity CMSAzure OpenAICloudflare Pages
Outcome

If you like using this site, you already know how we build.

The site itself is the demo: the design system, AI pipeline, and performance work are all inspectable by visiting it.

Publishing a post takes minutes, not a deploy cycle, because content lives in the CMS.

The AI tooling we ship to clients is the same tooling running our own content operation.

Every pattern on this page (fixed scope, small team, direct engineering) is how the site was actually built.