The self-hosted Cloud Run alternative
Levelrail vs Cloud Run: one binary, about 200 MB idle, Apache 2.0.
Levelrail control plane memory, idle, measured
~200 MB
- Install
- 1 binaryplus one agent per extra node
- License
- Apache 2.0one edition, no license key
- Ahead on
- 10 of 38capabilities, per Cloud Run's docs
The memory figure is one idle measurement of the Levelrail control plane (method). As of 2026-11-18.
What you gain over Cloud Run
10 capabilities where Levelrail is a plain yes and Cloud Run's own docs say partly or no. Full wording and sources are in the table.
All 38 capabilities
Statuses for Cloud Run are what its own documentation states; "Not stated" means its docs do not say. For Levelrail, "Active" means the feature ships today, with beta and stable tags from the feature status page and the exact scope in each note.
- Levelrail
- YesActive
- Cloud Run
- YesPartlyNo
A rule marks the 10 rows where Levelrail is ahead.
| Capability | Levelrail | Cloud Run |
|---|---|---|
| Architecture 3 | ||
| No SSH: agents dial out | Yesbeta Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out | Not applicable |
| Level-triggered reconciler with status reasons | Yes Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons | Not applicable |
| Single control plane binary | Yes One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary | Not applicable |
| Observability 3 | ||
| Metrics and log search built in | Yes Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in | Yes Automatic Cloud Monitoring metrics; logs in Cloud Logging Source for Cloud Run, Metrics and log search built in |
| Crashloop diagnosis with last log lines (Levelrail ahead) | Yes Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines | Partly Troubleshooting guide; logs checked manually, no automatic crashloop view Source for Cloud Run, Crashloop diagnosis with last log lines |
| Public status page | Yesstable Opt-in public page with components, 90 day uptime bars, incidents, maintenance and RSS Source for Levelrail, Public status page | Not stated in their docs |
| Deploys 10 | ||
| One-click rollback with pinned images | Yesstable Prior images pinned so cleanup cannot remove them. A 5xx spike or crashloop after cutover rolls back automatically (live-tested); the latency signal is beta Source for Levelrail, One-click rollback with pinned images | Yes Traffic rolls back to a previous revision immediately Source for Cloud Run, One-click rollback with pinned images |
| Readiness-gated deploys (zero-downtime on one node) (Levelrail ahead) | Yes Cutover only after the readiness probe passes. Live-tested on one node; multi-node is beta Source for Levelrail, Readiness-gated deploys (zero-downtime on one node) | Partly Gradual rollouts and traffic splits; health gating of cutover not stated Source for Cloud Run, Readiness-gated deploys (zero-downtime on one node) |
| Preview environments per pull request (Levelrail ahead) | Yesstable Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request | Partly Revision tags give separate URLs without traffic; no PR previews Source for Cloud Run, Preview environments per pull request |
| Docker Compose apps | Active Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps | Partly gcloud run compose up deploys a Compose file as one multi container service (supported subset of fields, secrets map to Secret Manager, volumes to Cloud Storage, max instances 1 by default); Google recommends Terraform for production Source for Cloud Run, Docker Compose apps |
| Git push deploys from GitHub, GitLab, Bitbucket | Active GitHub, GitLab, Bitbucket and Gitea documented; GitLab and Bitbucket previews are beta (synthetic webhooks). A git push remote on your own server (no provider needed) is beta Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket | Yes Developer Connect covers GitHub, GitLab, Bitbucket; Cloud Build covers GitHub Source for Cloud Run, Git push deploys from GitHub, GitLab, Bitbucket |
| Builds from source without a Dockerfile | Active Railpack detects Node, Python, Go and more. Ruby and PHP are accepted but only plan generation is verified, no live build; Rust, Deno and Elixir are rejected Source for Levelrail, Builds from source without a Dockerfile | Yes gcloud run deploy --source uses a Dockerfile if present, otherwise Google Cloud buildpacks (Go, Node.js, Python, Java, .NET, Ruby, PHP); deploy-without-build is Preview Source for Cloud Run, Builds from source without a Dockerfile |
| Scheduled jobs (Levelrail ahead) | Yes Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs | Partly Jobs can run once, on a schedule or in a workflow; delayed job execution is in Preview Source for Cloud Run, Scheduled jobs |
| Deploy freezes and policies (Levelrail ahead) | Yesstable Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploys Source for Levelrail, Deploy freezes and policies | Partly Binary Authorization policy lets Cloud Run deploy only images signed by trusted authorities, with allowlist patterns; freeze windows not stated Source for Cloud Run, Deploy freezes and policies |
| CI deploys with no stored secret | Active GitHub Actions only: a GitHub OIDC token is exchanged for a 15 minute token scoped to one app. Other CI uses an API token Source for Levelrail, CI deploys with no stored secret | Yes Workload Identity Federation lets GitHub Actions and GitLab CI jobs use their OIDC tokens for Google Cloud credentials, without service account keys Source for Cloud Run, CI deploys with no stored secret |
| Static site hosting | Yes Static HTML from git served by the embedded ingress with TLS; drag-and-drop folder or zip deploy Source for Levelrail, Static site hosting | Not stated in their docs |
| Data 3 | ||
| Managed databases with scheduled backups | Active Many engines, scheduled S3 backups. Postgres point-in-time restore is tested live; MySQL, MariaDB and MongoDB are beta Source for Levelrail, Managed databases with scheduled backups | Not stated in their docs |
| Point-in-time database restore | Active Postgres stable with an S3 compatible bucket; MySQL and MariaDB beta; MongoDB has no point-in-time restore Source for Levelrail, Point-in-time database restore | Not stated in their docs |
| Encrypted secrets for env vars | Yes Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars | Yes Secret Manager values injected as env vars or mounted volumes Source for Cloud Run, Encrypted secrets for env vars |
| Networking 4 | ||
| Private networking between apps or nodes | Active Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes | Partly Direct VPC egress reaches private IPs; internal DNS not documented Source for Cloud Run, Private networking between apps or nodes |
| Load balancing across replicas | Active Apps with more than one replica are round-robin balanced by default, with failed-replica skip and retry. The configurable balancer (health checks, sticky sessions, weights, drain) is experimental, behind a flag, verified on one machine only. HTTP only Source for Levelrail, Load balancing across replicas | Yes Requests balanced across regional instances automatically; multi region needs load balancer Source for Cloud Run, Load balancing across replicas |
| Request firewall, rate limits, bot protection (Levelrail ahead) | Yes Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection | Partly Cloud Armor filters traffic only through an external load balancer Source for Cloud Run, Request firewall, rate limits, bot protection |
| Automatic TLS certificates | Active Self-signed by default; public ACME (HTTP-01) has one recorded run on a live VPS. Renewal near expiry and DNS-01 wildcards are not exercised live; CAs needing EAB are unsupported Source for Levelrail, Automatic TLS certificates | Partly Domain mapping gives auto-issued and renewed Google-managed certs but is Preview and not recommended for production; global external Application Load Balancer is the recommended path. New Preview (Sep 28) custom URLs like example.cloud.run need no DNS or load balancer Source for Cloud Run, Automatic TLS certificates |
| Platform 11 | ||
| Multi-node | Activebeta Join, cordon and drain with real container relocation verified across two local Docker daemons; WireGuard mesh and cross-host transport still unverified. Resource-aware placement is beta Source for Levelrail, Multi-node | Not applicable |
| One-click service templates | Yesbeta 592 catalog entries, 583 active; 346 proven on a real engine, 246 previews without that pass yet Source for Levelrail, One-click service templates | Not stated in their docs |
| Autoscaling | Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling | Yes Scales on requests, events and CPU use; min and max instances; manual scaling available; custom CPU or concurrency utilization targets reached GA on 2026-09-29 Source for Cloud Run, Autoscaling |
| Sleep idle apps, wake on request | Yesstable Opt in per app; stops after 5 minutes to 7 days idle and wakes on the next request. Verified live against a real Docker daemon and the real ingress Source for Levelrail, Sleep idle apps, wake on request | Yes Scales to zero instances by default when there is no traffic Source for Cloud Run, Sleep idle apps, wake on request |
| CLI and HTTP API | Yes CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API | Yes gcloud CLI and Admin API manage services and jobs Source for Cloud Run, CLI and HTTP API |
| Deploy and alert notifications | Active Webhook and SMTP email have live e2e; 15 vendor kinds (Slack, Discord, PagerDuty and more) are beta, tested against local fakes Source for Levelrail, Deploy and alert notifications | Partly Cloud Monitoring alerts to email, Slack, webhooks, Pub/Sub Source for Cloud Run, Deploy and alert notifications |
| MCP / AI assistant integration (Levelrail ahead) | Yesbeta MCP server (beta) with over 240 tools in toolsets an agent enables on demand (256 at last count, 21 in the default session); in-app chat is behind a flag Source for Levelrail, MCP / AI assistant integration | Partly Remote MCP server (Streamable HTTP, OAuth 2.0 and IAM) deploys from images, source or zip and lists and inspects services; regional endpoints and the /deploy prompt are Preview; Cloud Audit Logs and optional Model Armor Source for Cloud Run, MCP / AI assistant integration |
| Runs on servers you own | Yes Runs on Linux servers you provide Source for Levelrail, Runs on servers you own | Not applicable |
| Open source license | Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license | Not stated in their docs |
| Declarative apply of the whole platform | Activebeta YAML export, plan and apply from CLI, dashboard, MCP or CI, plus a Terraform and OpenTofu provider. Experimental, behind a flag Source for Levelrail, Declarative apply of the whole platform | Partly Per service Knative YAML export and 'gcloud run services replace', plus Terraform google_cloud_run_v2_service; whole-platform apply is Terraform across Google Cloud Source for Cloud Run, Declarative apply of the whole platform |
| Functions and one-off jobs | Active Node, Python or Go handlers that sleep when idle and wake on the first request; scheduled and background calls with retries Source for Levelrail, Functions and one-off jobs | Yes Services plus Cloud Run jobs (up to 10,000 parallel tasks, schedule or workflow runs); sandboxes for jobs and worker pools in Preview Source for Cloud Run, Functions and one-off jobs |
| Security 4 | ||
| IAM, audit log and 2FA in the free edition (Levelrail ahead) | Yesstable Allow/Deny IAM policies (stable, live e2e), passkeys and TOTP, and an audit log with a verifiable hash chain, CSV export and forwarding, all in the one edition Source for Levelrail, IAM, audit log and 2FA in the free edition | Partly Cloud IAM and audit logs; 2FA is not a Cloud Run feature Source for Cloud Run, IAM, audit log and 2FA in the free edition |
| SAML or SCIM single sign-on | Activebeta OIDC sign-in (17 named providers plus generic OpenID Connect) is on by default once configured. SAML and SCIM are beta, behind a toggle and off by default; SAML ran against Keycloak and SimpleSAMLphp in a local lab, not Okta or Entra Source for Levelrail, SAML or SCIM single sign-on | Not stated in their docs |
| Audit log of every action (Levelrail ahead) | Yes Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucket Source for Levelrail, Audit log of every action | Partly Cloud Audit Logs cover Cloud Run API methods; the page does not state which are on by default, and Data Access logs appear to need enabling; pricing and retention not stated on the page Source for Cloud Run, Audit log of every action |
| Two-person deploy approvals (Levelrail ahead) | Yesstable A different person with the deploy ability must approve; the requester cannot approve their own. Approval also works from Slack or Discord Source for Levelrail, Two-person deploy approvals | Partly Via Cloud Deploy, a separate product: requireApproval on a target, approver role roles/clouddeploy.approver. The page opened describes Cloud Deploy generally, not a Cloud Run page Source for Cloud Run, Two-person deploy approvals |
All ten projects are on the full matrix. Product names and logos belong to their owners and are used for identification only.
Move over from Cloud Run
No importer. Deploy the same container image; the runbook maps each Cloud Run concept and lists what has none.
docker pull ghcr.io/glincker/levelrail:latestQuestions about Levelrail and Cloud Run
Is Levelrail a good alternative to Cloud Run?
Yes. Levelrail does what Cloud Run does with a lighter footprint and more built in. A fixed-price server you run, so cost does not move with traffic. Autoscaling is in beta, and wake from sleep is slower than a cold start. Logs, metrics and data stay on machines you control, with nothing billed by volume. A read-only importer and a dry-run mode let you move without touching Cloud Run.
Can I move from Cloud Run to Levelrail?
No importer. Deploy the same container image; the runbook maps each Cloud Run concept and lists what has none.
Is Levelrail ready to replace Cloud Run in production?
Run both side by side, move one domain at a time and keep Cloud Run as a fallback until you are happy. The feature status page lists the maturity of every area.