UI system
UI componentsTheme systemReusable UI blocks

UI system

Reusable UI blocks

Production-shaped landing, application shell, account and checkout blocks composed from the starter components.

Editorial landing system+−
Runtime Canary
Production starter

Build the product, not its plumbing.

A precise fullstack base with a complete UI system and one contract across every interface.

Contract first

Schemas, clients and transports stay aligned.

Production data

Prisma and PostgreSQL are ready from day one.

Every surface

HTTP, realtime, MCP, agents and CLI share one service.

The repetitive work

Keep infrastructure from becoming the product

01

Schema drift

One named Zod schema drives server validation and every client.
02

Transport duplication

HTTP, tools and CLI share the same implementation.
03

Frontend plumbing

Queries, realtime cache updates and errors arrive composed.
Built for product teams

A neutral foundation, not a sample business

Replace the example domain while retaining contracts, runtime boundaries, operational tooling and the complete component vocabulary.

Solo developers and teams

Why this topology

Clear ownership at every boundary

Validated boundaries

Fail-first environment and data parsing.

Persistent by default

Prisma and PostgreSQL with a real migration.

Independent backend

Long-running work, sockets and MCP stay outside Next.

Typed navigation

Contracts build calls and URLs without repeated strings.

Contract first

Schemas, clients and transports stay aligned.

Production data

Prisma and PostgreSQL are ready from day one.

Every surface

HTTP, realtime, MCP, agents and CLI share one service.

Start

Generate a complete system and learn it through one bounded domain.

Adapt

Keep the boundaries and replace fixtures with your own product model.

Scale

Split deployments without rewriting the contract or transport surface.

Learn by tracing one operation

Follow a project mutation from schema to contract, service, HTTP client, query cache, Socket.IO event, MCP tool and CLI command.

  1. 1Define a named schema
  2. 2Reference it from a thin contract
  3. 3Implement the domain once
  4. 4Consume the generated surfaces

Theme-aware media

A project shell ready to become yours

Light + dark
Theme-aware generic application preview

Frontend foundations included

React 19

Server-first composition and isolated client islands.

Responsive UI

Touch, keyboard and desktop interaction patterns.

Source components

Own and adapt every primitive without a black box.

Composable sections

From landing page to application shell

01

Editorial landing

02

Operational dashboard

03

Account workspace

04

Data-heavy admin

Flexible

Foundation

A reusable layout demonstrating pricing, comparison and conversion patterns.

Recommended

Product

A reusable layout demonstrating pricing, comparison and conversion patterns.

Flexible

Scale

A reusable layout demonstrating pricing, comparison and conversion patterns.

Runtime Canary · Built with StitchkitContracts · UI · Realtime · Tools
Application shell+−
Workspace
OverviewContentPeople

Dashboard

Overview

Live

Requests

12.8k

Users

1,284

Conversion

18.4%

Activity

Activity feed

Deployment completed2 minutes ago
Project contract updated18 minutes ago
New collaborator joined1 hour ago
Account flows+−

Sign in

Account workspace

Controlled presentation, no fake authentication

Checkout presentation+−
Secure checkout

Complete your order

Product foundation$99
Typed contract surface
Complete UI source
Production deployment profiles

Presentation only. Connect your own provider contract.

Inspect the foundation

The useful path stays short

Application code calls a typed client while validation, transport and observability remain framework-owned.

const snapshot = await api.repository.read();

await api.repository.refresh();
// The same operations are available to HTTP, MCP, agents and CLI.