Home
Stack

How we build

1Websites and web apps · items 1.1–1.4

Layer 1, web: sites and web apps
ItemComponentRoleNote
1.1TypeScriptLanguageOne typed language from the browser to the edge.
1.2SvelteInterfaceInteractive UI with a small runtime.
1.3AstroSitesStatic-first pages that load fast.
1.4Tailwind CSSStylingA constrained, shared design vocabulary.

2Mobilephones and tablets · items 2.1–2.3

Layer 2, mobile: phones and tablets
ItemComponentRoleNote
2.1SwiftLanguageNative code on Apple platforms.
2.2SwiftUIInterfaceDeclarative iPhone and iPad interfaces.
2.3Cross-platform appsReachOne codebase where native is not required.

3Cloud and datahosting, storage, analysis · items 3.1–3.4

Layer 3, cloud and data: hosting, storage, analysis
ItemComponentRoleNote
3.1CloudflareEdgeHosting, functions and DNS close to users.
3.2SupabaseBackendAuth, storage and Postgres, managed.
3.3PostgreSQLDatabaseThe relational core.
3.4BigQueryWarehouseAnalytics over large event data.

4Product practicehow we decide and ship · items 4.1–4.5

Layer 4, product practice: how we decide and ship
ItemComponentRoleNote
4.1PostHog analyticsMeasureDecisions from behaviour, not guesses.
4.2Agent orchestrationBuildMany agents in parallel, directed by one engineer.
4.3Agent review and testsCheckAgents review each other’s work; tests and checks gate every change.
4.4Engineer approvalDecideA person approves everything that ships.
4.5Continuous deploymentShipSmall changes, released as soon as they pass.

Fig. 1 — The stack, exploded: four layers, sixteen parts.

The process behind layer 4, step by step