# Surge.sh

> surge.sh | Storage; 2 records: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/surge/ | JSON https://fshy.ajam.dev/api/v1/entity/surge.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## Surge.sh

- `storage/surge-sh` | qualifies-with-caveat | evidence reported | binding per-object-cap | category paas
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://surge.sh
- free tier: Free plan: unlimited projects and unlimited publishes; each project capped at 450 MB and 10,100 files. No account-level byte quota. | unit: objects | metered on: unstated | read on: 2026-10-21 | source: [1]
- per-object cap: no per-file cap documented but it inherits the project cap | source: [1] | note: not stated
- retention: not stated | source: [1] | note: not stated
- egress: No bandwidth quota or metering is documented anywhere on the free plan; every project is served from all 10 of Surge's own edge nodes ('Every project—free or paid—serves from all of them'). | metered: no
- identity: anonymous
- interface: rest, cli
- limits:
  - per-ip-shaping: 1 TiB/day [1]
  - write-gated: Application too large') [1]
  - per-object-cap (binding): no per-file cap documented but it inherits the project cap [1]
- limits note: 450 MB and 10,100 files per project (hard: 'Aborted - Unable to publish. Application too large'); no bandwidth figure published; no per-file cap documented but it inherits the project cap. Re-publishing replaces the whole project (full-sync deploy), so appending one file re-uploads the directory.
- interface detail: rest
- tooling: Official `surge` CLI (npm, ~free) and a documented raw REST deploy API: PUT /:domain with Basic auth, Content-Type: application/gzip, a gzipped tarball body plus file-count and project-size headers. That is directly scriptable, no CLI needed.
- composes with: Unlimited projects x 450 MB = arbitrary total per account; unlimited free accounts (email+password in-terminal, no card). Sharding is natural because each project is just a folder.
- reliability: Deploy is full-replace, not incremental — a slow link makes each publish expensive. Free tier has no stated SLA and no published bandwidth ceiling, so behaviour at 1 TiB/day is unproven.
- notes: the same as the free tier
- evidence:
  - [1] 2026-10-21: 'Projects are limited to 10,100 files and 450 MB.'
  - [2] 2026-10-21: 'The core of Surge costs nothing, without trial windows or project caps: Unlimited projects and publishes'
  - [3] 2026-10-21: 'PUT /:domain ... The body is a gzipped tar archive ... file-count / project-size headers'
  - [4] 2026-10-21: probe: curl -D - -> HTTP/1.1 200, Server: cloudflare, Accept-Ranges: bytes (edge is CF-fronted)
- sources:
  - [1] https://surge.sh/docs/cli/publishing
  - [2] https://surge.sh/docs/platform/plans
  - [3] https://surge.sh/docs/api/deploys
  - [4] https://surge.sh/

## surge.sh as a bulk archive (naive)

- `storage/surge-sh-as-a-bulk-archive` | fails-quota | evidence reported | binding none | category rejected-provider
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://surge.sh/docs/cli/publishing
- free tier: 450 MB / 10,100 files per project and every publish is a full gzipped-tarball replace, so a 450 MB project costs 450 MB of upload per change. Only viable if projects are written once and… | unit: none | metered on: none | read on: 2026-10-21 | source: [1]
- per-object cap: not recorded | source: [1] | note: not recorded
- retention: not recorded | source: [1]
- egress: not recorded | metered: no
- identity: email
- interface: unknown
- tooling: not recorded
- composes with: the same as tooling
- reliability: the same as the free tier
- notes: the same as the free tier
- extras:
  - dead_end.failure_class: quota
  - dead_end.why: 450 MB / 10,100 files per project and every publish is a full gzipped-tarball replace, so a 450 MB project costs 450 MB of upload per change. Only viable if projects are written once and…
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: 450 MB / 10,100 files per project and every publish is a full gzipped-tarball replace, so a 450 MB project costs 450 MB of upload per change. Only viable if projects are written once and…
  - [2] 2026-10-21: cited as the basis of the rejection: 450 MB / 10,100 files per project and every publish is a full gzipped-tarball replace, so a 450 MB project costs 450 MB of upload per change. Only viable if projects are written once and sha
- sources:
  - [1] https://surge.sh/docs/cli/publishing
  - [2] https://surge.sh/docs/api/deploys