Garage UI is the web dashboard that Garage object storage never shipped, turning an admin API that speaks JSON over HTTP into screens your whole team can use. Create and configure buckets, browse objects with drag-and-drop uploads, and preview images, video, PDFs, and text inline instead of downloading files just to check what they are. A recursive search finds objects across a whole bucket, and bucket settings carry size and object-count quotas so one tenant cannot quietly eat the cluster. Access keys are created in the UI and assigned per-bucket permissions, replacing error-prone command-line key surgery. The cluster overview watches node status, layout configuration, and storage usage, so a degrading node shows up in the dashboard before it shows up as an outage. Sign-in flexes to your setup: no auth on a trusted network, basic admin credentials, the Garage admin token, or OIDC single sign-on through providers like Keycloak and Authentik. With OIDC teams enabled, access control maps token claims to bucket prefixes with named permission presets, and unmatched users are denied by default rather than promoted. Zero-config startup reads your existing garage.toml, so the first login takes minutes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Picture your object storage scattered across a home server, a friend's rack, and a cheap VPS in another country, still answering S3 requests like nothing happened: that is exactly the deployment Garage was built for. Every object is replicated to three zones, so losing a node, a disk, or an entire site degrades the cluster instead of destroying your data. Applications talk to it with the standard S3 API: create buckets, upload objects in multiple parts, list and copy them, and hand out access keys that are scoped per bucket. A separate web endpoint serves static websites straight from buckets with CORS support, which covers personal sites, documentation, and release downloads without another server in the chain. The whole system ships as one dependency-free binary that asks for about a gigabyte of RAM and any x86-64 or ARM CPU from the last decade, second-hand hardware very much included. There is deliberately no consensus protocol to babysit: nodes gossip their cluster layout, tolerate 200-millisecond links, and keep serving reads while parts of the fleet are unreachable. Deuxfleurs runs it in production for their own hosting, and common pairings include restic or rclone backup targets, Matrix media storage, and Nix binary caches. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.