# Cloud Run compared with other platforms

> Cloud Run next to a VPS, DigitalOcean, Netlify and AWS, and the databases a Cloud Run app can use, with prices and what each choice leaves out.

<https://exodus.elim.io/blog/topic/compare>

These guides put Cloud Run next to the other places an app can run: a VPS, DigitalOcean App Platform, Netlify and AWS, and the databases a Cloud Run app can sit on. Each one prices the same app on both sides, names what each platform does that the other does not, and says when staying where you are is the better answer.

- [Cloud SQL, Firestore or a serverless Postgres: choosing the database for a Cloud Run app](https://exodus.elim.io/blog/cloud-sql-firestore-or-serverless-postgres.md): The database sets the floor of a Cloud Run bill: Cloud SQL from $9.37 a month, Firestore per document, or a serverless Postgres on another cloud. Costs, connections and code for each.
- [How fast Cloud Run wakes up: cold starts, measured](https://exodus.elim.io/blog/cloud-run-cold-start-measured.md): An idle Cloud Run app stops, and the next visitor waits for a start. What a study across eight platforms measured, what 703 of our own starts took, and how to measure and shorten yours.
- [Cloud Run or a VPS: which one costs less](https://exodus.elim.io/blog/cloud-run-or-a-vps.md): A VPS bills the month; Cloud Run bills the seconds your code runs. Worked prices for a small app, a busy one and a steady one, and what each price leaves out: database, egress, disk, your time.
- [Moving an app from DigitalOcean App Platform to Cloud Run](https://exodus.elim.io/blog/digitalocean-app-platform-to-cloud-run.md): App Platform bills each container all month with a traffic allowance; Cloud Run bills while requests run. What each part of the app spec becomes, the commands, and the bill on both sides.
- [Moving a small web app from AWS to Cloud Run](https://exodus.elim.io/blog/from-aws-to-cloud-run.md): App Runner takes no new customers, Lambda needs an adapter and Fargate bills all month. What each AWS piece becomes on Google Cloud, a small app's cost on each side, and the move in six steps.
- [Moving a Netlify site to Firebase Hosting and Cloud Run](https://exodus.elim.io/blog/netlify-to-cloud-run.md): A Netlify site moves to Firebase Hosting for files and one Cloud Run service for code. An adapter for unchanged functions, _redirects as firebase.json, schedules, secrets, the domain, both bills.