What this is
Your Supabase project already knows everything about your product. Who signed up, what they touched, when they stopped. Getting that out of Postgres and into a shape somebody can answer questions with is a different job, and most of the writing about it is either a vendor diagram or a tutorial that stops at “and now you have data in your warehouse.”
So we are building ours in public, on camera, one layer a week. Supabase Postgres, Supabase Pipelines into BigQuery, models on top, and the numbers our own go-to-market people ask for on Mondays. You get the working parts and the parts where we got it wrong.
Eight episodes after this one. Episodes 1 to 3 are out; the rest land weekly.
Who it is for
You run a product on Supabase and someone has started asking for numbers you cannot produce. Or you are weighing a warehouse and want to see the constraints before you commit to one. Or you already have the pipeline and the numbers still feel untrustworthy.
If you already run a modelled warehouse with a tested collection layer, this will be too basic. Skip to episode 8, which is the one about what breaks.
What you will have at the end
A publication you wrote on purpose, replicating into BigQuery. Models that answer defined activation, account-health and expansion questions. Plus worked examples of migrations and data-contract changes to test in your own chain.
The shape of it
The pull request changes the schema before replication begins. The database records what happened, Pipelines moves it, BigQuery models it, and your GTM tools act on the result.
Episode 1 covers the chain, episodes 2 to 4 build it, 5 to 7 use it, and 8 is about what breaks it.
Why we are doing this on camera
Two honest reasons. The first is that we needed the stack. We build Skene, which reviews tracking changed in pull requests and can run deterministic plan-versus-scan checks through separate API or MCP paths. We could not answer basic questions about our own product because our collection layer had gaps. Building it in public was cheaper than building it twice.
The second is that this stack is new enough that the write-ups do not exist yet. Pipelines is in public alpha as reviewed 16 September 2026. The BigQuery destination has real constraints (primary keys, replica identity, no type changes) that you find out about by hitting them. If watching us hit them saves you an afternoon, the series has done its job.