Overview
The original simple PaaS with a mature ecosystem and Postgres support. Heroku handles deployment and hosting, often with a global edge network and zero-config CI/CD.
What you get
Tools in this category turn a Git push into a running site or app, building, deploying, and serving from edge locations close to users. Expect previews per branch, custom domains, environment variables, edge functions, log streams, and analytics on traffic and performance.
Where it fits in your stack
They sit at the boundary between your repo and your users. Most teams pair them with a backend-as-a-service or managed database, plus a CDN/storage layer for assets. The “right” host often comes down to where your data lives and which framework you favour.
Who it’s for
Heroku is aimed primarily at builders looking for a focused tool in this space. When evaluating, look at framework support, build times on real projects, free-tier limits, region coverage, edge function constraints, and the egress/bandwidth pricing once you exit the free tier.
Pricing & licensing
Most providers in this category combine a free tier with usage-based fees for bandwidth, storage, and requests. Headline per-GB numbers rarely tell the full story, model your real traffic and asset volumes against Heroku’s pricing page before committing, and pay particular attention to egress fees once you grow past the free quota.