Is it really compatible with S3?

Garage implements the S3 API, so standard clients and SDKs work against it unchanged — including backup tools such as restic. Coverage is the common S3 surface, not every last AWS-specific extension; check the project documentation if you rely on an unusual call.

Can I use it as a MinIO replacement?

For the common self-hosted case — an S3 endpoint for backups and applications — yes. Garage is lighter and its licence is AGPLv3, with no feature reserved for a paid edition. It is a different project, not a drop-in fork, so validate your specific integrations.

Does a single node give me redundancy?

No. A single-node install stores one copy of your data on one machine, so keep the usual backup discipline. Garage's replication is designed for a multi-node cluster, which the same binary supports when you add machines.

Spin up a data platform quickly.

Garage

S3-compatible object storage in a single Rust binary — for backups, static assets and any application that speaks S3, on your own server.

RAM In validation

In validation

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Garage is an S3-compatible object store built by Deuxfleurs for small, self-hosted, geo-distributed deployments. It is written in Rust, ships as a single distroless container, and is designed to stay lightweight and easy to operate rather than to scale to petabytes.

What you get on a ServOrbit VPS is an S3 endpoint of your own: a bucket, an access key and a secret key, ready for any S3 client or SDK — restic and Borg for backups, an application storing user uploads, a static site behind a CDN, or a database dumping its archives. Because the API is the standard S3 one, existing tooling works unchanged.

Garage has no web console. Administration goes through the `garage` command-line tool and an HTTP admin API, which is a deliberate design choice rather than a missing feature: the daemon stays small and the operational surface stays narrow. If you need a browser interface, community projects provide one on top of the admin API.

The single-node deployment installed here creates its bucket and its S3 credentials at first boot, with no manual cluster layout step. The same binary later grows into a multi-node, geo-distributed cluster if you need replication across machines.

Key features

S3-compatible API — existing clients, SDKs and backup tools work without modification.

Single Rust binary in one distroless container, with no database server to run alongside it.

Bucket and S3 credentials created automatically at first boot, ready to use immediately.

HTTP admin API for scripted administration of buckets, keys and cluster status.

Grows from a single node to a geo-distributed cluster with replication when you need it.

AGPLv3 — free software, with no feature held back behind a commercial edition.

When to use this solution?

1

2

3

4

Deploy Garage on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

02

03

04

Frequently asked questions

No, and that is by design. Administration goes through the garage command-line tool and an HTTP admin API. The daemon stays small and its operational surface narrow. Community projects provide a browser interface on top of the admin API if you want one.

They are generated at installation and surfaced in your ServOrbit client area, under the service's credentials. You can create additional keys and buckets afterwards with the garage CLI.

Complementary solutions

Application Deployment & DevOps

Garage isn't orderable yet.

Automatic installation for this solution is ready and currently going through our tests on a real server. Ordering will open as soon as validation is complete.

Garage

Key features

When to use this solution?

Deploy Garage on your VPS

Frequently asked questions

Complementary solutions

Backrest

ClickHouse

PostgreSQL Stack

Garage isn't orderable yet.

Need help?