Garage UI

Garage UI is an open-source web dashboard for managing Garage S3-compatible object storage clusters, bringing bucket, key, and cluster administration into the browser.

What is Garage UI?

Garage UI is a web-based administrative interface for Garage, a self-hosted S3-compatible object storage platform. It connects to Garage's S3 API and admin API using credentials from a config file, environment variables, or an existing garage.toml, and exposes a browser UI on port 8080. The project includes a Go backend and a Node.js frontend, ships as a single Docker image or a Helm chart, and is MIT-licensed with a public repository maintained by Noooste.

Key Features

• Bucket management — create, configure, and browse buckets, including drag-and-drop file uploads.
• Access key management — create keys and assign per-bucket permissions.
• Cluster overview — monitor node status, layout configuration, and storage usage.
• Flexible authentication — choose no auth, basic credentials, or OIDC providers like Keycloak and Authentik.
• Multi-user access control — optional OIDC-team-based permissions with per-bucket-prefix granularity.
• Easy deployment — configure with one YAML file or GARAGE_UI_ environment variables; supports Docker and Kubernetes.
• Inline object preview — preview images, video, PDF, and text without downloading.
• Zero-config startup — run straight from an existing garage.toml, with token auth auto-enabled when no auth method is configured.

Who is it for?

• Garage cluster administrators who need a GUI to manage buckets, keys, and cluster layout instead of using the command line.
• Self-hosting teams that run Garage for object storage and want multi-user access with OIDC integration.
• Kubernetes operators who deploy Garage via Helm and need a dashboard exposed as a ClusterIP service.

What can you do with Garage UI?

• Cluster admins: configure bucket quotas (size and object count limits), edit bucket policies, and review layout changes.
• Developers: generate scoped access keys for applications and preview or search objects recursively across a bucket.
• Support engineers: inspect storage usage and node status, and enable debug logging to troubleshoot connection issues.

How does Garage UI work?

Garage UI reads configuration from either a config.yaml file or directly from garage.toml, which supplies the S3 endpoint, admin endpoint, admin token, and S3 region. It then starts an HTTP server on port 8080 serving the dashboard and an API at /api/v1/. Configuration precedence is built-in defaults, then garage.toml, then config.yaml, then GARAGE_UI_ environment variables.

Pricing

Garage UI is free and open source under the MIT license.

FAQ

Is Garage UI free?

Yes, Garage UI is released under the MIT license and is free to use and modify.

What Garage versions does it support?

Garage UI aims for broad compatibility, supporting Garage v1 through the latest version, including IPv6-only networks and file-based secrets.

How do I configure authentication?

You can set no authentication, basic admin credentials, or an OIDC provider such as Keycloak or Authentik. When nothing is configured, token auth auto-enables and the login page asks for the Garage admin token.

Can I deploy Garage UI on Kubernetes?

Yes, an official Helm chart is available, and it creates a ClusterIP service on port 80; you can port-forward to it before adding an ingress.

How do I use secrets in Docker?

Sensitive values like the admin token or OIDC client secret can be loaded from files using environment variables with a _FILE suffix, matching the convention used by Postgres and MySQL images.