Baseloop

The SaaS stack was costing $700–800+ a month and throttling the product: Supabase's 2XL tier at roughly $410, Trigger.dev Pro capped at 200 concurrent runs when the workload needed 1,000 — with another $160 in concurrency bundles, per-second compute charges, and invocation fees on top.

I led the move to self-hosted infrastructure on Coolify and Hetzner: Supabase on a dedicated CCX43, the Trigger.dev webapp on a CPX52, and four CPX42 workers — €205 a month, roughly 70% cheaper, now clearing 3,000+ concurrent runs with no artificial ceiling.

The migration ran against production — real users, real data, no downtime budget. That meant reading Trigger.dev's Go and TypeScript source when the docs ran out, and catching the failure modes nobody writes about: Postgres sequence resets, auth sessions that must survive the move, storage file permissions that don't.

Three open-source artifacts came out of that work: coolify-trigger-v4 (Docker Compose for distributed Trigger.dev v4 on Coolify, from single-server to multi-worker tiers), supabase-sync (an npm CLI that migrates schema, data, auth users with password hashes intact, storage, roles, and sequences — no forced credential resets), and latest-supabase-coolify-template (auto-generated JWTs and production Postgres tuning for 200–500 concurrent users and 10GB+ databases).

Alongside infrastructure I build the product itself in CedarJS — a TypeScript framework with Laravel-like conventions: GraphQL APIs, auth, jobs, and migrations, batteries included.