Fully Managed RustFS
as a Service

Deploy RustFS as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

RustFS is an open-source object storage server written in Rust that speaks the Amazon S3 API. Buckets, access keys, versioning and erasure coding across disks behave the way your existing tools expect, while the data sits in the datacenter region you pick rather than one chosen for you.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

RustFS

RustFS

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
RustFS Preview Image

ABOUT THE SOFTWARE

What is RustFS

RustFS is an open-source, S3-compatible object storage server written in Rust. It stores objects in buckets, protects them with erasure coding across disks, and exposes the same API surface that applications already use to talk to Amazon S3.

RustFS is published under the Apache 2.0 licence by RustFS, Inc. That matters more than it normally would for a storage project: the previous default choice in this category moved to a network copyleft licence, then removed most of its management console from the free edition, and finally stopped maintaining the open repository altogether. RustFS was started as a permissively licensed answer to that, and the licence puts no restriction on who may run it as a service.

Operationally it is a single Rust binary with no runtime to install alongside it. It runs on one disk, on several disks in one node with erasure coding, or across nodes. It ships a web console for buckets, users and policies on a separate port from the S3 API, an access-key and policy model modelled on AWS IAM, optional OpenID Connect login, and OpenTelemetry traces, metrics and logs. The project also exposes an OpenStack Swift API for older clients.

FEATURES

What RustFS does

RustFS covers the object storage surface most applications actually call: buckets and objects, multipart uploads, presigned links, versioning, access keys and policies, replication between buckets, and erasure coding that survives losing a disk.

S3-compatible API

Buckets, objects, multipart uploads and presigned URLs answer on the standard S3 endpoints, so the AWS CLI, rclone, s3cmd and the usual SDKs work unchanged.

Erasure coding with healing

Objects are split into data and parity shards across separate disks. Losing a disk up to the parity count costs you nothing, and shards rebuild in the background.

Bucket versioning

Overwrites and deletes keep prior versions instead of destroying them, which is what makes an accidental sync in the wrong direction recoverable.

Object Lock and retention

Buckets can hold objects under a retention period so restore points cannot be quietly removed by a client that has the keys.

Bucket replication

Objects written to one bucket can be mirrored to another, either on the same instance or to a second S3 endpoint you control.

Access keys and policies

An access-key model with AWS-style policy documents, plus multi-tenancy and optional OpenID Connect login for people rather than machines.

Web console

Buckets, users, keys and policies are managed from a browser console served on its own port, not only from a command-line client.

OpenTelemetry output

Traces, metrics and logs are emitted in OpenTelemetry format, so the instance drops into a Prometheus and Grafana setup without a shim.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to RustFS the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed RustFS

Most people arriving at RustFS were running something else. Their object store lost its management console in a free-edition trim, then stopped being maintained in the open. Moving is straightforward. Running the replacement safely is where the work actually is.

Object storage looks deceptively simple to self-host. One binary, one port, a bucket, done. What the quickstart leaves out is everything that protects the bytes afterwards: choosing an erasure layout you can live with, keeping headroom on the volume, terminating TLS without breaking request signing, watching for a failing disk, and holding a copy somewhere else.

Two RustFS failure modes are worth naming, because both are cheap to avoid and expensive to meet. The first is disk layout. Several people have built what looked like a multi-disk erasure setup by pointing RustFS at several directories on one physical drive, putting every shard of a stripe in the same failure domain. Upstream now refuses to start that way, and an environment flag overrides the refusal. The second is running a volume to capacity: there are reports of internal metadata damage after a volume filled, where the filesystem underneath checked out clean but the store would no longer assemble a read quorum.


REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run RustFS on DANIAN

Three shapes of team that keep showing up in object storage conversations: one moving finished work off a metered bucket, one holding backups for other people, and one parking research output that a pipeline reads back by URI.

SIX-PERSON VIDEO STUDIO

Finished project archives off a metered bucket

Delivered masters were sitting in a metered cloud bucket where every client re-download reappeared on the invoice. They now push completed projects to a RustFS instance in the region their editors work from, with versioning on so a re-export never overwrites the approved master.

TWO-PERSON MANAGED-SERVICES SHOP

Client backup repositories written by Restic

Restic writes each client's repository to its own bucket with a separate access key, so one compromised endpoint cannot read another client's data. Retention is set on the bucket rather than trusted to the agent, and the instance sits away from the offices it protects.

FOUR-PERSON RESEARCH GROUP

Sequencing output a pipeline reads back by URI

Their workflow tool reads and writes S3 URIs, so the storage had to speak the API rather than look like a network share. Raw reads land in one bucket and processed outputs in another, with the console on a separate hostname for the two people who administer it.

COMPARISON

Four ways to run RustFS

Four realistic paths to S3-compatible storage, costed against one scenario: a terabyte held, roughly a hundred gigabytes read back each month. The interesting column is not the cheapest number, it is what each path asks you to carry.

Path1 person5 people10 peopleWhat you also carry
Metered cloud object storage (Amazon S3 Standard)~$24/mo~$24/mo~$24/moCost tracks stored data and egress, not people: the same shape at 5 TB is about $154/mo and at 10 TB about $316/mo, before request charges.
Self-host on a rented server$25-60/mo$25-60/mo$25-60/moServer plus a terabyte volume, then the erasure layout, TLS, proxy signing rules, storage alarms, patching and your own off-site copy.
Home server (Synology DS423, four bays)~$780-1,100 once~$780-1,100 once~$780-1,100 onceRoughly $1.20 a month in electricity, plus your home uplink, your power cuts, and a second location for the backup you still need.
DANIAN managed RustFS€9/mo€9/mo€9/moInstance, hardware, updates, daily off-site backups, monitoring, SSL and support. Storage above the included allowance is a paid add-on.

Scenario: 1 TB stored, about 100 GB egress per month, list prices checked in August 2026. Metered cloud storage is billed by data rather than by headcount, which is why its figure does not move across the three columns either.

BY INDUSTRY

RustFS for specific industries

Object storage gets picked for different reasons in different rooms. These four sectors put genuinely different demands on RustFS: file sizes, the standard the data has to satisfy, and how quickly it has to come back.

Mastered deliverables are packaged to SMPTE ST 2067, the IMF specification, which means a title is not one file but a directory of essence and metadata components that must stay together and stay unaltered. Object storage suits that better than a shared drive, because each component keeps its own key and version history. The volumes are the hard part: one hour of UHD ProRes 422 HQ lands at roughly 440 GB, so a modest slate fills terabytes. We enable bucket versioning by default for studios so a re-export never destroys the approved master, raise the proxy body limits so multipart uploads of very large essence files complete without retries, and keep the console on a separate hostname from the S3 endpoint.

Backup practice has settled on the 3-2-1-1-0 rule: three copies, two media types, one off-site, one immutable or offline, and zero errors on a tested restore. RustFS covers the off-site and immutable parts, because a bucket can hold objects under a retention period that a compromised client key cannot simply delete. A shop protecting forty endpoints accumulates around ten terabytes of retained restore points. We give each client its own bucket and access key so one breached endpoint cannot enumerate another client's data, set retention on the bucket rather than trusting the backup agent, and place the instance away from the offices it protects.

Groups funded under the NIH Genomic Data Sharing Policy are expected to retain and share primary sequence data, not just the paper that came out of it, which turns storage from a lab expense into a condition of the grant. The files are large and long-lived: one human genome at 30x coverage runs to roughly 100 to 200 GB once raw reads and aligned output are both kept. Workflow tools such as Nextflow address inputs and outputs as S3 URIs, so a POSIX share is the wrong shape. We keep raw reads and processed output in separate buckets with distinct keys so a rerun cannot overwrite source data, and watch headroom closely because sequencing arrives in bursts.

Container registries implement the OCI Distribution Specification, and nearly every registry worth running stores its blobs in an object store behind that API rather than on local disk. The same instance usually ends up holding build artifacts and package caches too. The workload shape is unusual: registry traffic is dominated by many small objects in the kilobyte range rather than a few large ones, which is the case RustFS was built to be fast at. We raise file descriptor limits because a busy registry opens far more handles than a quiet bucket, and keep the S3 endpoint on its own hostname at the root path so signed requests from your build agents validate first time.

FAQ

Frequently asked questions

Three groups: how RustFS behaves and what we tune, how you get your existing objects into it, and how the platform underneath works.

01

Technical and configuration

It implements the core S3 surface: buckets, objects, multipart uploads, presigned URLs, versioning, access keys and policy documents. The AWS CLI, rclone, s3cmd and the standard SDKs work against it unchanged. A few areas such as lifecycle rules are still marked as under testing upstream, so we test your specific client during the trial.
Each object is split into data shards plus parity shards written to separate disks, so the store survives losing up to the parity count. A common layout keeps sixteen data shards and four parity shards, spending about a fifth of raw capacity on protection. The layout is fixed at initialisation and cannot be changed afterwards.
We never do this. Pointing the store at several directories on one drive looks like a protected multi-disk setup and is not one, because every shard of a stripe shares a single failure domain. Upstream now refuses to start that way, and the environment flag that overrides the refusal is never set on our fleet.
We pin the S3 API to the root path of its own hostname and give the console a separate hostname. RustFS assumes it owns the root path, so serving the API from a sub-path breaks signature validation and presigned links. We also raise proxy body and header limits so large multipart uploads survive the hop in front of the container.
We alarm long before it does. There are reports of internal metadata damage after a RustFS volume reached capacity, where the filesystem underneath checked out clean but the store would no longer assemble a read quorum. We watch headroom and grow the storage while that is still a change rather than a recovery.
Both are present. Versioning keeps prior copies through overwrites and deletes, and Object Lock holds objects under a retention period so a client with valid keys cannot quietly remove restore points. Upstream has fixed several retention enforcement defects recently, so we would rather you treat it as protection against accident than as a statutory records vault.
The project supports multi-node erasure coding, but upstream still marks distributed mode as under testing. On DANIAN each instance runs as a single node with erasure coding across its volumes, plus our own encrypted daily copy held in a second datacenter. That is the honest shape of what we operate today.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes, by two routes. Either copy objects into a fresh RustFS bucket with rclone or a mirror command, or use the binary replacement path where RustFS starts against the existing data directory.
Object data, tags, versions, bucket metadata and lifecycle settings carry across on the replacement path. Site replication, event notifications and directory-service logins do not. Access keys and policies are recreated by hand.
Yes. rclone or the AWS CLI sync command reads from the existing bucket and writes into RustFS. Bucket policies, lifecycle rules and object tags are stored differently and get recreated. Budget for the outbound transfer charge on the source side, which is usually the largest one-off cost of the whole move.
The trial runs seven days with no card. Copy a representative slice of your buckets across, point one client at it and check that your tooling signs requests correctly. If you carry on afterwards the same instance continues, so nothing is rebuilt and nothing is copied twice.

03

Billing, support and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed RustFS for 7 days

No card. Cancel from the dashboard.