Managed Garage hosting
Pilae installs, patches, backs up and monitors Garage for you, on your own servers or in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
From CHF 449EUR 479USD 559 a month on Starter, hosting and onboarding included.
- Data and streaming
- Open source
- Replaces Amazon S3
- Runs on
- Your own hardware, or a Pilae Cloud region
- Replaces
- Amazon S3, MinIO, Wasabi
- Licence
- AGPL-3.0
Garage among the data and streaming apps
The event streams, pipelines and stores a data team runs, placed next to the systems that produce the data rather than in a vendor region. Garage is the storage.
Garage system requirements
Before anything is deployed, this is what has to exist. We size it with you in the first session, and we say so when your own hardware is already enough.
All 5 requirements, and why each is there
- Nodes3 nodes · 3 zonesThree-way replication keeps one copy in each zone. The smallest zone sets how much the cluster can hold, so zones are sized alike.
- CPU and memory2 vCPU · 4 GB per nodeUpstream asks for 1 GB. The headroom lets the kernel cache the metadata database, which upstream recommends for performance.
- Metadata diskSSD · ZFS or BtrfsHolds the index of every object. Garage does not checksum its metadata, so the filesystem should, and the default LMDB engine needs snapshots in case an unclean shutdown corrupts it.
- Data disksHDD or SSD · XFSGarage checksums and scrubs data blocks itself and uses several disks per node without RAID. Ext4 is avoided because its inode limits bite on large object counts.
- Network between zones≤200 ms · ≥50 MbpsUpstream figures. Nodes talk to each other on port 3901, always encrypted, over the private network. The S3 endpoint has no TLS of its own, so it stays on the private network too, and reaches the gate only if you publish it.
Running Garage in production: what it takes
Place three zones
One node per zone, placed where the data is allowed to live: Pilae regions, your own sites, or both. Zones get similar capacity, because the smallest one sets how much the cluster can hold.
Metadata on SSD, with snapshots
The object index lives on SSD under a checksumming filesystem, and data blocks on large disks under XFS. Metadata is snapshotted every six hours, because an unclean shutdown can corrupt the default LMDB engine, and the snapshots go to the data disks rather than the SSD.
A key per application, private by default
Every app gets its own key on its own buckets. Garage answers only on the private network, and anything you publish, such as a static site or a presigned download link, goes through the gate on port 443.
Back up beyond the replicas
Three copies survive a lost disk or a lost zone, not a delete. Buckets go offsite daily, encrypted, to a location in the country your contract names. On the Enterprise plan, once a month we restore one into a scratch environment and read it back.
Upgrade one major release at a time
Minor releases roll through node by node with no downtime. Major releases go one at a time, never skipped, and the whole cluster switches together after a metadata snapshot. The Pilae Agent rehearses each upgrade on a copy of the cluster and applies it in your window once you approve, recording it in the console.
From our runbook
One Garage node of three, as configured
# /etc/garage.toml on acme-s3-fra1. The nodes in gra1 and ams1 differ only in their addresses.
replication_factor = 3
consistency_mode = "consistent"
metadata_dir = "/var/lib/garage/meta" # NVMe, ZFS
metadata_snapshots_dir = "/srv/garage/hdd1/snapshots" # on the data disks, not the SSD
metadata_auto_snapshot_interval = "6h"
db_engine = "lmdb"
data_dir = [
{ path = "/srv/garage/hdd1", capacity = "8T" },
{ path = "/srv/garage/hdd2", capacity = "8T" },
]
rpc_bind_addr = "[::]:3901"
rpc_public_addr = "10.40.1.11:3901" # private network only
rpc_secret_file = "/run/secrets/garage_rpc_secret"
[s3_api]
api_bind_addr = "[::]:3900" # plain HTTP, private network only
s3_region = "garage"
[admin]
api_bind_addr = "10.40.1.11:3903"
admin_token_file = "/run/secrets/garage_admin_token"
metrics_token_file = "/run/secrets/garage_metrics_token"
metrics_require_token = true
# Layout, staged and applied once, from one node:
# garage layout assign 3f1a -z fra1 -c 16T -t acme-s3-fra1
# garage layout assign 9c07 -z gra1 -c 16T -t acme-s3-gra1
# garage layout assign d24e -z ams1 -c 16T -t acme-s3-ams1
# garage layout apply --version 1
Migrating from Amazon S3 to Garage
Applications keep speaking S3, so for most of them the move is a new endpoint, a region name and a new pair of keys, and the objects copy across with rclone or any S3 client. What does not come across is what Amazon keeps beside the objects. Garage has no versioning, so only the current version of each object moves. It has no object lock, bucket policies, ACLs or storage classes. IAM policies become one key per application with read, write or owner rights on named buckets, and lifecycle rules survive only as expiry and the cleanup of abandoned uploads. The work is in finding which of those features an application quietly relies on, and in the copy itself, which AWS bills as data transfer out unless AWS Support approves a credit for leaving.
- Migration guideHow to migrate from Amazon S3 to GarageFind the S3 features each bucket relies on, size the copy, copy with rclone, repoint each application to Garage, then verify checksums before deleting from S3.
- ServiceSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
Moving from Amazon S3 to Garage, step by step
- List what each bucket relies on: We read the AWS configuration of every bucket for the features Garage lacks. A bucket that needs object lock stays on a store that has it, and we name those buckets before anything moves.
- Create buckets and keys: Each application gets one Garage key, limited to its own buckets. Keys can carry an expiry date, so a contractor's key ends when the contract does.
- Copy, then copy the difference: A bulk copy with rclone runs while the applications still write to S3, and a second pass on the night of the switch takes what changed. Object counts and sizes are compared per bucket before anything is repointed.
- Repoint, then freeze the old bucket: Each application gets the new endpoint, region and keys, with path-style or virtual-host addressing set to what it expects. It is tested against Garage first, so a call Garage does not implement returns 501 there and not in production. Headers Garage ignores on an upload, such as a conditional write, tags or SSE-S3 and SSE-KMS encryption, raise no error, so we search the code for them. The S3 bucket stays read-only until its owner signs off.
What Garage is, and who runs it
S3-compatible object storage that keeps every object in three zones, on your own hardware or in the Pilae regions you choose.
Self-hosted Garage for S3-compatible object storage
Garage is an object store that speaks the Amazon S3 API. It ships as a single binary with no external database or coordination service, and it was designed to keep every object in three zones: separate sites joined over ordinary networks, so that a whole site can go dark while the applications carry on. It is developed by Deuxfleurs, a French non-profit that has run it in production since 2020, with public funding from the EU Next Generation Internet programme.
Most of the apps we operate want a bucket somewhere: Nextcloud for primary storage, Harbor for container images, backup tools for their repositories. Garage is that bucket, spread across three of our 10+ Pilae Cloud regions, across three of your own sites, or across a mix of both. The bucket is often where most of an organisation’s data ends up, which makes it the place where residency is decided.
Read the full briefFold the brief
Garage in production: zones, metadata and backups
Most of the work is in the layout. We place one node per zone and prefer fewer, bigger nodes over many small ones, because Garage spreads data most evenly over those. Metadata sits on SSD and is snapshotted every six hours. Nodes answer only on the private network, whose encrypted tunnels carry the S3 traffic Garage serves without TLS of its own. A bucket reaches the internet only through the gate, and only if you publish it.
A delete reaches all three replicas at once, and Garage has no versioning to undo it, so the replicas are not the backup. Buckets are also backed up daily, encrypted, to an offsite location in the country your contract names, and on the Enterprise plan, once a month we restore one into a scratch environment and read it back. Our monitoring probes every node every 60 seconds, and upgrades go through the Pilae Agent one major release at a time.
Garage licence and S3 compatibility
Garage is AGPL-3.0 and has no paid edition. If you want to fund the project directly, the Garage team at Deuxfleurs takes donations and support contracts. What a small system gives up is S3 API coverage: no versioning, no object lock, no bucket policies or ACLs, and no server-side encryption with managed keys. Customer-provided keys (SSE-C) work, and the disks underneath are encrypted. We check what your applications call before we recommend Garage, and say when another store fits better. See the plans for the price. Talk to us about the buckets you want to move off S3.
What Pilae is responsible for
The same commitments on every app we run, Garage included, and what stays yours. How the platform does it.
Ours
- A pinned version: A version we have run, not whatever latest resolves to that day.
- A runbook: What it depends on, how it fails, what to do about it. In your repository.
- Daily backups: Encrypted and offsite, and on Enterprise restored every month. A backup nobody has restored is a file.
- A patch window: Security updates in a window you agreed, with a rollback ready.
- Someone watching: Every endpoint probed on the minute. An alert reaches a person, not a dashboard nobody opens.
Yours
- The credentials: You hold them. Ours are separate, named, logged and revocable with one command.
- The approval: We ask before anything changes outside an agreed window.
- The exit: The machine, the data, the compose files and the runbook are already yours. Nothing stops when our access does.
Who runs it
Engineers who answer for it
Our engineers review every plan the Pilae Agent prepares and answer for the result.
Your data stays where the contract says
On your own servers or in Pilae Cloud. On Business and Enterprise you choose the region, and your contract names each location.
A Swiss company, a Swiss contract
Pilae is a Swiss company, and your contract with it is governed by Swiss law.
Garage runs on Starter from CHF 449EUR 479USD 559 a month in Pilae Cloud, or on Business with up to three apps on your own servers.
Compare the plansGarage: common questions
Is Garage open source?
Where do the objects actually live?
Can a Garage bucket hold our backups?
How does Garage compare with MinIO or Ceph?
What happens when a node or a whole zone fails?
Ask the engineers who would run your Garage
Thirty minutes on the deployment you already have, or the one you are about to start.
- Go deeperExit plan for critical SaaS and cloud providers, documented and testedA documented, tested fallback for each critical SaaS and cloud dependency, supporting DORA exit strategies and FINMA outsourcing rules.
- CompareSelf-hosting vs managed open source: doing it yourself, or PilaeSelf-hosting gives you the apps and the whole job of running them. Pilae gives you the same open-source apps, operated under a contract, on your premises or in Pilae Cloud.
- CheckBackups and disaster recovery for your self-hosted appsDaily encrypted offsite backups on every plan, longer retention and point-in-time recovery for databases from Business, monthly restore tests and recovery objectives on Enterprise.
