Platform
How Lyvyl stores, delivers and transforms your files, and where it runs.
Storage
Each bucket belongs to one storage region. Uploads are written to three zones inside that region before we confirm them, and a read after a successful write always returns the new data.
Lifecycle rules delete or archive files by age or prefix, so temporary uploads and old builds clean themselves up.
- Object sizeUp to 5 GB per request, 5 TB with multipart uploads
- VersioningOptional per bucket, with up to 90 days of history
- ConsistencyRead-after-write for new and overwritten files
Delivery
Connect your own domain to a public bucket and files are served from the edge location closest to each visitor. Cached copies follow the cache headers you set, and a purge clears a path everywhere in under a minute.
Private files stay private: share them with signed links that expire after a time you choose.
- ProtocolsHTTP/3 over QUIC and HTTP/2, TLS 1.3
- CertificatesIssued and renewed automatically for your domains
- Signed linksExpiring URLs for private downloads
Image and video processing
Request any size of an image by adding parameters to its URL. The original stays untouched; each derived size is generated once and then served from cache.
https://files.example.com/photos/lake.jpg?w=640&fmt=autoSee image URL parameters for the full list.
Security
Files are encrypted at rest with AES-256 and in transit with TLS 1.3. API keys can be limited to specific buckets and to read-only access, and every key change is recorded in the account audit log.
Regions
Storage regions hold your data. Edge locations cache public files and answer requests.
| Code | City | Role |
|---|---|---|
| fra1 | Frankfurt | Storage and edge |
| ams1 | Amsterdam | Storage and edge |
| hel1 | Helsinki | Storage and edge |
| iad1 | Ashburn | Storage and edge |
| waw | Warsaw | Edge |
| par | Paris | Edge |
| mad | Madrid | Edge |
| sto | Stockholm | Edge |
| yyz | Toronto | Edge |