Skip to content

Object storage

Each project gets a bucket. How to put things in it, how to mount it into a workload, and the one way it is not a disk.

Every project has one bucket, and everything in the project shares it. It belongs to the project rather than to any workload, so it outlives the things that read it — deleting a workload does not touch the data.

Putting things in it

From the browser. The project’s Files view lists the bucket and handles upload and download, including large files. It shows how much you have used against your quota.

From a workload. Mount it — see below.

There is no S3 SDK or CLI access today. The endpoint-plus-scoped-credential path that a write-heavy application would want is designed but not built, so if your plan was aws s3 cp from your laptop, it is not available yet.

Mounting it into a workload

A workload can opt in to mounting the project bucket as a directory. It appears at /mnt/shared by default, and the mount path is configurable — deliberately not /data, which collides with too many images.

Credentials are handled for you. They are rotated on a schedule without interrupting anything: a pod that mounted before a rotation keeps working on the credential it already holds, and picks up the new one when it next restarts. There is nothing for you to store or renew.

It is not a filesystem

This is the part worth reading twice, because the failure is confusing rather than loud.

The mount is object storage wearing a directory’s clothes. It supports sequential, whole-object writes. It does not support:

  • appending to an existing file
  • writing to the middle of a file
  • renaming a file in place

Applications that assume a POSIX filesystem — databases, anything keeping a write-ahead log, anything that appends — will misbehave on it, sometimes subtly.

What it is very good at is the case it was built for: reading datasets and model weights, and writing whole output files once.

Quotas

Each project has a storage quota, enforced by the storage backend at write time rather than by a periodic check. A write past the limit is refused at the moment it happens; nothing is silently truncated.

Any project member can see usage — bytes, object count, and the quota — in the Files view. Changing the quota is a platform-administrator action, because it is an allocation decision rather than a project setting.

Storage is not a billed dimension yet.