Fully Managed SeaweedFS
as a Service

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

SeaweedFS is an open-source distributed object store — an S3 API for blobs, media, backups, and data lakes — pairing the convenience of cloud object storage with the control of running the endpoint yourself. It serves billions of files at one disk read each, and it is the Apache-2.0 store many teams moved to after MinIO stopped open-source development in 2026.

✓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

SeaweedFS

SeaweedFS

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 →
SeaweedFS Preview Image

ABOUT THE SOFTWARE

What is SeaweedFS

SeaweedFS is an open-source distributed storage system that speaks the S3 API. It is built to hold billions of files and serve each one in a single disk read, which makes it a fast home for blobs, media, backups, and data-lake tables.

SeaweedFS is licensed under Apache 2.0 and is maintained by Chris Lu and a wide contributor base, with more than 35,000 stars on GitHub. It is written in Go and was inspired by Facebook's Haystack paper: each file needs only about 40 bytes of metadata , and a read is a single disk seek rather than a walk through layers of indirection.

The system splits into four roles. A master tracks volumes and topology, volume servers hold the actual data, a filer overlays directories, paths, and permissions, and an S3 gateway serves the Amazon S3 API. The filer keeps its metadata in a pluggable store — PostgreSQL, MySQL, Redis, Cassandra, and others — which is what lets a SeaweedFS cluster scale its namespace independently of the data it holds. That separation is the source of both its speed and the one operational decision that matters most, covered below.

FEATURES

What SeaweedFS does

SeaweedFS is more than a plain bucket store. It carries the S3 features applications expect, plus filesystem and data-lake access paths, replication options, and tiering to other clouds. The capabilities below are the software's own, available on every managed instance.

S3-compatible API

Buckets, multipart uploads, versioning, lifecycle policies, and object lock with retention modes, reachable by the aws CLI, rclone, restic, and the mc client.

Pluggable filer stores

The filer keeps metadata in PostgreSQL, MySQL, Redis, Cassandra, and more, so the namespace scales independently of object data.

Erasure coding

Store warm-to-cold data with parity shards instead of full copies, cutting raw storage while keeping durability.

Cross-datacenter replication

Asynchronously replicate buckets to a second region or cluster for a geographically separate copy.

FUSE mount and WebDAV

Reach the same store as a mounted filesystem or over WebDAV, alongside the S3 endpoint, for tools that do not speak S3.

Cloud tiering and Cloud Drive

Mount an external S3, GCS, or Azure bucket through the filer and cache it locally, fronting existing cloud data.

Encryption at rest

Encrypt objects on the volume servers with a separate key per file, held in the filer store and applied transparently on read.

Iceberg and data-lake tables

Serve Apache Iceberg tables and Parquet data over S3 for query engines such as Spark, Trino, and DuckDB.

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 SeaweedFS 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 SeaweedFS

After MinIO stopped open-source development in 2026, teams that wanted a self-hosted S3 endpoint went looking for an actively maintained, Apache-2.0 replacement. SeaweedFS is the most common landing spot — but running it well is more than starting one process.

A working SeaweedFS deployment is not a single binary. You run a master, one or more volume servers, a filer, and the S3 gateway, and you decide how the filer stores its metadata, how data is replicated, and how volumes are compacted and backed up. Each of those is a real decision with a real failure mode behind the wrong default.

The decision that catches most people is the filer metadata store . Out of the box, SeaweedFS uses an embedded LevelDB store. It supports only one filer and tops out near 2,000 writes per second, and — this is the part that hurts — the filer store is your namespace. Lose or corrupt it and buckets can disappear even though every byte of object data is still sitting on the volume servers. There is a documented case of buckets vanishing under heavy deletes with the wrong index variant. The second trap is replication: the default is 000 , a single copy, so losing one volume server loses the data on it. Neither default is wrong for a laptop demo; both are wrong for production.

REVIEWS

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

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

USE CASES

Three teams who run SeaweedFS on DANIAN

SeaweedFS fits anywhere an S3 endpoint does, but the reasons differ by team. Here are three setups that show what people change when they move from a metered bucket or a DIY install to a managed instance.

7-PERSON SAAS TEAM

Leaving MinIO for an Apache-2.0 S3 endpoint

They run the endpoint in Germany, with one bucket for user uploads behind the app and a second, object-locked bucket holding OpenTofu state. We back the filer with PostgreSQL and turn versioning on, so a bad deploy can roll the state back.

PHOTOGRAPHY STUDIO

Serving image libraries without per-request bills

Their proofing site reads the same hero images millions of times a month, which would rack up GET fees on metered storage. We put the endpoint near their audience, apply erasure coding to colder shoots, and sync new work nightly with rclone.

ANALYTICS TEAM

A private S3 store for Parquet and Iceberg

They write Parquet partitions through the S3 API and query them with DuckDB and Trino. We run the filer on PostgreSQL so listings across thousands of files stay fast, and keep the store in one region to sit close to their compute.

COMPARISON

Four ways to run SeaweedFS

Say you want a small private S3 endpoint — app blobs, backups, a staging mock — with real traffic on it. Here is what each path costs in money, in metered fees, and in your time. The figures are monthly and use published 2026 rates.

PathWhat you payEgress & requestsYour timeYour own endpoint?
Managed object storage(Amazon S3)$0.023/GB stored. A 30 GB store is cents, but the bill is metered and grows with use.$0.09/GB egress, plus per-request fees ($0.005 per 1,000 writes, $0.0004 per 1,000 reads). Real bills run 2–3× the storage line.Low — it is hostedNo — data sits with the provider
Self-host on a VPS~$24/mo for a 2 vCPU / 4 GB production-class VPS, plus ~$5 backup storage and ~$15 monitoring ≈ $44/mo.None billed, but you run the master, volume servers, filer, and an external metadata database, plus replication and compaction yourself.5–10h setup, then 1–2h/mo — €100–280/mo effective with time costedYes
Home serverHardware such as a Synology DS923+ (~€650) or HP ProLiant ML30 Gen10 (~€800–1,500), amortised, plus power and a business uplink.None billed, but a static IP, off-site backup target, and your own operations are on you.2–4h/mo — €210–667/mo effective with time costedYes
DANIAN managed SeaweedFSFlat €9/month at the base tier (30 GB storage and 1,000 GB traffic included; storage and traffic scale with your approval).No egress fee. No per-request fee. Backups, SSL, updates, and monitoring included.0 hours — we run itYes — your S3 endpoint, in the region you choose

For a small endpoint that serves real traffic, the flat €9 wins because the metered egress and per-request fees on hosted object storage are where the bill actually grows. The honest exception is bulk cold archives: if you only need to park many terabytes you rarely read, pay-as-you-go stores like Backblaze B2 ($6/TB) or Wasabi ($6.99/TB) are cheaper per terabyte than scaling a managed instance — at the cost of per-request and minimum-retention fine print, and of the data living on someone else's endpoint rather than yours.

BY INDUSTRY

SeaweedFS for specific industries

Different fields put different demands on an object store: API parity for software teams, read economics for media, listing speed for analytics, and cheap restores for backup. Each section below shows how a managed SeaweedFS instance is set up for that work.

Software teams want an S3 API their code already speaks, without a third party holding the objects, and they want a licence that lets them ship the store inside a product. SeaweedFS's Apache-2.0 licence allows exactly that, which is why many moved to it after MinIO stopped open-source development in 2026. On DANIAN we back the filer with PostgreSQL and enable versioning and object lock, which makes a bucket safe to use as a state backend for tools such as Terraform and OpenTofu. A typical pattern is one bucket for user uploads behind the app and a second, locked bucket for infrastructure state. Each object carries about 40 bytes of metadata and is served in a single disk read, so a busy uploads bucket stays quick even as it passes tens of millions of files.

Media libraries are mostly large, warm files read far more often than written, and per-request charges on metered storage climb fast at that read volume. The relevant yardstick here is the cost per million reads: SeaweedFS serves files with one disk read and does not hot-spot on popular objects, and a managed instance carries no per-GET fee at all. On DANIAN we apply erasure coding to colder asset buckets to cut raw storage while keeping durability, and we place the endpoint in the region closest to the audience. A studio syncs its render output nightly with rclone and serves proofs over the S3 API, so a single image requested a few hundred million times a month does not turn into a GET-fee line the way it would on AWS S3.

Lakehouse queries scan thousands of Parquet files, and the constraint is usually listing performance, which depends on the filer metadata store rather than the object data. The embedded LevelDB default caps near 2,000 writes per second and supports only one filer; on DANIAN we run the filer against PostgreSQL so listings stay consistent and the namespace survives a restart. SeaweedFS exposes an Apache Iceberg path and an S3 endpoint that Spark, Trino, and DuckDB read directly. A data team writes Parquet partitions through the S3 API and queries them with DuckDB, holding steady read latency as a table grows past a billion small files, with the store kept in one region to sit close to the query engines.

Backup tools such as restic, rclone, and duplicati write to any S3 target, and the cost that bites is the one on the way back: restoring data. The relevant standard is the 3-2-1 backup rule — copies on separate media, one off-site — and SeaweedFS supports that with cross-datacenter replication for a second copy. AWS S3 charges $0.09/GB to read data out, so restoring a terabyte adds about $90 on top of storage; on DANIAN there is no egress fee, so a full restore costs nothing extra. We set object lock with a retention window so a backup bucket resists deletion, and confirm any capacity increase with you first. A managed-service provider points each client's restic job at its own bucket and tests a restore monthly without watching a transfer meter.

FAQ

Frequently asked questions

Three groups of questions: how we configure SeaweedFS, how migration and onboarding work, and how billing, support, and the platform behave. The technical answers describe the defaults we actually set on every instance.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

We back the filer with PostgreSQL, not the embedded LevelDB store SeaweedFS ships with by default. LevelDB supports only one filer and caps near 2,000 writes per second, and the filer store is your namespace. Postgres lets the namespace survive a restart and scale past that limit.
Yes. SeaweedFS exposes the S3 API with buckets, multipart uploads, versioning, lifecycle policies, and object lock with retention modes. The aws CLI, rclone, restic, and the mc client all work against it unchanged, so existing scripts point at the new endpoint with a URL change.
We monitor the free volume count and grow capacity before writes can fail. SeaweedFS rejects writes when no free volume exists, so we watch that signal and add volumes ahead of it. Any resource increase is confirmed with you first.

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.
The S3 API and the mc client both work against SeaweedFS, so most application code and scripts point at the new endpoint with a URL change.

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 SeaweedFS for 7 days

No card. Cancel from the dashboard.