# Zeabur

Canonical: https://inetgeek.com/hosting/zeabur/

Deployment platform that builds services from Git or Docker images and runs them on servers bought through it or brought by the user, billed as plan fees plus fixed-price servers.

## Who it suits

A Git-to-deploy dashboard on servers you own or rent at a fixed monthly price, from $5 a month for the Dev plan, with hardware from AWS, GCP, Hetzner, DigitalOcean and others to choose from.

Consider something else if You want usage billing on a shared platform or published compliance: Zeabur's shared cluster takes no new projects, the plan fee excludes the server, no uptime percentage is published, and SOC 2 Type II is still in progress.

## iScore

67 / 100 (80% interval 61–72), rank 10 of 11 in hosting — interval overlaps the next rank, so this is an ordering, not a finding.

inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known.
Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every hosting peer ranked: https://inetgeek.com/hosting/zeabur/alternatives/

- Price: 76 (70–82), weight 25%, 4 of 5 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: egress_overage_price
- Capacity and limits: 49 (36–62), weight 20%, 0 of 6 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: bandwidth_included, concurrent_builds, entry_plan_memory, max_request_duration, regions, sites_included
- Capabilities: 74 (63–86), weight 20%, 7 of 12 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: connection_pooling, edge_network, persistent_processes, scale_to_zero, streaming_response_limit
- Trust and compliance: 63 (57–70), weight 15%, 5 of 11 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: audit_logs, hipaa_eligible, iso27001, pci_dss, support_included, support_response_time
- Evidence: 86 (86–86), weight 10%, 4 of 4 criteria scored
- Adoption: 50 (11–89), weight 10%, 0 of 2 criteria scored

## What the documentation says

### Pricing

- Free tier: Yes — A $0 plan that manages 1 server of your own; the shared cluster that hosted free services takes no new projects. ([source](https://zeabur.com/docs/en-US/pricing), read 2026-09-27)
- Kind of free offer: Free tier ([source](https://zeabur.com/docs/en-US/pricing), read 2026-09-27)
- What the free plan includes: The $0 Free plan gives dashboard basics and community support, manages 1 server you own elsewhere, and keeps logs 48 hours. Separately, each user gets one 14-day free trial of Dev ($5/month) or Pro ($19/month). ([source](https://zeabur.com/pricing), read 2026-09-27)
- Credit card to start: No ([source](https://zeabur.com/docs/en-US/pricing/free-plan), read 2026-09-27)
- Entry paid plan: $5/month for the Dev plan, with the first 14 days free. The fee buys platform features; the server services run on is bought separately at its own fixed monthly price, or brought by the user. ([source](https://zeabur.com/docs/en-US/pricing), read 2026-09-27)
- Pricing model: A monthly plan fee (Free $0, Dev $5, Pro $19, Team $79) plus the servers you use, which are billed at a fixed monthly rate rather than by resource usage. Only legacy shared-cluster projects are still billed on resource usage. ([source](https://zeabur.com/docs/en-US/get-started/faq-support), read 2026-09-27)
- When you exceed a cap: No usage overage on servers, which are billed at a fixed monthly rate and auto-renew. If a renewal fails for lack of balance the server is powered off, not deleted, for a grace period of roughly 3 to 15 days depending on the provider; after that the server and its projects are deleted. ([source](https://zeabur.com/docs/en-US/server/purchase), read 2026-09-27)

### Deployment

- Git deployment: Supported ([source](https://zeabur.com/docs/en-US/deploy/methods/github-integration), read 2026-09-27)
- Docker deployment: Supported ([source](https://zeabur.com/docs/en-US/deploy/methods/dockerfile), read 2026-09-27)
- Containers: Supported ([source](https://zeabur.com/docs/en-US/security-practices), read 2026-09-27)
- Scheduled jobs: Limited — No built-in scheduler is documented; the Heroku migration guide points to system cron or a scheduled service. ([source](https://zeabur.com/docs/en-US/get-started/migration/heroku), read 2026-09-27)

### Infrastructure

- Persistent storage: Supported ([source](https://zeabur.com/docs/en-US/operations/data/volumes), read 2026-09-27)
- Managed databases: Limited — Databases run as services in your project; online and automatic backups start at the Dev plan. ([source](https://zeabur.com/docs/en-US/operations/data/backup-restore), read 2026-09-27)
- Autoscaling: Not supported — CPU and memory limits are set by hand per service; replicas are made by copying a service. ([source](https://zeabur.com/docs/en-US/deploy/networking/high-availability), read 2026-09-27)
- Regions: No fixed region list of its own: servers are bought from AWS, GCP, Hetzner, Linode, DigitalOcean, Aliyun, Tencent Cloud or Volcengine, filtered by continent (Asia, China, Europe, North America, South America, Oceania), or an existing server anywhere is attached. ([source](https://zeabur.com/docs/en-US/server/purchase), read 2026-09-27)
- Uptime SLA: No uptime percentage is published. The Free plan has no SLA; SLAs are mentioned only as part of custom Enterprise plans. ([source](https://zeabur.com/docs/en-US/pricing/free-plan), read 2026-09-27)

### Support

- Support on entry paid plan: Community support on Free. Every plan's standard tickets target a first response within 4 working days; Dev ($5/month) adds 2 express passes a month with a guaranteed 36-hour first response in working hours, Pro 5 and Team 10. ([source](https://zeabur.com/pricing), read 2026-09-27)

### Compliance

- SOC 2: Not yet certified: Zeabur states it is pursuing SOC 2 Type II, covering the security, availability and confidentiality criteria. ([source](https://zeabur.com/docs/en-US/security-practices), read 2026-09-27)
- GDPR / data residency: GDPR appears only as data-subject rights for EU and EEA residents in the Privacy Policy. No region or data-residency commitment is made there. ([source](https://zeabur.com/docs/en-US/privacy-policy), read 2026-09-27)
- Encryption at rest: Stated for Zeabur's own production data, which sits in MongoDB Atlas with AES-256 encryption at rest by default. Nothing is said about encryption of customer volumes or servers. ([source](https://zeabur.com/docs/en-US/security-practices), read 2026-09-27)
- Private networking / VPC: Services in the same project reach each other on a fixed internal hostname (for example postgresql.zeabur.internal). It is for service-to-service traffic inside one project, not for access from your own machine. ([source](https://zeabur.com/docs/en-US/deploy/networking/private-networking), read 2026-09-27)