Netlify
netlify.com · Compute, Storage · 3 records · JSON
- Netlify Computecaveatemailno cardDvolume-quota
- Netlify Open Source Computecaveatemailno cardDwrite-gated
- Netlify Blobs Storagefails: egressemail?card?Rper-object-cap
Netlify Compute
caveatemailno cardDvolume-quota
| Free tier | Free at USD 0 forever with a 300-credit monthly limit and a credit hard limit; credits are spent by deploys, compute, bandwidth and requests from one pool. unit mixed; metered on unstated |
|---|---|
| Price | none stated |
| Per-object cap | not stated on the pricing page; the pool is total credits, not a per-object size |
| Retention | not stated on the pricing page read today |
| Egress | bandwidth costs 20 credits per GB from the 300-credit pool free_allowance: 300 credits, about 15 GB of bandwidth |
| Identity | email a Netlify account; no card on the Free plan, and the plan has a hard credit limit rather than an overage |
| Limits |
one 300-credit monthly pool is shared by deploys, compute, bandwidth and requests, and the free plan has a hard limit with no recharge, so a site that serves 15 GB of bandwidth in a month has spent its whole allowance and then pauses. |
| Binding | volume-quota 300 credits is 30 GB-hours of compute or 15 GB of bandwidth, and both come out of the same 300. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | 300 credits a month is 30 GB-hours, which is 30 hours of a 1 GiB function, or about an hour a day across a month; Netlify Database and Blob storage draw from the same pool, so a storage backend must live elsewhere. |
| Reliability | no reliability event recorded |
| Notes | Confirms the corpus row; the legacy 100 GB bandwidth and 125k invocation figures do not appear on this page. Netlify functions are request-scoped like Vercel's, so it is not an always-on row either. |
| Evidence rung | documented the Free plan line and the credit cost table were read on the pricing page today |
| Checked | 2026-10-25 (live); stale on 2026-11-24 |
| Parsed numbers |
|
Evidence (5)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | www.netlify.com/pricing/ | Free plan: 300 credit limit; rates 15 credits per production deploy, 10 credits per GB-hour compute, 20 credits per GB bandwidth, 2 credits per 10k requests, quoted |
| 2026-10-22 | docs.netlify.com/manage/accounts-and-billing/billing/billing | Free plan is 300 credits/month with a credit hard limit and no auto recharge; monthly credits reset at the start of each cycle and do not roll over; accounts created from 2025-09-04 use credit plans, quoted |
| 2026-10-22 | www.netlify.com/pricing/pro-vs-free/ | Free includes 300 credits per month and 1 concurrent build; when credits run out, projects pause until the next billing cycle, quoted |
| 2026-10-24 | www.netlify.com/pricing/ | quoted: 'Free — $0 forever ... Credits: 300 credit limit' |
| 2026-10-24 | www.netlify.com/pricing/ | quoted usage credit costs: 'Production deploys 15 credits each', 'Compute 10 credits per GB-hour', 'Bandwidth 20 credits per GB', 'Web requests 2 credits per 10k requests' |
More fields (10)
{
"wave2": {
"class": "perpetual-allowance",
"free_tier_kind": "monthly-credit",
"shape": {
"vcpu": null,
"ram_gib": null,
"gpu_class": null,
"gpu_count": null
}
},
"shape": {
"vcpu": null,
"ram_gib": null,
"disk_gib": null,
"gpu_class": null,
"gpu_count": null
},
"billing_model": "free",
"term": "none",
"m10h_usd": 0.0,
"m24h_usd": 0.0,
"price_arithmetic": "no charge inside 300 credits",
"free_tier_kind": "credit-pool",
"network_out": {
"allow_outbound": true,
"allow_inbound_listen": false,
"ports": "HTTP only",
"static_ip": false,
"ipv6": false,
"per_session_bytes": null
},
"session_cap": {
"wall_clock_min": null,
"idle_reap_s": null,
"restart_required": false,
"note": "functions are request-scoped; no resident process"
}
}Unknown or withheld values (3)
$.interfaceinterface-unknown$.reliability_notenone-observed$.toolingnot-stated
Netlify Open Source Compute
caveatemailno cardDwrite-gated
| Free tier | Quoted: 'Our Open Source plan includes: 10,000 credits per month, Free production deploys, Unlimited team members, Sites remain active even if credits run out'. Available to a project that holds an OSI or CC-BY licence, publishes a Code of Conduct, and links back to Netlify. unit unlimited; metered on wall-clock; recurring-credit |
|---|---|
| Price | none stated |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | not stated |
| Identity | email not published |
| Limits |
A review of the application decides entry, and the site must carry a visible Netlify badge; the credit is monthly and does not roll over. |
| Binding | write-gated A review of the application decides entry, and the site must carry a visible Netlify badge; the credit is monthly and does not roll over. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | Build minutes and functions are the cheapest place to run a scheduled job that wakes a rented GPU host and kills it again, which is exactly the control plane a no-budget workload needs. |
| Reliability | no reliability event recorded |
| Notes | The best-documented small vendor credit: the number, the renewal rule and the durability term are all printed. The one structural catch is the badge requirement, which puts a vendor link on the project's front page. 'Must not be a commercial project, whether created by a company or an individual' is the line that excludes consulting work built on top of the same repository. |
| Evidence rung | documented |
| Checked | 2026-10-22 (live); stale on 2026-11-21 |
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | www.netlify.com/legal/open-source-policy/ | quoted the 10,000 credits per month, the 'sites remain active even if credits run out' term, the licence, Code of Conduct and badge conditions, and the exclusion of commercial projects |
| 2026-10-22 | www.netlify.com/legal/open-source-policy/ | the application route is a form at opensource-form.netlify.com, reviewed by Netlify |
More fields (1)
{
"wave2": {
"class": "vendor-oss-credits",
"free_tier_kind": "recurring-credit",
"shape": null
}
}Unknown or withheld values (10)
$.egress.meteredegress-unknown$.egress.termsnot-stated$.identity_cost.detailprocess$.interfaceinterface-unknown$.per_object_cap.notesprocess$.per_object_cap.statednot-applicable$.reliability_notenone-observed$.retention.notesprocess$.retention.statednot-applicable$.toolingnot-stated
Netlify Blobs Storage
fails: egressemail?card?Rper-object-cap
| Free tier | Object store with 5 GB max per object, but the Free plan is 300 credits/month where 1 GB of web bandwidth = 20 credits — i.e. ~15 GB of transfer/month total, shared with every other metered feature. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | 5 GB max per object (5000000000 bytes) |
| Retention | not stated |
| Egress | Metered in credits: 'Web Bandwidth | 1 GB transferred | 20 credits'. Free plan has '300 credits/month with credit hard limit'. ~15 GB/month of egress — three orders of magnitude short. free_allowance: 15 GB per month |
| Identity | email (placeholder) not published |
| Limits |
5 GB per object, 600-byte object keys, 2 KB metadata; Free = 300 credits/month hard cap covering bandwidth, requests (10,000 req = 2 credits) and functions compute; Go functions cannot access Blobs. |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| Interface | s3, rest, webdav, sftp, rclone rest |
| Tooling | Netlify JS/TS SDK (getStore/put/get) callable from Functions or Build Plugins; no S3/WebDAV/SFTP and no rclone backend. Access requires a Netlify site + function invocation. |
| Composes with | 500 projects per team x 300 credits, but credits are per team, not per project, so 500 sites do not multiply the allowance. Unlimited free teams would multiply, at ~15 GB egress each. |
| Reliability | Netlify moved all new accounts to credit billing on Sep 4, 2025 and the switch is irreversible; deploy-specific stores are deleted when the deploy is deleted. |
| Notes | Object store with 5 GB max per object, but the Free plan is 300 credits/month where 1 GB of web bandwidth = 20 credits — i.e. ~15 GB of transfer/month total, shared with every other metered feature. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.netlify.com/manage/accounts-and-billing/billing/billing | '300 credits/month with credit hard limit'; 'Web Bandwidth | 1 GB transferred | 20 credits' |
| 2026-10-21 | docs.netlify.com/build/data-and-storage/netlify-blobs/ | "An individual object's total size cannot exceed 5 GB" |
More fields (1)
{
"dead_end": {
"failure_class": "egress",
"why": "Object store with 5 GB max per object, but the Free plan is 300 credits/month where 1 GB of web bandwidth = 20 credits — i.e. ~15 GB of transfer/month total, shared with every other metered feature.",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (7)
$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted$.retention.statednot-extracted