One plan. The list below is the whole product; there is no enterprise tier hiding the good parts.
| Capability | Details |
|---|---|
| Uploads | HTTP multipart, a small CLI, or a dashboard drop zone. 100 MB per object, 10 GB per project. |
| Versioning | Content-addressed paths. Previous versions remain available for 90 days after they stop being referenced. |
| Compression | Brotli 11 and gzip 9 variants generated at upload for text-like types. Binary types are stored as-is. |
| Cache policy | immutable, max-age=31536000 for hashed paths; no-cache with ETag for named aliases. |
| TLS | Automatic certificates, HTTP/2, HSTS. Plain HTTP redirects to HTTPS. |
| Custom domains | Up to five per project. CNAME verification, certificates issued within minutes. |
| Limits | Fair-use bandwidth of 2 TB per month per project, then throttled rather than billed. |
| Logs | Aggregated counters only: requests, bytes, status classes. No per-visitor records. |
No edge functions, no image transformation pipeline, no A/B routing. Those are good products, but they are different products. Keeping the surface small is what lets a two-person team run this reliably.
Most teams move in an afternoon: upload the current build, add the domain, switch the DNS record. Because paths are content-addressed, you can run old and new hosting in parallel and compare before cutting over.