fshy

fshy / Compute / Egress and tunnels

Zeabur

zeabur.com · Compute, Egress and tunnels · 2 records · JSON

Zeabur Compute

caveatemailno cardDretention-clamped

zeabur.com/docs/en-US/pricing/free-plan · platform host · compute/zeabur · JSON · compare

Free tierFree Plan at USD 0: 'No credit card required', deploy as many projects and services as you like from GitHub, with services that 'automatically sleep after a period of inactivity'.
unit mixed; metered on unstated
Pricenone stated
Per-object capa single file upload is capped at 50 MB on Free; 48 hours of log retention; build machine 2C4G
Retention48 hours of logs on Free; no statement about service data
Egressthe documentation read today states no egress allowance on the Free Plan; the 2024 changelog introduced a fee of USD 1 per 10 GB and a 10 GB free quota for serverless-plan users
free_allowance: 10 GB (serverless plan, 2024 changelog)
Identityemail 'No credit card required — just sign up and start deploying'
Limits
  • retention-clamped services on the Free Plan sleep after a period of inactivity; the interval is not published source
  • volume-quota 10 GB of network usage free on the serverless plan, then USD 1 per 10 GB or automatic suspension source
  • per-object-cap 50 MB single-file upload; 0 advanced-model agent messages; no email sends source
not stated
Bindingretention-clamped sleep is the first thing that matters and the vendor does not publish the timeout, so the row cannot be planned against.
Interfaceunknown
Toolingnot stated
Composes withnot stated
Reliabilitythe sleep interval is unpublished, so 'a period of inactivity' cannot be sized; the vendor also states the Free Plan carries no SLA
NotesThe corpus recorded Zeabur's free tier as 'manages 1 server the client already owns', which is only the BYO-server row of the feature table; the Free Plan does deploy serverless services, without a card, and they sleep. The old USD 5 monthly credit is gone. What is not established is whether the Free Plan has any compute allowance at all or is metered against a card-free quota, and the sleep interval.
Evidence rungdocumented the Free Plan page was read today and states the auto-sleep and the no-card rule; the sleep duration and any compute allowance are not published on it
Checked2026-10-25 (live); stale on 2026-11-24
Parsed numbers
  • $.extras.m10h_usd price USD0.0 / month
  • $.extras.m24h_usd price USD0.0 / month
  • $.limits[1].value limit:volume-quota 10.0 GB
  • $.limits[2].value limit:per-object-cap 50.0 MB
Evidence (6)
datesourcewhat it proved
2026-10-02zeabur.com/pricingnot published
2026-10-22zeabur.com/pricing'Compute: manageable own servers - servers you purchased and own elsewhere ... you can still manage them from the Zeabur dashboard - 1 / 3 / 10 / Unlimited', with 'Email: daily quota 0 / 100 / Unlimited' and 'Single file upload size limit 50 MB' on the free column, quoted
2026-10-24zeabur.com/docs/en-US/pricing/free-planquoted: 'The Free Plan is Zeabur's free tier, designed for personal exploration and learning. No credit card required — just sign up and start deploying.'
2026-10-24zeabur.com/docs/en-US/pricing/free-planquoted: 'Auto-sleep — Services on the Free Plan automatically sleep after a period of inactivity. They wake up on the next incoming request, which may cause a few seconds of cold-start latency.'
2026-10-24zeabur.com/pricingquoted feature table: 'Single file upload size limit | 50 MB' on Free, 'Log retention | 48h', 'Manageable own servers | 1'
2026-10-24zeabur.com/changelogs/say-hello-to-the-serverless-planquoted: 'Previously, the Free Plan generously provided a $5 monthly usage credit' and 'No more need to tether a payment method or manually extend your access.'
More fields (18)
{
 "talaria_m10h_usd": 6.64,
 "talaria_m24h_usd": 8.95,
 "nemo_m10h_usd": null,
 "keep_rate": 1.0,
 "keep_rate_basis": "always-on by contract",
 "billing_model": "free",
 "shape": {
  "vcpu": null,
  "ram_gib": null,
  "disk_gib": null,
  "gpu_class": null,
  "gpu_count": null
 },
 "session_cap": {
  "wall_clock_min": null,
  "idle_reap_s": null,
  "restart_required": false,
  "note": "sleeps after an unpublished period of inactivity; wakes on the next request"
 },
 "persistent_storage": null,
 "network_out": {
  "allow_outbound": true,
  "allow_inbound_listen": false,
  "ports": "serverless HTTP services; no long-lived listening socket is documented",
  "static_ip": false,
  "ipv6": false,
  "per_session_bytes": null
 },
 "price_note": null,
 "free_tier_kind": "free-plan",
 "ps": {
  "gib": null,
  "price": "the client's own server storage",
  "durability": "the client's own server",
  "on_stop": true,
  "on_destroy": false,
  "max_retention": "as long as the client keeps it"
 },
 "net": {
  "out": true,
  "in": true,
  "ports": "the client's own server",
  "static_ip": null,
  "ipv6": null,
  "allowance": null
 },
 "term": "none",
 "m10h_usd": 0.0,
 "m24h_usd": 0.0,
 "price_arithmetic": "no plan fee; usage above the free allowances is billed or suspends the service"
}
Unknown or withheld values (7)
  • $.chaining not-stated
  • $.evidence[0].proved process
  • $.extras.price_note process
  • $.interface interface-unknown
  • $.interface_detail withheld
  • $.limits_note not-stated
  • $.tooling not-stated

Zeabur Egress and tunnels

fails: egressemailno cardDvolume-quota

zeabur.com/docs/en-US/pricing/free-plan · paas l4 port · egress/zeabur · JSON · compare

Free tierThe Free Plan is Zeabur's free tier, designed for personal exploration and learning. No credit card required - just sign up and start deploying.
unit none; metered on unstated
PriceUSD 0
Per-object capnot applicable
Retentionnot applicable
EgressThe Free Plan documentation states no monthly byte allowance; it lists only auto-sleep, no SLA, no Zeabur Email, and no backup or log forwarding.; ingress: tcp
free_allowance: none published
Identityemail "No credit card required - just sign up and start deploying."
Limits
  • volume-quota no published monthly byte allowance on the Free Plan source
Bindingvolume-quota Transport fails first: cloud services offer HTTP or TCP only, and the Free Plan auto-sleeps idle services, which ends a tunnel.
Interfacecli, rest Dashboard and CLI; ports declared per service with a type of HTTP or TCP.
ToolingDashboard, CLI, and templates; port type chosen per service port.
Composes withZeabur on a self-managed server could open UDP through that server's firewall; the free cloud tier cannot.
ReliabilityFree Plan services auto-sleep when idle and wake on the next request; a sleeping service cannot hold a tunnel. Forwarded host and port may change.
NotesThe UDP evidence in Zeabur's own templates is tied to dedicated-server projects, i.e. a server the client rents elsewhere and attaches. That is not a free platform port. Ports are also documented as possibly changing.
Evidence rungdocumented Whether the Free Plan may attach a TCP port at all is not stated; the plan page limits itself to sleep, SLA and feature exclusions.
Checked2026-10-23 (live); stale on 2026-11-22
Parsed numbers
  • $.price_per_tb_month price-per-tb USD0.0 TB / month
Evidence (3)
datesourcewhat it proved
2026-10-23zeabur.com/docs/en-US/pricing/free-planFree Plan, no card, auto-sleep after inactivity, no SLA
2026-10-23zeabur.com/docs/en-US/deploy/methods/custom-docker-image"Port Type can be HTTP or TCP" with TCP reachable at an auto-assigned hostname and port
2026-10-23zeabur.com/templates/1NIQIXsync-udp 22000/UDP forwarded entry, but "On dedicated server projects this will be your server's public IP"
More fields (7)
{
 "wg_path": "none",
 "wg_detail": "TCP ports only on cloud services: \"Port Type can be HTTP or TCP ... TCP ports can be accessed with an auto-assigned hostname and port (e.g., reg.clusters.zeabur.com:12345)\". UDP appears only in templates running on dedicated-server projects.",
 "ingress": "tcp",
 "volume_tib_month": null,
 "volume_stated": "The Free Plan documentation states no monthly byte allowance; it lists only auto-sleep, no SLA, no Zeabur Email, and no backup or log forwarding.",
 "bytes_transit": "yes",
 "transit_note": "Zeabur's cluster ingress forwards TCP to the service."
}
Unknown or withheld values (2)
  • $.per_object_cap.stated not-applicable
  • $.retention.stated not-applicable