Templates

Start from a real app

Gold path is saas and admin — auth, SQLite, Items and Team. Store and landings are composed catalog (same add-page / upgrade loop, no live auth). Gontify and Portfolio are showcase starters.

bunx create-cronus-app my-app --template saas

Landing pages

Named marketing looks composed from the same blocks as landing — catalog compose, not the saas gold path. Swap the stack, keep the upgrade path.

Ops

Workflow product

Composed catalog

Aurora · dark

Split hero with a quality panel, logo cloud, feature grid, integrations, and a banner CTA.

What's inside

hero--split + integrations grid
Aurora theme, dark mode
Navbar + footer chrome from the registry

$ bunx create-cronus-app my-app --template landing-ops

Secure

Infra / encryption

Composed catalog

Midnight · dark

Compact registry hero, metrics, proof, usage-based pricing, split FAQ, and CTA.

What's inside

hero--compact + pricing--usage + faq--split
Midnight theme, dark mode
Stats and testimonial grid for trust

$ bunx create-cronus-app my-app --template landing-secure

Coverage

Global services

Composed catalog

Sunset · light

Centered hero, stats, testimonial grid, FAQ, CTA. Sunset light.

What's inside

stats + testimonials--grid
Sunset theme, light mode

$ bunx create-cronus-app my-app --template landing-coverage

Broadcast

Studio / show

Composed catalog

Aurora · dark

Atmospheric hero, marquee logos, features, testimonials, pricing. Aurora dark.

What's inside

hero--atmosphere + logo-cloud marquee
Aurora theme, dark mode

$ bunx create-cronus-app my-app --template landing-broadcast

Every template prompts for (or accepts) --theme and --mode, bakes your pick into the app, and ships a cronus-ui.json so the registry CLI works from the first commit.

Keep building

Grow the app after you scaffold

Add a route with cronus-ui add-page, switch presets with theme set, or pull a single primitive with add. Upstream fixes land through upgrade without wiping local edits.

CLI docs Browse blocks