Get started
How-to guides
Reference
Concepts
Self-host gallery
AppendixWhat carries over from Cloud Run
The same container image
A Cloud Run service is an image that listens on a port. Deploy that image from a registry, with a registry credential for private ones. No rebuild is needed.
Revisions become deploys
Every deploy is recorded with its image and status. Prior images stay pinned, so rolling back switches to an image that is still there.
Logs and metrics included
Logs with search, request rate, error rate and latency percentiles are stored on your node. Nothing is billed by volume.
When moving makes sense
The service is up all day with steady traffic, so you pay for compute around the clock on Cloud Run anyway. You run several services and could put them on one server, which spreads a fixed price across them. You want logs, metrics and data on machines you control, or you are tired of a bill that moves with traffic. You are comfortable patching a Linux host, watching disk space and testing restores, or you have someone who is.When to stay on Cloud Run
Traffic is spiky or rare. Scale to zero and per request billing are hard to beat, and Levelrail has no autoscaling. You need capacity to appear in seconds under load, or to span zones or regions without building it yourself. You depend on Google identity and networking features such as workload identity or private connectivity to other Google services. Nobody wants to be on call for a server. Moving trades a bill for operations work.What to know before you try it
Levelrail is self-hosted and early. It is in beta, there is no stable release yet, and the feature status page says which parts are proven and which are not. You operate the server. OS updates, the Docker daemon, disk space, backups and restore tests are your job. A single server is a single failure domain. Levelrail does not run on Cloud Run and does not manage Google Cloud resources. It runs on Linux machines you provide, including VMs rented from any provider. Run it next to Cloud Run first and compare real numbers. The migration guide has a shadow run checklist.A cost model, with the assumptions written down
Estimates for one service with 1 vCPU and 0.5 GiB of memory for a 30 day month, using Cloud Run prices for Tier 1 regions such as us-central1, read from Google’s public pricing page on 2026-10-11. Prices change, and your region may be in another tier. Check the page before you decide. Egress, load balancers, Artifact Registry, Cloud SQL and your own time are excluded on both sides.
Read the Cloud Run migration runbook
From Cloud Run to your own server
1
Export the service definition
gcloud run services describe with the export format gives one YAML with the image, port, env, resources and probes.
2
Deploy the image to Levelrail
Create a registry credential if the image is private, set env and secrets, and check readiness on a temporary address.
3
Move data and DNS
Dump Cloud SQL, restore into a managed database, lower TTLs, switch, and keep Cloud Run as the fallback until you trust the new setup.
Frequently asked questions
Can I deploy my existing Cloud Run image unchanged?
Can I deploy my existing Cloud Run image unchanged?
Usually yes. Point Levelrail at the image and the port your container listens on, and set PORT as an env var if your app reads it. A private Artifact Registry image needs a registry credential.
Does it scale to zero or autoscale?
Does it scale to zero or autoscale?
Not like Cloud Run. Replicas are fixed. An app can be put to sleep after a quiet period and woken on the next request, which is slower than a Cloud Run cold start.
Is there an importer for Cloud Run?
Is there an importer for Cloud Run?
No. The runbook maps each Cloud Run concept to its Levelrail equivalent and lists what has none.
What does it cost?
What does it cost?
The software is free under Apache 2.0. Your cost is the servers you run it on, plus your time operating them.