Colophon

What's under the hood of this site, and who made the parts possible.

Every Lionshead product carries a small powered by Lionshead link in its footer. If you clicked one, that's how you got here. This is the same answer for every product we ship, starting with the site you're reading now.

The stack

Framework: Next.js 16 on React 19. Public pages prerender at build time; a small Node-runtime surface gates internal routes.
Styling: Tailwind CSS v4, configured from a five-value design-tokens.json at the repo root.
Type: Inter (variable) for sans, JetBrains Mono for monospaced accents. Both via next/font, self-hosted.
Content: MDX via @mdx-js and @next/mdx. Syntax highlighting from rehype-pretty-code on top of Shiki.
Auth: Firebase Auth for the sign-in that gates internal routes. @octokit/auth-app for server-side GitHub App tokens.
Hosting: Vercel. Marketing pages from the CDN; serverless functions back the authenticated surface.
Observability: Sentry for errors. Vercel Web Analytics for aggregate page views. No third-party tracking, no session replay, no advertising pixels.
Tests: Vitest for unit and integration. Playwright for end-to-end. Both run in CI on every PR.
Mark: A minimal geometric L. Restraint as visual identity.
Method: Specs and stories scaffolded with BMAD; Claude Code does the keystrokes; Allen runs the room.

Open source we lean on

None of this exists without the people who wrote the libraries. Naming them is the least we can do. The full dependency tree is much longer; this is the meaningful surface, the work we'd notice if it went away.

next · MIT
react · MIT
tailwindcss · MIT
@mdx-js/react · MIT
react-markdown · MIT
rehype-pretty-code · MIT
@sentry/nextjs · MIT
firebase · Apache 2.0
@octokit/auth-app · MIT
gray-matter · MIT
js-yaml · MIT
vitest · MIT
@playwright/test · Apache 2.0
next-themes · MIT

Our promises

A stack tells you what we built with. A promise tells you what we won't do with it. The four things we will not change, on any Lionshead product, are written out in plain language at House Rules. Lifetime price freeze. No ads. No selling your data. One-tap account and data deletion.

From Allen

I spent 15 years watching software get built badly. Most of the failures weren't mysteries. Nobody wrote tests. Nobody wrote docs. Nobody knew which version was in production. Nobody could roll back. Nobody owned the database. The post-mortems were all the same post-mortem.

I built Lionshead to take those failure modes off the table on day one, before there are any customers to disappoint. Showing you the stack is part of that. If the parts list is honest, the rest of the work probably is too. If the parts list is hidden, draw your own conclusions.

AI-assisted development is the other half. I ship as a solo operator because Claude Code does the keystrokes while I run the room. Ten years ago, a one-person company couldn't carry this much infrastructure. Now it can. That changes what a small company is allowed to be.

If you want to know whether a Lionshead product is built the way I say it is, this page is the start, and the House Rules are the contract. Dig in.

← Home