Layer 3 · self-hosting reality check
What it actually takes to self-host MinIO
The docs say 2 GB. In practice you want 4 GB. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Amazon S3 alternatives, where MinIO is one of the picks.
Wondering whether you need to at all? Is Amazon S3 free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 2 GB |
|---|---|
| RAM — what it really needs | 4 GB |
| CPU | 2 vCPU |
| Disk | Whatever you are storing. With erasure coding, usable capacity is meaningfully less than raw. |
| Monthly cost | $15–40/mo for a few TB on block storage, against S3 pricing that is cheaper per GB but charges for every request and every byte out |
| Setup time | 1 hour single-node, a day for a distributed set |
| How you install it | single binary or container; distributed mode wants at least four nodes to be meaningful |
| Ongoing maintenance | Moderate. Drive failures are your problem now, and so is capacity planning. |
| Where it stops scaling | Petabytes in distributed mode. The operational burden scales with it. |
The thing that catches people out
Single-node MinIO gives you the S3 API, not S3 durability. One disk, one machine, one failure domain — if the box dies, the data dies. People adopt it for the API compatibility and quietly inherit a single point of failure holding their backups. Either run it distributed or treat it as a cache with the real copy elsewhere.
When not to self-host MinIO
Egress is your main S3 cost and your traffic is spiky. Object storage is one of the few areas where cloud pricing is genuinely hard to beat once you count durability.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 3 self-hosting guides
Common questions
- How much RAM does MinIO actually need?
- 4 GB in practice. The documented minimum is 2 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU alongside it.
- What does self-hosting MinIO cost per month?
- $15–40/mo for a few TB on block storage, against S3 pricing that is cheaper per GB but charges for every request and every byte out This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for moderate. Drive failures are your problem now, and so is capacity planning.
- How long does it take to set up MinIO?
- 1 hour single-node, a day for a distributed set, via single binary or container; distributed mode wants at least four nodes to be meaningful.
- When should I NOT self-host MinIO?
- Egress is your main S3 cost and your traffic is spiky. Object storage is one of the few areas where cloud pricing is genuinely hard to beat once you count durability.
- What is the most common mistake when self-hosting MinIO?
- Single-node MinIO gives you the S3 API, not S3 durability. One disk, one machine, one failure domain — if the box dies, the data dies. People adopt it for the API compatibility and quietly inherit a single point of failure holding their backups. Either run it distributed or treat it as a cache with the real copy elsewhere.