Platforms & products
The platform we run our own company on
We run our own company on a platform we built ourselves, which is the clearest proof that we build the kind of software we describe.
Formulation Labs runs on a custom platform we built ourselves, the same kind of architecture we build for clients, with a public site, a client portal, and a shared package layer underneath.
- Turborepo
- Next.js 16
- TypeScript
- Supabase
- Cloudflare
- PostHog
- Playwright
The most honest case study a builder can show is the one it runs itself. Rather than stitch together off-the-shelf tools, we put the firm on a custom platform of our own: a single codebase that powers both the public website and the private client portal, sharing one design language, one data layer, and one set of tested building blocks. It is the same architecture we bring to client work, which means we feel every decision before we ever recommend it.
Two very different surfaces, a public marketing site and a private client application, had to share one codebase, one design language, and one set of components without bleeding into each other.
Everything had to be reusable, so a building block written once is shared cleanly rather than copied.
The public site is live and must never break, so changes ship through a build and preview gate before they reach production.
It had to be the proof of the firm's own standards, not a shortcut, which meant real tests and real architecture.
Built a Turborepo monorepo that holds two applications, the public marketing site and the private client portal, on a shared foundation.
Factored common work into eleven shared packages covering brand and design tokens, UI, data, domain logic, integrations, background jobs, AI, widgets, auth, and a testing layer.
Wired the public site to deploy automatically on every merge, behind typecheck, lint, and end-to-end Playwright gates so a broken change cannot reach the live domain.
Instrumented the platform with product analytics and session insight, so the firm measures its own funnel the way it measures a client's.
Outcomes
A public marketing site and a private client portal run from a single monorepo, sharing one design language and one data layer.
Eleven reusable packages, from design tokens to auth to background jobs, mean a capability is built once and shared cleanly across the platform.
The firm operates on its own platform, which is the clearest evidence that we build the kind of architecture we recommend.