Built-in, S3-compatible object storage is now available on Upsun Cloud

If your application stores large volumes of files, such as product images, video, documents, or user uploads, you've probably had to run a separate object storage service alongside Upsun. That meant another account to set up, another integration to maintain, and another bill to reconcile.

Object storage is now built into Upsun Cloud. You set it up like any other resource, your app connects to it through the standard S3 API, and it's billed with the rest of your project. It's already proven in production, running enterprise workloads since April 2026, including for one of Europe's largest retailers.

What is built-in object storage?

Key takeaway: object storage is now a resource you set on Upsun, just like CPU, memory, or disk.

Built-in object storage is S3-compatible storage you declare like any other Upsun resource, fully managed by the platform and billed on your existing invoice.

Object storage is designed for large or growing volumes of unstructured data: uploads, media, generated files, exports, and application-level backups. Your app reads and writes files through the S3 API rather than a folder on disk.

To turn it on, open your project in the Console, go to Configure resources, and toggle Enable object storage. Or use the CLI:

upsun resources:set --object-storage myapp:524288

The size is set in MB, so 524288 is the 512 GB minimum. Upsun creates a bucket for your app and passes the connection details to it automatically.

Why it matters for asset-heavy applications

Key takeaway: applications with large asset libraries can now run entirely on Upsun, without an external storage provider.

Until now, applications with large asset libraries needed to bring their own object storage to run on Upsun. That's no longer the case. Object storage is a strong fit for:

• Asset-heavy applications: Pimcore, Shopware, Ibexa, DAM and PIM systems, and e-commerce sites with large product catalogs
• Media-heavy applications: images, video, documents, and user-generated content
• Other large or growing data: AI and machine learning artifacts, logs, exports, and application-level backups

If you already pay for S3 or another object storage provider alongside your Upsun project, you can bring that storage onto the platform. That's one less account to secure, one less integration to maintain, and one less invoice to manage.

For large volumes of data, object storage also costs less per GB than standard Upsun disk storage.

How it works

Key takeaway: your app connects through the standard S3 API, and Upsun handles the credentials, backups, and environment cloning.

• Standard S3 API. The S3 SDKs, libraries, and tools your app already uses keep working, including the AWS CLI. Point your S3 client at the endpoint Upsun provides and use path-style addressing. There's no need to rewrite your application.
• Credentials handled for you. Upsun generates the connection details, including the endpoint, access key, secret key, and region, and makes them available to your app as environment variables. Read them at runtime rather than hardcoding them, since they can change when the app is redeployed.
• Included in backups. When you back up an environment, the contents of its bucket are backed up with everything else.
• Cloned with every branch. When you create a new environment from a branch, the bucket and its allocated size are cloned along with the rest of the environment's data. Your preview environments work with the same assets as production.
• Private to your project. The bucket is reachable only over your project's internal network and isn't exposed to the public internet.
• Shareable across containers. Workers, other applications, and tasks in the same project can use an app's bucket through a relationship.

For setup details and code examples, see the object storage documentation.

Pricing

Key takeaway: You pay for the capacity you allocate, on your existing Upsun invoice, with no per-request fees.

• Storage: €0.0833 per GB per month, billed on allocated capacity and prorated hourly
• Minimum: 512 GB, adjustable in 512 GB steps
• Per environment: each environment is billed for its own allocation. For example, 1 TB allocated across 6 environments is billed as 6 TB.
• Backups: €0.075 per GB per month, billed on allocated capacity as a separate line item
• Included: API requests and the compute running the service. There are no per-request fees.
• Data transfer: no separate egress fee for object storage; outbound traffic counts toward your project’s bandwidth like any other traffic

Billing is based on the space you allocate, regardless of how much data you actually store. Pausing an environment doesn't release that allocation, so object storage keeps billing while an environment is paused.

Object storage isn't available on trial projects. For rates in other currencies, see the pricing page.

What to know before you start

Key takeaway: each app gets one private bucket, and a few S3 features aren't supported yet.

• One bucket per app. Each app gets a single bucket, named after the app. Other containers can share it, but buckets can't be moved between apps.
• No public access. Files can't be served directly from the bucket to visitors, because the bucket is only reachable inside your project.
• Some S3 features aren't available. Bucket versioning, object locking, server-side encryption, access control lists, bucket policies, and lifecycle policies aren't supported.
• Turning it off deletes the bucket. Setting the size to 0, or removing the app, permanently deletes the bucket and its contents on the next deployment. There's no soft delete or retention period, so back up anything you need first.

Get started

Key takeaway: object storage is available now on Upsun Cloud projects, from the Console or the CLI.

1. In the Console, open your project and click Configure resources, then toggle Enable object storage. Or run upsun resources:set --object-storage <APP_NAME>:524288 from the CLI.
2. Configure your S3 client with the endpoint and credentials Upsun provides, using path-style addressing.
3. Start reading and writing files through the S3 API.

Read the object storage documentation for full setup steps, or talk to an expert about moving your existing storage onto Upsun.

Frequently asked questions (FAQ)

Can I use my existing S3 tools and SDKs?
Yes. Object storage uses the standard S3 API, so existing SDKs, libraries, and the AWS CLI work with it. Configure your client with the endpoint and credentials Upsun provides, and use path-style addressing.

How is object storage billed?
Object storage costs €0.0833 per GB per month, billed on the capacity you allocate and prorated hourly. The minimum is 512 GB per environment. Backups are billed separately at €0.075 per GB per month.

Am I charged for object storage when an environment is paused?
Yes. Pausing an environment stops CPU and memory charges, but object storage and its backups are billed on allocation, and pausing doesn't release the allocation. To stop object storage charges, set the allocation to 0. This deletes the bucket, and existing backups remain billable until they expire.

Are there per-request or egress fees?
No. API requests are included, and data transfer counts toward your project's existing bandwidth.

Can I serve files publicly from a bucket?
Not directly. The bucket is only reachable over your project's internal network.

Is object storage available on the free trial?
No. Object storage isn't available on trial projects.

What happens if I turn object storage off?
The bucket and all its contents are permanently deleted on the next deployment. There's no soft delete or retention period, so back up anything you need first.

Should I use object storage or a mount?
Use object storage for large or growing volumes of files accessed through the S3 API. For small amounts of file data that a single instance reads and writes through the filesystem, a persistent mount is usually a better fit.