SeaweedFS logo

OpenEverest for SeaweedFS

Run SeaweedFS, the open-source distributed object store, on any Kubernetes cluster. Provision the master, volume, filer, and S3 gateway as one instance, choose how S3 is exposed, and encrypt traffic between components - through a single UI and API, powered by the seaweedfs-operator.

SeaweedFS on OpenEverest
Guided Provisioning

Guided Provisioning

Name the instance and go with sensible defaults, or open each section to size the master, volume, filer, and S3 gateway - and review the full summary before you create it.

Instance Overview

Instance Overview

Copy the S3 endpoint into any S3 client, see replicas, CPU, memory, and disk for every component at a glance, and edit the master, volume, filer, or S3 gateway in place.

Key capabilities

One Instance, Full Stack

A single OpenEverest instance becomes a complete SeaweedFS cluster - master, volume servers, filer, and S3 gateway - and its S3 endpoint is published as connection details once it is ready.

A Home for Your Backups

Keep database backups next to your data: point an OpenEverest backup storage at the SeaweedFS S3 endpoint and your PostgreSQL and other instances back up to your own cluster instead of a public cloud bucket.

Scale Each Component

Set replicas, CPU, and memory for the master, volume, filer, and S3 gateway independently, and grow volume and filer disks in place when the StorageClass allows expansion.

Replication & Placement

Choose how many copies of each volume SeaweedFS keeps, validated against the servers you run. Master, volume, and filer pods spread across nodes by default, with node selectors, tolerations, and affinity on top.

Expose S3 Your Way

Keep S3 private on a ClusterIP, or publish it through a NodePort, a LoadBalancer, or an Ingress with your own host and TLS certificate - the external endpoint lands on the instance automatically.

Encrypted Between Components

Turn on mutual TLS for all gRPC traffic between master, volume, filer, and S3, with certificates from cert-manager - the operator's self-signed CA or your own Issuer.

Powered by

seaweedfs/seaweedfs

SeaweedFS is the open-source, Apache-2.0 distributed storage system for blobs, objects, files, and data lakes, built for billions of files.

seaweedfs/seaweedfs-operator

SeaweedFS instances on OpenEverest are powered by the open-source seaweedfs-operator, which manages the master, volume, filer, and S3 workloads on Kubernetes.

Frequently asked questions

Is SeaweedFS free to run on OpenEverest?
Yes. OpenEverest, SeaweedFS, and the seaweedfs-operator are open-source (Apache-2.0) with no licensing fees, and everything runs on your own Kubernetes cluster, in the cloud or on-premises.
Is SeaweedFS a database?
No. SeaweedFS is a distributed file system and object store: masters, volume servers, a filer, and an S3-compatible gateway. It stores blobs, objects, and files, and pairs naturally with the databases OpenEverest already manages.
How does OpenEverest run SeaweedFS under the hood?
The provider-seaweedfs provider translates an OpenEverest Instance into a Seaweed custom resource for the open-source seaweedfs-operator, which runs the master, volume, filer, and S3 components. The provider reports endpoints and health back onto the Instance and never manages pods directly.
What can I use SeaweedFS for?
Any workload that needs S3-compatible storage inside your own infrastructure: a backup target for your databases, dataset and artifact storage for AI pipelines, media files, or serving objects to applications without sending data to a public cloud.
Can I store my OpenEverest database backups in SeaweedFS?
Yes. Create a backup storage of type S3 that points at the instance’s S3 endpoint with path-style addressing, create the bucket, and attach the storage to your PostgreSQL or other instance. Backups then stay in your cluster.
How do applications outside the cluster reach S3?
By default the S3 gateway is only reachable inside the cluster. Switch its service to NodePort or LoadBalancer, or enable an Ingress with your host and TLS certificate; OpenEverest then publishes the external endpoint, over HTTPS when you use Ingress TLS, next to the in-cluster one.
Is traffic encrypted?
Enable inter-component TLS and the master, volume, filer, and S3 gateway talk to each other over gRPC with mutual TLS, using certificates issued by cert-manager. For HTTPS from S3 clients, terminate TLS at an Ingress - the in-cluster S3 service itself serves plain HTTP for now.
Which SeaweedFS versions are supported?
The provider currently ships SeaweedFS 4.47 in a standalone topology that provisions the master, volume, filer, and S3 components. See the provider repository for the current version matrix.

Ready to get started?

Deploy OpenEverest on any Kubernetes cluster and run your first S3-compatible object store in minutes.

View on GitHub Read the Docs

SeaweedFS is a trademark of its respective owners. OpenEverest is not affiliated with, endorsed by, or sponsored by the SeaweedFS project. These names are used for identification purposes only.