Render
render.com · 5 records in Compute, Egress and tunnels, Storage · JSON
Records 5
- caveatRender, Free instance (web service)
Computefree tieridentity emailcardlimit retention-clampedevidence documentedstale on 2026-12-04
- caveatRender Hobby
Computefree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-12-05
- trialRender Postgres (free)
Computeidentity emailno cardevidence reportedstale on 2026-11-06
- fails: egressRender (free)
Egress and tunnelsfree tieridentity emailcardlimit volume-quotaevidence documentedstale on 2026-11-23
- fails: quotarender — persistent disks and free web services
Storageidentity email?card?evidence reportedstale on 2026-11-05
- Free allowance
- A Free web service with an ephemeral filesystem, 750 Free instance hours per workspace per calendar month, and a 5 GB monthly outbound bandwidth allowance on the Hobby plan.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailcard required, no phone
- Binding limit
- retention-clampedspins down after 15 minutes without inbound HTTP or WebSocket traffic; a wake takes about one minute
- Evidence
- documented27 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
| Free tier | A Free web service with an ephemeral filesystem, 750 Free instance hours per workspace per calendar month, and a 5 GB monthly outbound bandwidth allowance on the Hobby plan. unit hours; metered on wall-clock |
|---|---|
| Price | none stated |
| Limits |
a WebSocket message from an existing connection resets the 15-minute timer, which the vendor states explicitly |
| Binding | retention-clamped 15 minutes of silence ends the process, so an always-on workload cannot live here at all; the 750 hours only bind for a service that is kept awake deliberately. |
| Identity | email an account is enough for a Free web service; a payment method is optional and its absence converts a bandwidth overrun into a suspension instead of a bill |
| Egress | Hobby workspaces include 5 GB of outbound bandwidth a month, then USD 0.15 per GB; without a payment method Render suspends all Free services for the rest of the month free allowance: 5 GB price per tb: USD 150 |
| Per-object cap | no per-object cap; the free tier is one service shape, less than one CPU and 512 MB of RAM |
| Retention | the filesystem is ephemeral and is lost on every redeploy, restart or spin-down; a Free Postgres database expires 30 days after creation |
| Interface | ssh a git push deploy, a public HTTPS endpoint, and a REST API |
| Tooling | git-based deploy, a render.yaml blueprint, the Render API |
| Composes with | an endpoint that answers and holds no state, kept warm by a request every 15 minutes |
| Reliability | 'Render might restart a Free web service at any time'; a service that initiates an uncommonly high volume of outbound traffic may be suspended |
| Notes | What is still unverified is whether a spun-down service wakes purely from an inbound request to a non-HTTP port; the docs name only HTTP requests and new WebSocket connections. |
| Evidence note | documented the spin-down trigger, the 750 hours, the suspension rule and the 5 GB Hobby allowance were all read on two Render documentation pages |
| Parsed numbers |
|
Evidence 27
| date | source | what it proved |
|---|---|---|
| 2026-10-06 | render.com/docs/free | 'Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic' |
| 2026-10-06 | render.com/docs/free | any changes to the local filesystem are lost on spin-down; 750 free instance-hours per workspace a month |
| 2026-10-22 | render.com/docs/free | read live: 750 instance-hours a month and the 15-minute spin-down |
| 2026-10-22 | render.com/pricing | quoted: Hobby includes 5 GB of bandwidth a month, additional bandwidth at USD 0.15 per GB, 25 services maximum, 2 custom domains |
| 2026-10-22 | render.com/docs/free | quoted: if you consume all of your outbound bandwidth during a given month, Render bills you for a supplementary amount, and if you have not added a payment method Render suspends all of your free services for the remainder of the month |
| 2026-08-02 | www.nodeseek.com/post-854242-1 | forum observation of the rollout lag, translated: Render announced that on 1 August the legacy Hobby plan becomes Hobby New and free traffic drops to 5 GB, but the old plan still had 100 GB that day |
| 2026-10-22 | render.com/blog/better-pricing-for-fast-growing-teams | vendor post, quoted: we are also reducing the bandwidth included in the Hobby and Pro plans |
| 2026-10-24 | render.com/docs/compute-plans | quoted table row: '0.1 CPU | 512 MB | free' |
| 2026-10-24 | render.com/docs/free | quoted: 'Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic.' |
| 2026-10-24 | render.com/docs/free | quoted: 'are lost every time the service redeploys, restarts, or spins down' |
| 2026-10-24 | render.com/docs/free | quoted: 'Shell access via SSH or the Render Dashboard', listed among the features free web services do not support |
| 2026-10-24 | render.com/docs/free | quoted: 'Render grants 750 Free instance hours to each workspace per calendar month' |
| 2026-10-24 | render.com/docs/free | quoted: 'Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic. This includes both HTTP requests and WebSocket messages from existing connections.' |
| 2026-10-24 | render.com/docs/free | quoted: 'Render grants 750 Free instance hours to each workspace per calendar month' and 'If you consume all of your Free instance hours during a given month, Render suspends all of your Free web services' |
| 2026-10-24 | render.com/docs/free | quoted: 'Running one-off jobs' listed among features Free web services do not support, and 'Render might restart a Free web service at any time.' |
| 2026-10-24 | render.com/docs/outbound-bandwidth | quoted: 'Hobby | 5 GB' in the monthly included bandwidth table, and '$0.15 per GB' above the allowance |
| 2026-10-24 | render.com/docs/cronjobs | quoted: 'There is a minimum monthly charge of $1 per cron job service.' |
| 2026-10-30 | render.com/pricing | a Hobby workspace includes 500 standard build pipeline minutes a month, then USD 5 per 1K minutes |
| 2026-10-30 | render.com/docs/build-pipeline | a build command times out after 120 minutes; the same page states 30 minutes for a pre-deploy command, a 16 GB build disk limit, and that Hobby always uses the Starter tier of 2 CPU and 8 GB RAM |
| 2026-10-30 | render.com/docs/build-pipeline | build concurrency is one per service, and a new build cancels the one in progress |
| 2026-10-30 | render.com/docs/free | without a payment method, running out of pipeline minutes stops new builds for the month; the next line says services stay active on existing build artifacts |
| 2026-10-30 | web.archive.org/web/20250615030429/https://render.com/docs/b | the Wayback capture of 2025-06-15 of the build pipeline page already stated 500 pipeline minutes a month for Hobby, with the same 120-minute build timeout; the allowance is unchanged |
| 2026-10-30 | render.com/docs/free | the Free instance allowance is 750 hours per workspace per calendar month |
| 2026-11-02 | render.com/docs/deploys | the overlapping-deploy policy is a workspace setting; wait is the default for workspaces created on or after 2025-07-14 |
| 2026-11-02 | render.com/docs/deploys | the concurrency limit the deploys page states is per service, not per workspace |
| 2026-11-02 | render.com/docs/build-pipeline | the build limit on the build pipeline page is per service; no workspace-wide concurrency is stated |
| 2026-11-02 | render.com/pricing | the Hobby pipeline allowance is 500 minutes a month; the pricing page lists no build concurrency row |
More fields 13
| shape | {"vcpu": 0.1,"ram_gib": 0.5,"disk_gib": null,"gpu_class": null,"gpu_count": null} |
|---|---|
| billing model | free-instance |
| session cap | {"wall_clock_min": null,"idle_reap_s": 900,"restart_required": false,"note": "15 minutes without inbound HTTP or WebSocket traffic; wake takes about a minute"} |
| persistent storage | {"included_gib": 0,"price_gib_month": "no persistent disk on free","durability": "ephemeral","survives_stop": false,"survives_destroy": false,"max_retention": "the instance lifetime"} |
| network out | {"allow_outbound": true,"allow_inbound_listen": true,"ports": "one HTTP port; outbound ports 25, 465 and 587 blocked; reserved ports 18012, 18013, 19099 refused","static_ip": false,"ipv6": false,"per_session_bytes": null} |
| free tier kind | free-instance-hours |
| granularity | {"min_billed_s": 0,"rounding_s": null} |
| burst x | 1.0 |
| shape note | 0.1 CPU and 512 MB as the vendor states; no disk is allocated on free |
| term | monthly |
| m10h usd | 0.0 |
| m24h usd | 0.0 |
| price arithmetic | no charge; 750 instance hours a month is 31.25 days, so one always-on service consumes the whole workspace pool |
Render Hobby
Compute- Free allowance
- Render's documentation confirms both the figure and the mechanism, quoted: 'Hobby | 5 GB' in the included-bandwidth table, and 'If you consume all of your outbound bandwidth during a given month, Render bills you for a supplementary amount.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quota5 GB a month is about 170 MB a day, and the second cap arrives first for a service that is always on: 750 free instance hours across all free services in a workspace, which one always-on service exhausts in 31 days.
- Evidence
- documented8 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Render's documentation confirms both the figure and the mechanism, quoted: 'Hobby | 5 GB' in the included-bandwidth table, and 'If you consume all of your outbound bandwidth during a given month, Render bills you for a supplementary amount. If you haven't added a payment method, Render instead suspends all of your Free services for the remainder of the month.' A separate 750-hour monthly instance cap suspends free web services when exhausted. unit GiB; metered on wall-clock; perpetual-monthly |
|---|---|
| Price | none stated |
| Limits |
|
| Identity | email no card is required to hold the free plan, and its absence is what triggers suspension rather than a bill: the docs state 'If you haven't added a payment method, Render instead suspends all of your Free services for the remainder of the month'. No hold amount is stated because no payment method is required. The signup form is not quoted, so the email requirement is inferred rather than read; debit and prepaid acceptance are not stated, and a card only changes overage from suspension to billing. |
| Egress | 'Hobby | 5 GB' included bandwidth; 'Render spins down your workspace's services until the start of the next month' when the allowance is exhausted with no payment method free allowance: 5 GB a month on the Hobby plan price per tb: USD 153.60 per TiB (USD 0.15 per GB) over the public internet; USD 30.72 per TiB (USD 0.03 per GB) over a private link |
| Interface | rest, cli REST API (API key created in Account Settings) and the Render CLI are documented. Dashboard shell and SSH are not available for a Free web service; they are listed for paid web services, private services and background workers only. |
| Tooling | Render CLI (Homebrew, WinGet, curl installer) and the public REST API with an API key. |
| Composes with | Render's free web service composes with a free Postgres only for 30 days, because a free Postgres database expires 30 days after creation with a 14-day grace period before deletion. |
| Reliability | no reliability event recorded |
| Notes | The term that binds first for an always-on service: 750 instance hours a month is 31.25 days, so a single always-on free web service uses the whole workspace pool and a second free service has none. Render's free tier also has two traps a reader should know before planning: a free Postgres expires after 30 days, and free services spin down after 15 minutes of inactivity with about a minute to restart. The page states both a 5 GB Hobby egress allowance and a per-GB price beyond it. |
| Parsed numbers |
|
Evidence 8
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | render.com/docs/outbound-bandwidth | quoted: 'Hobby | 5 GB' included bandwidth; 'Render spins down your workspace's services until the start of the next month' when the allowance is exhausted with no payment method |
| 2026-10-22 | render.com/docs/free | quoted: 'Render grants 750 Free instance hours to each workspace per calendar month'; 'If you consume all of your Free instance hours during a given month, Render suspends all of your Free web services until the start of the next month' |
| 2026-10-22 | render.com/docs/outbound-bandwidth | quoted: 'If your workspace exceeds this amount, Render bills you for each additional GB of bandwidth used: $0.15 per GB for traffic sent over the public internet, $0.03 per GB for traffic sent over a private link connection', with the included-bandwidth table row 'Hobby | 5 GB' and the FAQ 'If you've linked a payment method, Render bills you for each additional GB of bandwidth ... Otherwise, Render spins down your workspace's services until the start of the next month.' Supports the 5 GB included allowance, the per-month clock and the suspend-without-a-payment-method mechanism the verdict rests on. It also documents a per-GB price above the allowance, so egress is metered once the included volume is passed, which the stored egress.metered=false does not carry; the qualifies-with-caveat verdict is unaffected |
| 2026-11-04 | render.com/docs/api | a public REST API is documented |
| 2026-11-04 | render.com/docs/cli | a CLI is documented |
| 2026-11-04 | render.com/docs/ssh | a Free web service has neither dashboard shell nor SSH; paid web services, private services and background workers do |
| 2026-11-04 | render.com/docs/outbound-bandwidth | Hobby included outbound bandwidth is 5 GB |
| 2026-11-04 | render.com/docs/outbound-bandwidth | overage price over the public internet |
More fields 1
| facets | {"class": "verification","free_tier_kind": "perpetual-monthly","shape": null} |
|---|
Unknown values 3
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer
Render Postgres (free)
Compute- Free allowance
- A free Postgres instance that expires 30 days after creation
- Verdict
- triala time-boxed or one-time trial, not a recurring allowance
- Cost
- not stated
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-06checked 2026-10-22 (live); stale on 2026-11-06
| Free tier | a free Postgres instance that expires 30 days after creation unit none; metered on wall-clock; a separate resource type from the free web service, with its own expiry |
|---|---|
| Price | none stated |
| Limits |
it is kept because the 30-day clock is the same kind of limit |
| Identity | email an account; no card |
| Egress | not applicable beyond the connection |
| Retention | the free database expires 30 days after creation (30 days) |
| Interface | ssh a PostgreSQL connection string |
| Tooling | any Postgres client; the connection string is in the dashboard |
| Composes with | 30 days of state, then it must be migrated |
| Reliability | no reliability event recorded |
| Evidence note | reported re-read live on 2026-10-22 for the free-tier and limit figures |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-06 | render.com/docs/free | free Postgres databases expire 30 days after creation |
| 2026-10-22 | render.com/docs/free | read live: free Postgres expires 30 days after creation |
More fields 4
| billing model | flat-pool |
|---|---|
| persistent storage | {"included_gib": null,"price_gib_month": "not offered","durability": "30 days","survives_stop": true,"survives_destroy": false,"max_retention": "30 days"} |
| network out | {"allow_outbound": true,"allow_inbound_listen": true,"ports": "the Postgres port","static_ip": null,"ipv6": null,"per_session_bytes": null} |
| free tier kind | none |
Unknown values 2
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
Render (free)
Egress and tunnels- Free allowance
- You can deploy certain Render service types free of charge ...
- Verdict
- fails: egressdata cannot be read back out at a usable rate or price
- Cost
- free tier
- Identity
- emailcard required, no phone
- Binding limit
- volume-quota5 GB per month on Hobby; $0.15/GB above
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | You can deploy certain Render service types free of charge ... Free instances have important limitations, described below. Do not use them for production applications. unit GB; metered on downloaded-bytes |
|---|---|
| Price | USD 0 |
| Limits |
|
| Binding | volume-quota 5 GB/month is 0.005 TiB. The transport fails first though: no public port other than one HTTP port exists on a free web service. |
| Identity | email Free instances need an account; a payment method is optional, and without one Render "spins down your workspace's services until the start of the next month" at the cap. |
| Egress | Hobby workspace included bandwidth: 5 GB per month. Above that, $0.15 per GB, or the workspace is spun down until the next month.; ingress: http-only free allowance: Hobby workspace included bandwidth: 5 GB per month. Above that, $0.15 per GB, or the workspace is spun down until the next month. |
| Interface | rest, cli Dashboard, API, and render.yaml blueprint. |
| Tooling | Git push or Dockerfile; no port configuration beyond PORT. |
| Composes with | Render can host the HTTP side of a stack; it cannot host an endpoint. |
| Reliability | Free instances spin down when idle; the workspace is spun down at the bandwidth cap if no card is on file. |
| Notes | Private services can bind extra ports but only over the private network; the free tier does not include private services. One public HTTP port per service. |
| Evidence note | documented A probe cannot be run because no non-HTTP public port can be created on a free instance. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | render.com/docs/free | Free web services and static sites; bandwidth counted against workspace allowance |
| 2026-10-23 | render.com/docs/outbound-bandwidth | Hobby 5 GB included bandwidth; $0.15/GB public internet; spin-down without a payment method |
| 2026-10-23 | render.com/docs/web-services | "Render forwards inbound requests to your web service at this port (it is not directly reachable via the public internet)." |
More fields 7
| wg path | none |
|---|---|
| wg detail | HTTP only. "Every Render web service must bind to a port on host 0.0.0.0 to serve HTTP requests ... Render forwards inbound requests to your web service at this port (it is not directly reachable via the public internet)." |
| ingress | http-only |
| volume tib month | 0.00455 |
| volume stated | Hobby workspace included bandwidth: 5 GB per month. Above that, $0.15 per GB, or the workspace is spun down until the next month. |
| bytes transit | no |
| transit note | Render terminates HTTP; no raw socket reaches a user. |
Unknown values 2
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer
- Free allowance
- Persistent disks are paid-only: 'You can attach a persistent disk to a paid Render web service'.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Persistent disks are paid-only: 'You can attach a persistent disk to a paid Render web service'. Free web services have an ephemeral filesystem — 'any changes to your web service's… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | render.com/docs/disks | the text of Free tier, above |
| 2026-10-21 | render.com/docs/free | cited as the basis of the rejection: Persistent disks are paid-only: 'You can attach a persistent disk to a paid Render web service'. Free web services have an ephemeral filesystem — 'any changes to your web service's filesyste |
More fields 1
| dead end | {"failure_class": "retention","why": "Persistent disks are paid-only: 'You can attach a persistent disk to a paid Render web service'. Free web services have an ephemeral filesystem — 'any changes to your web service's…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field