v1One CLI, all the boilerplates —Read the manifesto
boila

Search the catalog

Find a boilerplate by name, stack, or body content.

Manifesto

Pick a starter.
Stop the bookmark
graveyard.

Every dev keeps a Notion page of starters they'll someday try. Most never get opened twice. Boila is a curated registry plus a single command — pick the thing, scaffold it, ship it.

  1. 01

    One CLI, one registry

    Every framework ships its own create-* command. They all do the same thing, none of them know about each other. Boila collapses that surface into a single, curated catalog and a single command.

  2. 02

    Curation is the moat

    Scraping GitHub for trending starters produces noise. The value of Boila is the editorial pass — a maintainer checked that the install path works, the license is permissive, and the intent is distinct from existing entries.

  3. 03

    Indexed by intent, not just by stack

    Most people don't pick a boilerplate by framework anymore. They pick by what they're shipping — a SaaS, a landing, an API. The taxonomy reflects that.

  4. 04

    Static all the way down

    No backend. No database. No auth. The registry is files in this repo. PRs are the contribution gate. The site is HTML, the search is local, the CLI talks to a static JSON.

Where to next

The catalog grows when you contribute.

Boila is community-curated. If you maintain a starter that passes the bar, send it through. The PR template walks you through it.