Our story

Why nertia exists — recipes, portability, and aligned incentives.

A site is a recipe — three parts combined:

  • Pattern (fractal) — how things are arranged. The same idea repeats at every scale: a section has a layout (hero vs. split), a page is a layout of sections, a site is a layout of pages.
  • Skin — a tokenized design system you build and apply. Skins are CSS variable overrides on a shared design base, not component rewrites, so any skin works with any pattern.
  • Content — your actual copy, links, and media. From the builder UI, a nertia.md file, or a spreadsheet.

A recipe is pattern + skin + content — the complete, portable spec for a site. The editor reads and writes it; the renderer renders it. One format, every input. A section is one functional content block (hero, pricing, contact).

Why this matters

Most site builders optimize for retention, not ownership. Structure lives inside a proprietary editor. Export is an afterthought. Pricing drifts toward extraction once the product matures.

nertia flips that. The recipe is the site. Export is first-class. The core builder stays free.

AI is the frosting, not the cake

The recipe carries the site; AI carries only the polish. Standards, shared compositions, and your content are the cake. AI helps refine — it does not reinvent the stack on every prompt.

Keep reading

Our story — docs