All writing
SaaS Systems: Architecture, Cost and Simplicity
Field notes and decision frameworks connecting backend cost, cloud choices and product complexity as one systems problem.
Parts are listed in the recommended reading order.
Why does a SaaS Supabase bill get out of hand?
What makes a backend service expensive is rarely the pricing table — it is how your application talks to it.
Supabase or Cloudflare? Infrastructure decisions for small products
The useful question is not which platform is better, but which complexity the product actually needs today.
10 signs your startup needs simplification, not another feature
Growth does not always mean adding. Sometimes the biggest obstacle is the accumulated weight of what already exists.
What 2.6 million Ordovia requests taught me about SaaS architecture
The request volume was not only a billing issue. It was an architectural signal that network behavior was not visible enough.