Best hosting for an API with a database
An API with a database is the workload where hosting bills surprise people, because the database often costs more than the compute. These picks favor platforms where the database is a first-class, managed part of the deploy.
The estimates cover the app process; every platform here bills the database separately, and the provider pages spell out what is known about those prices.
Render
Move to Standard ($25, 1 CPU / 2 GB) if 512 MB gets tight; a managed database adds more.
- Why it fits
- Apps and APIs that want git-push deploys with a fixed, understandable instance price.
- How deploys work
- Connect the Git repo; Render builds and deploys on push, with Docker support and instant rollbacks.
- The tradeoff
- The workspace-plus-services model means several line items, and bandwidth overage is pricey.
- The managed database bills on top of this estimate.
Railway
Roughly a quarter vCPU and 512 MB always on; a small database adds a few dollars.
- Why it fits
- Full-stack apps and APIs where you want the app and its database running in minutes.
- How deploys work
- Connect a repo or image; Railway detects the build, deploys it, and adds databases with one click.
- The tradeoff
- Pure usage billing means the bill moves with your traffic — predictable only while the app is small.
- The managed database bills on top of this estimate.
DigitalOcean App Platform
Includes 150 GiB of transfer; a managed database adds more.
- 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.
Ranked by ease of deploy for this stack, then by monthly cost — never by commissions. Your project isn't exactly this one? Answer four questions for a personal recommendation.