Object Storage
Object Storage is an S3-compatible storage service for files of any size — user uploads, application backups, media assets, build artifacts, dataset exports, machine-learning datasets.
It speaks the standard AWS S3 API end to end: bucket operations, object operations, multipart uploads, presigned URLs, AWS Signature v4 authentication, path-style and virtual-hosted addressing. Any tool or SDK that talks to Amazon S3 works with Runsite Object Storage by changing only the endpoint URL.
Pricing & plans
Comparing options or looking for the free tier? See plans, specs and pricing on the S3-compatible object storage page.
What you get
Section titled “What you get”- A dashboard in your workspace to create buckets, upload and browse files, generate access keys and share signed download links — without writing a single line of code.
- A public S3 endpoint at
https://s3.runsite.appthat any S3 SDK or CLI can talk to directly. - Per-bucket access keys so you can give one app, one CI job, one user only the access they need.
- Public buckets for static assets you want to serve directly over HTTPS (avatars, product images, public downloads).
- Presigned URLs for direct browser uploads and time-limited downloads — your backend never has to proxy bytes.
Concepts
Section titled “Concepts”| Bucket | A container for objects, identified by a name unique inside your workspace (3–63 characters, lowercase). |
| Object | A single file, identified by a key inside a bucket. Objects can be of any size. |
| Access key | A pair of access_key_id and secret_access_key used to authenticate API requests. Scoped by permission set and optionally to a single bucket. |
| Presigned URL | A short-lived, signed URL that grants access to a specific object without exposing credentials. |
| Public bucket | A bucket whose objects are readable anonymously over HTTPS — handy for static assets. |
Endpoint
Section titled “Endpoint”There is a single S3 endpoint, regardless of where your data is stored:
https://s3.runsite.appBoth standard S3 addressing styles are supported:
- Path-style —
https://s3.runsite.app/<bucket>/<key>(recommended, what the dashboard shows) - Virtual-hosted style —
https://<bucket>.s3.runsite.app/<key>
For the region_name field that some SDKs require, use auto. Runsite stores all data in EU jurisdiction.
Where to next
Section titled “Where to next”- Dashboard — buckets, files, keys and settings in the UI.
- Access keys — generating, scoping and revoking credentials.
- Connecting clients — boto3, AWS SDK, AWS CLI, rclone and more.
- Presigned URLs — direct browser uploads and time-limited downloads.
Storing user uploads from a web app?
Generate a per-bucket key with read & write permissions, store it in your service environment variables and use any S3 SDK against the Runsite endpoint. Browser-side uploads should go through a presigned URL so your access keys never reach the client.