Expertise / 05
Platform Engineering
Multi-tenant products built end to end as the sole engineer: accounts and roles, plans and billing, job queues, and isolation enforced by the database rather than by the interface.
2 platforms, all delivered
01 — Tools and stack
What this work is built on. Every tool below is part of at least one of the platforms further down this page. HoverTap a card to see what it is used for.
PostgreSQL
Data and isolation
Row-level security, so a query for another tenant’s data is refused by the database itself, and a job queue with claim, retry and dead-letter semantics.
Supabase
Data and isolation
PostgreSQL, its policies and edge functions. The model’s key lives in an edge function, never on the web server.
Prisma
Data and isolation
The schema as code: 21 models and 27 migrations in one product, counted on 2026-09-08.
Next.js
Application
The product itself, from the public pages to the authenticated screens, in one codebase.
TypeScript
Application
One language across the API routes, the background work and the interface.
Stripe
Billing and the outside world
Subscription plans, each carrying the limits that the product enforces.
Google Ads
Billing and the outside world
A production API integration: spend is ingested from it, and every mutation is validate-only unless a flag says otherwise.
02 — Delivered
AdWash — Autonomous Google Ads Management
Built as its only engineer: a multi-tenant product whose plans hold real spend to a ceiling, whose automation can undo itself and whose deploys assert their own outcome.
Just Grade Metrics — AI Call Quality Assurance
Row-level security on 31 tables, tested by attempting cross-tenant reads, and a PostgreSQL job queue with claim, retry and dead-letter semantics.
03 — Book a call
Building a product with accounts and billing?
Book a call to go through tenants, roles and plans, and what already exists.