# Cloud Run basics

> What Cloud Run is, the three shapes code takes there, regions, concurrency, buildpacks or a Dockerfile, and a Google Cloud project for a small team.

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

Start here if you have never deployed to Cloud Run. These guides explain what the service runs and how it bills, which shape your code takes as a service, a job or a worker pool, how many requests one instance serves, which region to pick, how the container gets built, and how to set up the project a small team works in.

- [Buildpacks or a Dockerfile: how to get your code into a Cloud Run container](https://exodus.elim.io/blog/buildpacks-or-a-dockerfile.md): One command builds your Cloud Run container with Google's buildpacks or your own Dockerfile. What each does, what it costs, who patches the OS, what breaks, and the commands for both.
- [Choosing a Cloud Run region: latency, price tiers and what each region has](https://exodus.elim.io/blog/choosing-a-cloud-run-region.md): A Cloud Run service lives in the region of its first deploy. What that decides (latency, a 20 to 40% price gap, nearby products, where data stays), how to measure it, and how to move later.
- [Cloud Run services, jobs and worker pools: which shape your code takes](https://exodus.elim.io/blog/cloud-run-services-jobs-and-worker-pools.md): Cloud Run runs a container as a service, a job, a worker pool or a Preview singleton. What each is, how it bills, the commands, and which one each part of a PaaS app becomes.
- [Concurrency on Cloud Run: how many requests one instance takes](https://exodus.elim.io/blog/concurrency-on-cloud-run.md): One setting decides how many requests share a Cloud Run instance. What it limits, how the autoscaler reads it, why your web server decides the real number, and its effect on the bill and database.
- [Planning a new product for Cloud Run before you write it](https://exodus.elim.io/blog/planning-a-new-product-for-cloud-run.md): The decisions to make before writing a product for Cloud Run: where state lives, the database, background work, payments, live updates, the region, and the bill at launch, in a year and busy.
- [Reading your first Google Cloud bill](https://exodus.elim.io/blog/reading-your-first-google-cloud-bill.md): A first Google Cloud bill is a statement that arrives after the charge, with many $0.00 lines. How it is built, when you are charged, how to check a line yourself, and what credits are.
- [Request-based or instance-based billing on Cloud Run: which one to pick](https://exodus.elim.io/blog/request-based-or-instance-based-billing.md): A Cloud Run service bills only while it handles requests, or for every second an instance lives. What each charges for, what the CPU does between requests, where costs cross, and how to switch.
- [Setting up a Google Cloud project for a small team](https://exodus.elim.io/blog/setting-up-a-google-cloud-project-for-a-small-team.md): The first hour on Google Cloud in order: organization, billing account, a project per environment, budget and cap, APIs, group roles, keyless service accounts, contacts. Costs and traps.
- [The Cloud Run free tier, explained: what is free, how far it goes, what ends it](https://exodus.elim.io/blog/the-cloud-run-free-tier-explained.md): Cloud Run gives each billing account $4.32 of CPU, $0.90 of memory and 2 million requests a month. What that buys, who shares it, what quietly uses it up, and how to read what is left.
- [What Cloud Run is, for someone who has never used it](https://exodus.elim.io/blog/what-cloud-run-is.md): Cloud Run runs your container and bills for the seconds it works. What it runs, its three shapes, how it bills, what changes in your code, cold starts, what it does not do, a first deploy.