Object Storage for Relution
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. After the switch, Relution automatically transfers the existing resources from the database to the bucket. The switch cannot be reversed.
Even with object storage, some content remains in the database: certificates and private keys (encrypted) as well as files up to 512 KB. The database and the bucket are therefore backed up together. Details: Connect object storage →
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 avoid cloud costs and provide full control over the data.
| Provider | Description |
|---|---|
| SeaweedFS → | Recommended. Easy to deploy, tested with Relution. SeaweedFS Setup → |
| Garage → | Lightweight, designed for self-hosting. |
| Ceph → | Enterprise-grade, highly scalable. |
| RustFS → | Rust-based alternative. |
| MinIO → | Not Recommended. Has ceased development. Migration from MinIO to SeaweedFS → |
SeaweedFS has been thoroughly tested with Relution. Other backends can work but have not been tested.
Cloud Providers
| Provider | Notes |
|---|---|
| AWS S3 → | The original S3 implementation, tested with Relution. |
| Hetzner Object Storage → | German provider, cost-effective, tested with Relution. |
Managed Relution hosting with object storage included is available via our Sales Team → – more info: Relution Cloud →
Next Steps
The next steps depend on the situation:
| Situation | Next Steps |
|---|---|
| New setup with SeaweedFS (recommended) | 1. SeaweedFS Setup → 2. Connect object storage → |
| New setup with a cloud provider | 1. Set up at cloud provider 2. Connect object storage → |
| Encrypting object storage (optional) | Server-Side Encryption (SSE-C) →, before the first start with object storage |
| Migrating from MinIO or another backend | – Migration Guide → |