Overview

Introduction

By default, Relution stores certain resources - such as native app binaries - in its database. This can cause the resource table to grow very large, especially when managing many native apps.

To optimize performance, Relution supports storing these resources in external S3-compatible object storage buckets.

⚠️ MinIO Users: MinIO ceased development in October 2025 and will not receive updates. We recommend migrating to SeaweedFS using our guide: Object Storage Migration →

When to Use Object Storage

While optional, external object storage is recommended in these cases:

  • Installation and management of native apps on Windows devices
  • Managing a larger number of native apps, or native apps larger than 50 MB
  • Servers with more than 5,000 devices

Available Options

The most widely known object storage is AWS S3, but many S3-compatible solutions exist - both cloud-hosted and self-hosted.

Self-Hosted / On-Premise

Self-hosted solutions let you avoid cloud costs and keep full control over your data.

ProviderDescription
SeaweedFSRecommended. Easy to deploy, tested with Relution.
Our setup guide →
GarageLightweight, designed for self-hosting.
CephEnterprise-grade, highly scalable.
RustFSRust-based alternative.
MinIONot Recommended. Has ceased development.
Our migration guide →

We have thoroughly tested SeaweedFS with Relution. Other backends can work but have not been tested.

Cloud Providers

ProviderNotes
AWS S3The original S3 implementation, tested with Relution.
Hetzner Object StorageGerman provider, cost-effective, tested with Relution.

For managed Relution hosting with object storage included, please contact our Sales Team – more info: Relution Cloud →

Next Steps

Choose your path based on your setup:

Your SituationNext Steps
New setup with SeaweedFS (recommended)1. Set up SeaweedFS →
2. Configure Relution →
New setup with a cloud provider1. Set up at cloud provider
2. Configure Relution →
Migrating from MinIO or another backendMigration Guide →