← Back to posts

The Architecture Behind This Starter

This starter is more than a template — it’s a reference architecture. Built with Next.js, powered by Sanity, and deployed globally using OpenNext on Cloudflare Workers, it demonstrates how content and compute can work together in a modern edge-native system.

Pedro Duque
Pedro Duque
computer

1. Content Layer

Powered by Sanity:

  • Structured schemas
  • GROQ-powered queries
  • Real-time collaboration
  • Portable content blocks

Sanity handles content modeling and content APIs.

2. Application Layer

Built with Next.js:

  • React Server Components
  • File-based routing
  • Streaming rendering
  • API routes (edge-compatible)

This keeps the frontend modern and scalable.

3. Edge Runtime

Using OpenNext, the app is adapted for:

  • Cloudflare Workers
  • Global edge execution
  • Low-latency rendering
  • Middleware at the edge

The result is distributed compute instead of centralized servers.

4. Deployment Flow

Deployment is simple:

  • Build frontend
  • Deploy to Workers
  • Deploy Studio separately
  • Configure environment variables

No proprietary infrastructure required.

Why This Matters

This architecture gives you:

  • Content flexibility
  • Infrastructure independence
  • Performance-first mindset
  • Clean separation between content and compute

It’s not just a starter — it’s a blueprint for edge-native applications.