~/setup
What I build with, and where it runs.
Every entry runs in something live or in my working week, and says where. Unless an entry says otherwise, I pay for it, use the free tier, or my employer provides it. Anything a company sends me is marked, and gets a verdict only after real use.
- liveruns in something in production
- in usein my working week, not shipped yet
- testingbeing tested now, no verdict yet
- retiredused, then dropped, and why
AI and agents
what does the reading for me · 1
- Claude Code live
Agents in my team's daily operations: incident triage, dead-letter queues, merge request review, release notes.
Read-only by default. The rule lives in the harness, not in a policy document.
Frameworks and tools
what the products are written in · 7
- Next.js live
The web apps of Futer and Luckybites.
- Expo in use
Futer's native iOS and Android apps, on the same backend as the web.
- Astro live
Static sites: Zyntral, and this one.
The page is HTML by the time it reaches the visitor.
- NestJS · Prisma live
Moodcycling's subscription backend, in a clean-architecture layout over Postgres.
- Vitest · Playwright in use
Tests for the flows in Futer that touch matches and, soon, money.
- GSAP · Lenis live
The motion and the smooth scroll on this site.
- Capacitor retired
Futer's first mobile packaging.
Replaced by Expo for the native apps.
Platforms and services
what the products stand on · 6
- Supabase live
Database, auth and storage for Futer and Luckybites.
Row-level security on every table: who can read what is decided in the database.
- Vercel live
Hosting for this site and for Zyntral.
- Cloudflare live
In front of Luckybites.
A promo going around the city is exactly when the site must not fall over.
- Stripe live
Moodcycling's recurring billing, behind an adapter the domain does not know about.
- Clerk live
Sign-in and accounts for Moodcycling.
- Mux live
Video delivery for Moodcycling's classes.
Operations
the day job, on a regulated platform · 3
Tracing production incidents, from the alert to the root cause.
- Kubernetes · ArgoCD live
Deploys across two clouds and four environments.
- RabbitMQ live
Messaging between services, dead-letter queues included.
Hardware
the desk · 0
Nothing listed yet. Hardware goes in after a few weeks of daily use, not on the day it arrives.
Building something that belongs on this list?
No affiliate links on this page.