Developer infrastructure without the conference talk

deployment platforms, managed databases and edge runtimes

The infrastructure market has consolidated around a handful of patterns: separate storage from compute, push the runtime closer to the user, and charge for what is consumed rather than what is provisioned. Each of those patterns solves a real problem and creates a new one, and the new one is usually on the invoice.

This site profiles deployment platforms, managed databases and edge runtimes, focusing on the operational consequences rather than the feature list. A platform that scales to zero is excellent until you need the first request after idle to be fast. A database with instant branching is excellent until the branches accumulate.

Each profile covers what the product does, how the pricing behaves once you are inside it, where it breaks down, and what leaving would cost. The last section is the one most reviews skip and the one that matters most when the contract renews.

Profiles

• Appwrite backend platform

  a self-hostable backend in one deployment

• Cloudflare Workers edge runtime

  V8 isolates at the edge and the consistency model that shapes them

• CockroachDB distributed SQL

  distributed SQL, quorum writes and multi-region cost

• Deno Deploy edge runtime

  TypeScript at the edge without a build step

• Fly.io edge application hosting
• Hasura GraphQL engine

  a generated GraphQL API and permissions as metadata

• Neon serverless Postgres
• Netlify frontend platform

  static deploys, build minutes and where the bandwidth goes

• PlanetScale MySQL platform

  MySQL on Vitess, branches and row-based billing

• Railway deployment platform
• Render unified cloud
• Supabase Postgres backend
• Turso edge SQLite
• Vercel frontend cloud

  the frontend cloud, and what its metered resources actually cost