Watch the credit math: deploys cost 15 credits each out of 300.
- Why it fits
- Static sites and frontend apps that deploy from Git and want a generous, mature workflow.
- How deploys work
- Connect the Git repo; pushes build and deploy automatically with previews for every pull request.
- The tradeoff
- The credit system makes bills hard to predict — traffic, deploys, and compute all drain one pool.
- The managed database bills on top of this estimate.
A small app can stay inside the monthly allowance; it pauses if any enforced Free limit is exhausted.
- Why it fits
- JavaScript and TypeScript sites, full-stack framework apps, and APIs that benefit from built-in previews, databases, cron, caching, and telemetry.
- How deploys work
- Connect GitHub for builds on every push or run deno deploy from the CLI; framework presets configure common JavaScript stacks automatically.
- The tradeoff
- It runs the Deno runtime, not Node itself, and its two-region managed footprint and metered Active CPU, memory, and egress trail broader competitors for heavy traffic.
- The managed database bills on top of this estimate.
Includes 50 GiB of outbound transfer; billed per second.
- Free option
- Free tier: 3 apps with static sites, 1 GiB of outbound transfer each per month. Extra static-site apps cost $3/month.
- Why it fits
- Apps that want git-push deploys inside a provider they can grow with.
- How deploys work
- Connect the Git repo or a container image; App Platform builds, deploys, and scales it.
- The tradeoff
- Weaker compute per dollar than a Droplet — the convenience premium is real.
- The managed database bills on top of this estimate.
