Launch offer — first 20 buyers:EARLYBIRD −$30

Ship the enterprise React app, skip the plumbing

Cliore is a production-ready React SPA starter with authentication, architecture, testing, and CI/CD already wired together and documented — so your first commit is a feature, not setup.

~/work — day one
unzip cliore.zip && cd cliorenpm i && npm run dev  vite 8 ready in 312 ms  ✓ Keycloak realm connected — roles: admin, user  ✓ 300+ tests · ~99% coverage · CI green  ➜ local: http://localhost:5173git commit -m "feat: my first feature"  ← not "chore: setup"
React 19MUI 9Router 7Keycloak 26TypeScript 6Vite 8~99% coverage300+ tests

what's inside

Everything an enterprise SPA needs

Nine pieces of foundation, each wired to real services and covered by tests — not placeholders you have to finish.

Keycloak auth + RBAC

OIDC login, silent token refresh, and route- and component-level role guards wired to a real Keycloak 26 realm — not a stub.

Feature-Sliced Design, enforced

app → pages → widgets → features → entities → shared, with ESLint boundary rules that fail the build on illegal imports.

RTK Query + MSW

Typed data layer with caching and invalidation; MSW handlers run UI and tests without a live backend.

i18n with react-intl

Message catalogs, locale switching, and formatting helpers set up end to end.

A real source tree

A documented codebase, not disconnected snippets.

MUI theme

Tokens, typography, and overrides read from one source.

Tests + Storybook

Vitest + Testing Library with an enforced gate, Playwright E2E against a real Keycloak, Storybook review.

CI/CD + gated release

Every PR runs the full pipeline; releases are versioned and gated.

Deploy matrix

Documented paths — pick a target and ship without reverse-engineering the build.

Observability, SEO & docs

Error boundaries and logging hooks, sensible SEO defaults, and written docs covering every layer of the starter — 22 pages and counting.

~99%
test coverage
300+
unit tests
39
Storybook stories
22/24
Node CI matrix
en · es
i18n out of the box
22
docs pages

see inside

A real app and a real codebase

Cliore is a running application and a documented source tree — not a folder of disconnected snippets. Here's what you get.

who it's for

Built for people shipping real apps

Solo devs & founders

Skip weeks of setup and ship your MVP on a foundation that already handles auth, state, and CI.

Agencies & freelancers

Start every client project from the same audited baseline — consistent structure, faster delivery.

Teams standardizing

Adopt one enforced architecture (FSD + ESLint boundaries) so a growing codebase stays maintainable.

the stack

Built on the newest GA majors

Cliore targets current, supported versions so you inherit today's APIs and a long support window — not a migration backlog.

Reactv19
The latest GA with the new compiler-ready APIs and Actions.
MUIv9
Enterprise component library, themed from one token source.
React Routerv7
Modern data-router setup with typed routes.
Keycloakv26
Battle-tested OIDC auth with PKCE and silent SSO.
TypeScriptv6
Strict mode across every layer, no implicit any.
Vitev8
Rolldown-powered builds and instant HMR in dev.

architecture

Feature-Sliced Design, enforced

Layers flow in one direction — higher layers may import lower ones, never the reverse. ESLint boundary rules keep it that way as the codebase grows.

src/ — Feature-Sliced structure
src/
├─ app/       providers, router, store
├─ pages/     route-level screens
├─ widgets/   composed UI blocks
├─ features/  user actions + model
├─ entities/  domain models + api
└─ shared/    ui, config, lib
appProviders, routing, global config — the composition root.
↓ imports ↓
pagesRoute-level screens assembled from widgets and features.
↓ imports ↓
widgetsSelf-contained UI blocks composed for a page.
↓ imports ↓
featuresUser-facing actions with their own UI and logic.
↓ imports ↓
entitiesBusiness domain models and their data access.
↓ imports ↓
sharedReusable UI, config, and utilities with no upward imports.

the math

Cheaper than the time you'd spend

Wiring enterprise auth, architecture, and CI by hand is weeks of the least valuable, most error-prone work — before you ship a single feature. Here's the trade-off.

Build it yourselfStart with Cliore
Time to a working app3–6 weeks of plumbingRunning in minutes
Keycloak auth + RBACDIY, easy to get wrongWired to a real realm
ArchitectureEndless bikesheddingFSD, boundary-enforced
Tests & CISet up from zero~99% covered, gated
CostYour salaried weeksFrom $49, one-time

pricing

One-time purchase, yours to keep

Buy once, download the full source, and use it across your projects. No subscription.

PopularStandard
$79 one-time

Most teams

  • Complete source code
  • Use in unlimited projects
  • 12 months of updates
  • Email support
Get Standard
Pro
$149 one-time

Studios & agencies

  • Everything in Standard
  • First premium theme free on release
  • Priority email support
Get Pro

First 20 only — use code EARLYBIRD for Standard at $49 (save on $79)

Secure checkout via Lemon Squeezy · instant download · VAT handled · the full source is yours to keep

faq

Questions, answered

What license do I get?

A permissive license to use and modify the source in your own products. You may not resell or redistribute Cliore itself as a competing starter. Full terms ship with the download.

What's included?

The complete source for the starter: auth, Feature-Sliced structure, data layer, MUI theme, i18n, the test suite, the CI/CD pipeline, and written documentation for each layer.

Do I get updates?

Yes. Early and Standard include updates within the current major version; Standard adds a full year of updates and Pro extends coverage across your organization. You keep everything you have downloaded.

Which versions does it target?

The newest GA majors: React 19, MUI 9, React Router 7, Keycloak 26, and TypeScript 6 — so you start on current, supported foundations.

Can I get a refund?

Because this is downloadable source, sales are final. If something is broken or not as described, contact us and we will make it right.

Your first commit should be a feature

See the running app, then get the source and build your product instead of its scaffolding.

$ git commit -m "feat: the thing you were hired to build"