fshy / Compute / Egress and tunnels / Storage
Vercel
vercel.com · Compute, Egress and tunnels, Storage · 8 records · JSON
- Vercel Computecaveatemailno cardDvolume-quota
- Vercel Sandbox Computecaveatemailno cardDvolume-quota
- vercel blob Storagefails: egressemail?card?Rdisagrees
- Vercel Hobby Egress and tunnelsfails: quotaemailno cardDvolume-quota
- Vercel Blob (Hobby plan) Storagefails: quotaemail?card?Rper-object-capdisagrees
- Vercel Deployment Storage / artifact store (Hobby, 30-day TTL) Storagefails: quotaemail?card?Rretention-clamped
- vercel edge config / global config Storagefails: quotaemail?card?R
- vercel hobby (static deployments) Storagefails: quotaemail?card?R
Vercel Compute
caveatemailno cardDvolume-quota
| Free tier | Hobby at USD 0: 4 CPU-hours of active CPU, 360 GB-hours of provisioned memory, 1 million function invocations, 100 GB of fast data transfer and 1 million CDN requests a month; 100 cron jobs per project, once a day each. unit mixed; metered on wall-clock |
|---|---|
| Price | none stated |
| Per-object cap | functions cap at 2 GB of memory and 300 seconds of duration on Hobby |
| Retention | no persistent disk; a function is stateless |
| Egress | 100 GB of fast data transfer and 10 GB of fast origin transfer a month free_allowance: 100 GB |
| Identity | email a Vercel account; no card on Hobby |
| Limits |
the 360 GB-hours of provisioned memory runs out before the 4 hours of Active CPU: a function pinned at the Hobby 2 GB maximum consumes 360 GB-hours in 180 hours, and memory is billed for the whole invocation, not only the CPU slice. |
| Binding | volume-quota 360 GB-hours at the 2 GB function ceiling is 180 hours of wall clock, and memory is billed for the whole invocation rather than the CPU slice. |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | 360 GB-hours at 1 GB of provisioned memory is 360 hours a month, which is a cron worker that never sleeps; the 300 s duration cap forces chunking, so the shape is a queue plus short functions rather than a daemon. |
| Reliability | exceeding a Hobby limit usually means waiting 30 days, not paying an overage; some limits have shorter pause periods |
| Notes | The cron row is the part that matters for a 03:00 job: the trigger is free and allowed on Hobby, but its precision is plus or minus 59 minutes, so it cannot be relied on for an exact hour. Confirms the corpus row on the quotas. |
| Evidence rung | documented the Hobby usage table, the cron limits and the 30-day pause rule were all read in Vercel's documentation today |
| Checked | 2026-10-25 (live); stale on 2026-11-24 |
| Parsed numbers |
|
Evidence (6)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | vercel.com/docs/pricing | Hobby included usage: Active CPU 4 hours, Provisioned Memory 360 GB-hrs, Invocations 1 million; Fast Data Transfer first 100 GB; CDN requests 1M/month, quoted |
| 2026-10-22 | vercel.com/docs/functions/limitations | Hobby maximum memory 2 GB; maximum duration 300 s default and maximum; 1,024 file descriptors shared across concurrent executions; single region iad1 by default, quoted |
| 2026-10-22 | vercel.com/pricing | Hobby USD 0/mo, 1M CDN requests/month included, 100 GB/month fast data transfer included, quoted |
| 2026-10-24 | vercel.com/docs/plans/hobby | quoted table: 'Active CPU | 4 CPU-hrs', 'Provisioned Memory | 360 GB-hrs', 'Function Invocations | First 1,000,000', 'Fast Data Transfer | First 100 GB' |
| 2026-10-24 | vercel.com/docs/plans/hobby | quoted: 'if you exceed your usage limits on the Hobby plan, you will have to wait until 30 days have passed before you can use the feature again' |
| 2026-10-24 | vercel.com/docs/cron-jobs/usage-and-pricing | quoted: 'Hobby | 100 cron jobs | Once per day | Per-hour (±59 min)' |
More fields (10)
{
"wave2": {
"class": "perpetual-allowance",
"free_tier_kind": "monthly-allowance",
"shape": {
"vcpu": null,
"ram_gib": 2,
"gpu_class": null,
"gpu_count": null
}
},
"shape": {
"vcpu": null,
"ram_gib": 2,
"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 the Hobby allowances",
"free_tier_kind": "free-allowance",
"network_out": {
"allow_outbound": true,
"allow_inbound_listen": false,
"ports": "HTTP only; no listening socket",
"static_ip": false,
"ipv6": false,
"per_session_bytes": null
},
"session_cap": {
"wall_clock_min": 300,
"idle_reap_s": null,
"restart_required": false,
"note": "a function may run 300 s on Hobby; nothing stays resident"
}
}Unknown or withheld values (2)
$.interfaceinterface-unknown$.toolingnot-stated
Vercel Sandbox Compute
caveatemailno cardDvolume-quota
| Free tier | 'Sandbox is free for Hobby users within the usage quotas': 'Sandbox Active CPU | 5 hours/month', 'Sandbox Provisioned Memory | 420 GB-hours/month', 'Sandbox Creations | 5,000/month', 'Sandbox Data Transfer | 20 GB/month', 'Snapshot Storage | 15 GB (lifetime)'. 'Max Session Duration | 45 minutes' on Hobby. unit mixed; metered on wall-clock; No cash credit on Hobby; the Pro plan's USD 20 monthly credit is a plan credit. |
|---|---|
| Price | none stated |
| Per-object cap | 'You can provision 1 or an even number of vCPUs between 2 and 32 depending on your plan ... The default is 2 vCPUs' and 'Each vCPU includes 2 GB of memory'. |
| Retention | Snapshot storage is 15 GB lifetime on Hobby; Drive storage 15 GB lifetime. Sandboxes themselves are ephemeral. |
| Egress | 'Data your sandbox sends to the internet, plus all traffic to and from exposed ports, is billable and measured in GB'; downloads into the sandbox are free. Hobby includes 20 GB a month, then USD 0.15/GB. free_allowance: 20 GB a month price_per_tb: USD 150 per TB |
| Identity | email A Hobby account needs only a Vercel login; no card is required for the free sandbox quota. No hold exists at that tier. |
| Limits |
Active CPU is billed only while code runs, but provisioned memory is billed for the whole time the sandbox exists, so an idle box is not free. |
| Binding | volume-quota The 45-minute session cap is the first wall; 5 hours of active CPU a month is the second, and neither reaches a day of uptime, let alone a month. |
| Interface | rest, cli SDK and REST; persistent sandboxes and snapshots |
| Tooling | Vercel SDK, CLI, snapshots and drives |
| Composes with | active-CPU billing makes an idle agent nearly free here, and the 45-minute session cap is what stops it being a host |
| Reliability | A sandbox that reaches 45 minutes is stopped by the platform, and its state is only preserved if a snapshot was taken. |
| Notes | Even setting the 45-minute cap aside, the allowance cannot hold a box up: 730 hours of a 2 vCPU / 4 GB sandbox needs 2,920 GB-hours of provisioned memory against 420 included, and 730 hours of active CPU against 5. The Pro plan's USD 20 monthly credit would buy 154 hours of memory alone. This row is for batch jobs. |
| Evidence rung | documented Quotas, the session cap, the vCPU rule and the transfer terms are on the pricing doc read today. |
| Checked | 2026-10-25 (live); stale on 2026-11-24 |
| Parsed numbers |
|
Evidence (5)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | vercel.com/docs/sandbox/pricing | Hobby: 5 hours active CPU and 420 GB-hours memory a month, 45-minute maximum session, 10 concurrent sandboxes |
| 2026-10-22 | vercel.com/docs/sandbox/pricing | active CPU is time actually using the CPU; waiting on I/O does not count |
| 2026-10-22 | vercel.com/docs/sandbox/pricing | Hobby: max 4 vCPU, 8 GB memory, 64 GB disk, 15 open ports; over the included limit, creation pauses until the next cycle |
| 2026-10-22 | boat.dev/compare | a competitor's comparison table lists Vercel Sandbox at USD 0.682 per hour for a 4 vCPU / 8 GB / 50 GB machine, with list prices dated 2026-09-26; this is a reported rate about a third party and not a reading of the vendor's own page |
| 2026-10-24 | vercel.com/docs/sandbox/pricing | quoted: 'Sandbox Active CPU | 5 hours/month | $0.128/hour', 'Sandbox Provisioned Memory | 420 GB-hours/month | $0.0212/GB-hour', 'Max Session Duration | 45 minutes' on Hobby and '24 hours' on Pro, 'Sandbox is free for Hobby users within the usage quotas', 'Each vCPU includes 2 GB of memory'. |
More fields (21)
{
"shape": {
"vcpu": 2,
"ram_gib": 4,
"disk_gib": null,
"gpu_class": null,
"gpu_count": null
},
"billing_model": "per-hour on active CPU plus provisioned memory",
"granularity": {
"min_billed_s": 60,
"rounding_s": 60
},
"session_cap": {
"wall_clock_min": 45,
"idle_reap_s": null,
"restart_required": true,
"note": "45 minutes on Hobby, 24 hours on Pro"
},
"keep_rate": {
"value": 0.0,
"basis": "only active CPU and provisioned memory while running are billed",
"source": "https://vercel.com/docs/sandbox/pricing"
},
"persistent_storage": {
"included_gib": 64,
"price_gib_month": "snapshot storage USD 0.08 per GB-month on Pro",
"durability": "ephemeral NVMe; snapshots are separate",
"survives_stop": false,
"survives_destroy": false,
"max_retention": "a snapshot persists until deleted"
},
"network_out": {
"allow_outbound": true,
"allow_inbound_listen": true,
"ports": "exposed ports",
"static_ip": null,
"ipv6": null,
"per_session_bytes": null
},
"free_tier_kind": "monthly-allowance",
"m10h_usd": null,
"m24h_usd": 61.9,
"price_arithmetic": "4 GB x 730 h = 2920 GB-h x 0.0212 = 61.90 for memory; active CPU at 5% of a 2 vCPU box = 36.5 CPU-h x 0.128 = 4.67; total about 66.57 a month if CPU is near idle",
"price_note": "2 vCPU and 4 GiB billed as active CPU plus provisioned memory, at 100 per cent CPU. At 50 per cent CPU the same shape is USD 63.84 for 300 hours. The two seed figures are the two utilizations and neither is wrong.",
"price_basis": "10 h/day x 30 = 300 h; 24/7 x 30 = 730 h",
"burst_x": 1.0,
"burst_bill": "$6e-07 per start",
"crosscheck": {
"boat_compare_2026-09-26": "USD 0.682/h at 4 vCPU / 8 GB"
},
"term": "monthly allowance",
"credit_usd": 0,
"credit_months_at_shape": 0.144,
"credit_hours_at_shape": 105,
"credit_expiry": "resets monthly"
}vercel blob Storage
fails: egressemail?card?Rdisagrees
Sibling records disagree:
- verdict:
storage/vercel-blobsays fails-quota, storage/vercel-blob-2 says fails-egress
| Free tier | Hobby includes 1 GB/month blob storage and 10 GB data transfer, then regional metered pricing. 1 GB per account is 3 orders of magnitude below the bar and the overage is per-GB paid. unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | not recorded |
| Reliability | Hobby includes 1 GB/month blob storage and 10 GB data transfer, then regional metered pricing. 1 GB per account is 3 orders of magnitude below the bar and the overage is per-GB paid. |
| Notes | Hobby includes 1 GB/month blob storage and 10 GB data transfer, then regional metered pricing. 1 GB per account is 3 orders of magnitude below the bar and the overage is per-GB paid. |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | vercel.com/docs/vercel-blob/usage-and-pricing | Hobby includes 1 GB/month blob storage and 10 GB data transfer, then regional metered pricing. 1 GB per account is 3 orders of magnitude below the bar and the overage is per-GB paid. |
More fields (1)
{
"dead_end": {
"failure_class": "egress",
"why": "Hobby includes 1 GB/month blob storage and 10 GB data transfer, then regional metered pricing. 1 GB per account is 3 orders of magnitude below the bar and the overage is per-GB paid.",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded
Vercel Hobby Egress and tunnels
fails: quotaemailno cardDvolume-quota
| Free tier | 100 GB fast data transfer, 1M CDN requests and 1M invocations per month unit GB; metered on downloaded-bytes |
|---|---|
| Price | none stated |
| Per-object cap | not applicable: billed by volume |
| Retention | not applicable |
| Egress | 100 GB/month of fast data transfer; excess is held rather than billed free_allowance: 100 GB/month |
| Identity | email a Vercel account |
| Binding | volume-quota the monthly byte allowance in egress.free_allowance is what runs out, and no kind in the six-value vocabulary names a byte volume over a period counted per account. per-ip-shaping is the closest, because it is the only kind that bounds a volume, and its subject here is the account rather than the caller's address |
| Interface | cli vercel deploy |
| Tooling | vercel CLI |
| Composes with | composes with a git repository and a domain; the 100 GB is the whole allowance and the excess pauses rather than bills. |
| Reliability | Hobby usage past the allowance pauses until the window resets rather than billing |
| Notes | The same 100 GB ceiling as Fastly and the same verdict for the same arithmetic. |
| Evidence rung | documented |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | vercel.com/docs/plans/hobby | 100 GB fast data transfer per month |
More fields (3)
{
"stale_after_days": 180,
"bytes_transit": "yes",
"transit_note": "the CDN serves the deployment's bytes from Vercel's edge"
}Vercel Blob (Hobby plan) Storage
fails: quotaemail?card?Rper-object-capdisagrees
Sibling records disagree:
- verdict:
storage/vercel-blobsays fails-quota, storage/vercel-blob-2 says fails-egress
| Free tier | 1 GB/month of storage, TOTAL per Hobby team — not per project. Pricing table: 'Blob Storage Size | Regional | Usage-based | 1GB/month' for the Hobby Included column, alongside 'Blob Simple Operations | First 10,000', 'Blob Advanced Operations | First 2,000', 'Blob Data Transfer | First 10 GB'. Per-file ceiling is genuinely large: 'you can store files up to 5 TB' (multipart above 100 MB). Unlimited stores since Sept 2026 — but the changelog is explicit that this buys no storage: 'Splitting the same data across more stores doesn't change those costs.' unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | Per-file ceiling is genuinely large: 'you can store files up to 5 TB (5000000000000 bytes) |
| Retention | not stated |
| Egress | Metered and small: 10 GB of Blob Data Transfer included, then hard-stopped. 'You will not pay for any additional usage. However, you will not be able to access Vercel Blob if limits are exceeded. In this scenario, you will have to wait until 30 days have passed before using Blob storage again.' Public blobs are served from *.public.blob.vercel-storage.com with no auth. |
| Identity | email (placeholder) not published |
| Limits |
1 GB storage/month, 10 GB transfer, 2,000 advanced ops (each store creation counts as one), 10,000 simple ops. Operation rate limit 1,200/min simple, 900/min advanced. 512 MB max cacheable blob — larger blobs MISS every time and incur Fast Origin Transfer. 30-day total lockout on exceeding any limit. |
| 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 | rest, rclone rest |
| Tooling | @vercel/blob JS/TS SDK (put, get, del, head, copy, list, client upload) and a Python SDK; usable from any host with a token. No rclone backend. |
| Composes with | The obvious idea — unlimited stores x 1 GB — is explicitly dead: storage is billed on total GB-months regardless of store count, and the Hobby allowance is per team. Chaining requires multiplying Vercel accounts, and a Hobby team is 1 per person with a hard 30-day lockout on breach, so the practical rate is roughly 1 GB per person per month. |
| Reliability | Reliable while under quota; the failure mode is a 30-day feature freeze, not deletion. Public URLs are stable. Cache HITs are free but misses are billed, so large blobs are unusually expensive. |
| Notes | 1 GB/month of storage, TOTAL per Hobby team — not per project. Pricing table: 'Blob Storage Size | Regional | Usage-based | 1GB/month' for the Hobby Included column, alongside 'Blob Simple Operations | First 10,000', 'Blob Advanced Operations | First 2,000', 'Blob Data Transfer | First 10 GB'. Per-file ceiling is genuinely large: 'you can store files up to 5 TB' (multipart above 100 MB). Unlimited stores since Sept 2026 — but the changelog is explicit that this buys no storage: 'Splitting the same data across more stores doesn't change those costs.' |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | vercel.com/docs/vercel-blob/usage-and-pricing | Hobby Included column: '1GB/month' storage, 'First 10 GB' data transfer, 'First 10,000' simple ops, 'First 2,000' advanced ops; 'you will not be able to access Vercel Blob if limits are exceeded ... wait until 30 days have passed' |
| 2026-10-21 | vercel.com/changelog/unlimited-vercel-blob-stores-on-every-p | published Sep 23, 2026: unlimited stores, but 'Splitting the same data across more stores doesn't change those costs' |
| 2026-10-21 | vercel.com/docs/vercel-blob | 'you can store files up to 5 TB' |
| 2026-10-21 | 1sxstfwepd7zn41q.public.blob.vercel-storage.com/blob-oYnXSVc | probe: curl -D - -> 200, Content-Length 2275823, Server: Vercel, X-Vercel-Cache: HIT, no auth |
More fields (1)
{
"dead_end": {
"failure_class": "quota",
"why": "1 GB/month of storage, TOTAL per Hobby team — not per project. Pricing table: 'Blob Storage Size | Regional | Usage-based | 1GB/month' for the Hobby Included column, alongside 'Blob Simple Operations | First 10,000', 'Blob Advanced Operations | First 2,000', 'Blob Data Transfer | First 10 GB'. Per-file ceiling is genuinely large: 'you can store files up to 5 TB' (multipart above 100 MB). Unlimited stores since Sept 2026 — but the changelog is explicit that this buys no storage: 'Splitting the same data across more stores doesn't change those costs.'",
"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
Vercel Deployment Storage / artifact store (Hobby, 30-day TTL) Storage
fails: quotaemail?card?Rretention-clamped
| Free tier | 10 GB of Deployment Storage per Hobby team, and that pool is what every retained deployment output draws from. This is the clearest example in the whole slot of a 'free tier' that is a build-artifact store, not storage. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Per-object cap | not stated |
| Retention | Deployment Retention defaults for Hobby are now 30 days for ALL four states — canceled, errored, pre-production, production (Pro gets 180 days preview / 1 year production) (30 days) |
| Egress | Served by Vercel's CDN at no separate charge while the deployment exists (Fast Data Transfer Hobby allowance is 100 GB, shared across all Vercel services). Deployment URLs are public unless Deployment Protection is on. |
| Identity | email (placeholder) not published |
| Limits |
THE TTL IS THE STORY, and it tightened twice in 2026. Deployment Retention defaults for Hobby are now 30 days for ALL four states — canceled, errored, pre-production, production (Pro gets 180 days preview / 1 year production). The Sept 16, 2026 changelog cut it further: 'Each Hobby project now keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type, regardless of age. Preview deployments no longer get their own protection.' Deletion runs within 48 hours of eligibility, then a recovery window, then permanent removal. CLI source upload is capped at 100 MB per deploy (Hobby), 15,000 files. |
| Binding | retention-clamped a clock, not a quota: bytes leave whether or not the client is finished with them |
| Interface | rest, git, rclone, cli rest |
| Tooling | vercel deploy CLI / Git integration / REST Deployments API. No object-level API at all — you cannot address a file inside a deployment except by URL. No rclone backend and no possible wrapper, because there is no list/put primitive. |
| Composes with | None useful. 10 GB is a hard pool shared by every project on the team, and going over it 'can block you from deploying until you free some up'. 200 projects on Hobby but one shared 10 GB — the multiplier actively works against you here. |
| Reliability | Hard, automatic, irreversible expiry after 30 days. Any file hosted only in a deployment URL is gone a month later. Treat as a 30-day hot tier and nothing else. |
| Notes | 10 GB of Deployment Storage per Hobby team, and that pool is what every retained deployment output draws from. This is the clearest example in the whole slot of a 'free tier' that is a build-artifact store, not storage. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | vercel.com/docs/deployment-retention | default table: 'Hobby | 30 days | 30 days | 30 days | 30 days' vs 'Pro and Enterprise | 30 days | 90 days | 180 days | 1 year'; last_updated 2026-09-16 |
| 2026-10-21 | vercel.com/changelog/hobby-projects-now-retain-fewer-deploym | published Sep 16, 2026: 'Hobby teams get 10GB of Deployment Storage'; 'keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type'; 'deployments outside those exceptions are now deleted immediately instead of after 30 days' |
| 2026-10-21 | vercel.com/docs/limits | 'Projects | 200' on Hobby; 'the maximum size of the source files that can be uploaded is limited to 100 MB for Hobby'; '15,000' source files |
More fields (1)
{
"dead_end": {
"failure_class": "not-storage",
"why": "10 GB of Deployment Storage per Hobby team, and that pool is what every retained deployment output draws from. This is the clearest example in the whole slot of a 'free tier' that is a build-artifact store, not storage.",
"retry_when": "never; it is not storage",
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (6)
$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.per_object_cap.notesnot-extracted$.per_object_cap.statednot-extracted$.retention.notesnot-extracted
vercel edge config / global config Storage
fails: quotaemail?card?R
| Free tier | Renamed to Global Config, and the Free limits are absurd for storage: 'Maximum store size / 1 MB' and 'Maximum number of stores (total) / 1' on Hobby. One megabyte. This is a feature-flag st unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | not recorded |
| Reliability | Renamed to Global Config, and the Free limits are absurd for storage: 'Maximum store size / 1 MB' and 'Maximum number of stores (total) / 1' on Hobby. One megabyte. This is a feature-flag st |
| Notes | Renamed to Global Config, and the Free limits are absurd for storage: 'Maximum store size / 1 MB' and 'Maximum number of stores (total) / 1' on Hobby. One megabyte. This is a feature-flag st |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | vercel.com/docs/storage/edge-config/edge-config-limits | Renamed to Global Config, and the Free limits are absurd for storage: 'Maximum store size / 1 MB' and 'Maximum number of stores (total) / 1' on Hobby. One megabyte. This is a feature-flag st |
More fields (1)
{
"dead_end": {
"failure_class": "quota",
"why": "Renamed to Global Config, and the Free limits are absurd for storage: 'Maximum store size / 1 MB' and 'Maximum number of stores (total) / 1' on Hobby. One megabyte. This is a feature-flag st",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded
vercel hobby (static deployments) Storage
fails: quotaemail?card?R
| Free tier | 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | not recorded |
| Reliability | 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo |
| Notes | 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | vercel.com/docs/limits | 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo |
| 2026-10-21 | vercel.com/changelog/hobby-projects-now-default-to-30-day-de | cited as the basis of the rejection: 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo |
| 2026-10-21 | vercel.com/docs/deployment-storage | cited as the basis of the rejection: 100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo |
More fields (1)
{
"dead_end": {
"failure_class": "retention",
"why": "100 MB max static upload per deployment on Hobby, and since Apr 29 2026 Hobby deployment retention is capped at 30 days ('Deployments outside your retention window will be automatically remo",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded