Est. 2026The full archiveBuilt by the Layerbase team
Project Next App
Essays on the machinery behind software: the AI that increasingly writes it, the SaaS that sells it, the databases that remember it, and the startup culture that keeps insisting it is all normal.
RSS feed ↗9 posts in the archive
Previously, on the blog
The PingCAP breach: the control plane took the keys
Someone walked into PingCAP with stolen accounts for a month. The databases held. The keys, the query history, and the org records did not.Turso is going to Supabase. Now watch the pricing.
Supabase is buying Turso. What consolidation means for a beloved free tier, and why waiting for the new plans is not a plan.Tiny teams, expensive distribution
AI lets a three-person team build like twelve, but being found, believed, and bought costs what it always did, and it eats the freed margin.The stack monoculture
Almost every new web product is Next and React and Postgres and Tailwind. The sameness is load-bearing and it also has a price worth naming.Your pricing page is the roadmap
Seats, events, and AI credits quietly became plan walls, and those walls now decide what products can do, so the pricing page is the roadmap.Your AI wrapper is really a workflow
Strip away the model and the product still stands: the schema and the state machine and the human checkpoints are the durable part.Postgres is eating the stack
Postgres quietly absorbed the queue, the search engine, and the vector index, and the honest case for where to stop is worth more than the hype.The PR review is the bottleneck
AI agents moved the bottleneck from writing code to reading it. Review throughput is now the constraint on shipping and most teams have not noticed it.