OPEN-SOURCE S3/MINIO-COMPATIBLE OBJECT STORAGE

S3-Interface Local-Objects

A MinIO fork maintained by the Pigsty Community With supply-chain continuity and security updates

Documentation Download & Install

SILO // STORAGE NODE PGSTY-01

S3 API:9000APPLICATION TRAFFIC

OBJECT STORAGE CORE SILO MINIO-COMPATIBLE

CONSOLE:9001OPERATOR ACCESS

ERASURE SET // DISTRIBUTED DISKS

D01ONLINED02ONLINED03ONLINED04ONLINE

COMMUNITY FORKMAINTAINED BY PIGSTY

KEY METRICS

Maintained in public, visible at a glance

479,169 Docker Pulls 1,925 GitHub Stars 19 Security Fixes 7 Releases

DokployPRODUCT TEMPLATE

Grafana LokiHELM · BUNDLED SERVICE

PigstyPG BACKUP REPO

RAGFlowDEFAULT COMPOSE

ModelarDBCI · INTEGRATION

AgentsMeshCOMPOSE · CI

MeasureBACKEND DEPLOYMENT

FiremootREFERENCE COMPOSE · CI

VALUE PROPOSITION

Keep what works. Maintain what matters

A focused downstream for operators who need continuity—not a new storage experiment.

01 · CONSERVATIVE MAINTENANCE

Conservative by Design

Narrow changes. Durable operations

Focused build, dependency, and runtime maintenance
Applicable security fixes for the active release line
Targeted repairs for reproducible defects

Minimize downstream delta. Maximize continuity

02 · COMPATIBLE INTERFACE

Familiar Operational Surface

Evaluate an upgrade—not a migration

Preserves the minio executable and S3 APIs
Keeps environment variables, CLI conventions, and release tags
Fits common deployment workflows and existing automation

Interface first. Migration cost contained

compatibility.contract

# Expected continuity
executable: minio
object_api: S3 compatible
environment: MINIO_*
release_tag: RELEASE.*
client: mc / mcli
policy: test before rollout

03 · COMPLETE DELIVERY

Release Artifacts Included

From source to runnable artifacts

Versioned binaries, checksums, and release notes
RPM, DEB, APK, and multi-architecture container images
A maintained Console and compatible client

Maintain the delivery surface—not just the source

SILO // RELEASE SURFACEVERSIONED · CHECKSUMMED OCIamd64 · arm64 RPMEL compatible DEBDebian · Ubuntu APKAlpine Linux BINserver · client SUMSHA256 checksums ACTIVE RELEASE LINE →

04 · VISIBLE SECURITY

Visible Security Record

Policy, advisories, and code in one place

Public security policy and private reporting path
Fork security notes target the active release line
Review, pin, test, and retain a rollback path before rollout

Make maintenance—and its limits—auditable

SECURITY.md

# Active release line
report: privately
triage: reproducible issues
advisories: published with code
compatibility: goal, not guarantee

# Pin · Review · Test · Roll back

S3 INTERFACE

The interface your stack already speaks

SILO follows MinIO's established application and operational surface, so evaluation centers on compatibility testing—not redesigning storage access.

S3 Clients → Environment Variables → Command-Line Client →

S3S3 APIApplication interface $minioServer executable ENVMINIO_*Configuration surface RELRELEASE.*Version tags MCmc / mcliOperator workflow IAMIAM + TLSSecurity controls

OBJECT STORAGE CAPABILITIES

Browse the Documentation →

OPERATIONS

Familiar Console, monitoring, and replication workflows

Open Console Docs ↗

OPERATOR VOICES

Real migration reports, with the caveat intact

Public third-party reports from April–May 2026. They describe individual environments, not universal compatibility or production guarantees.

IN-PLACE MIGRATION

“I’m happy to report it was seamless!”

Stopped the container, changed the Quadlet image, and restarted—with the admin Web UI restored.

PRODUCTION USE

“I have this running on a nixos server in my production environment”

An x86_64-linux build was running on a real server; Nixpkgs inclusion remained a community proposal.

REPRODUCED GUIDE

“本記事の手順そのままで動作することが確認できています。”

The LiteLLM hands-on kept working as written after switching to pgsty/minio and pgsty/mc.

MAINTENANCE CAVEAT

“it might lack long-term maintenance in the future, so just keep an eye on it.”

Useful now is not a lifetime promise: pin releases, follow advisories, and keep validating your own workload.

MAINTENANCE

A deliberately narrow promise

SILO exists for continuity across existing MinIO-compatible deployments—not an unlimited product roadmap.

MAINTAINED SURFACE

What stays maintained

Builds and dependencies for the active release line
Applicable security fixes and advisories
Focused fixes for reproducible defects
Versioned artifacts and documentation

EXPLICIT BOUNDARY

What is not promised

A full continuation of the upstream roadmap
Historical releases or multiple support branches
Untested, item-by-item compatibility guarantees
Response, remediation, or release-time SLAs

DOWNLOAD

Get SILO

Choose the server or admin client first, then use the install path that matches your operating system, architecture, and deployment model.

DATA SERVICE

SILO Server

Server binaries, container images, Linux packages, source, and Pigsty Ansible automation.

LinuxDockerKubernetesAnsiblemacOSWindows

Choose install method

ADMIN CLI

mcli Client

A compatible command-line client for buckets, objects, identity, cluster administration, and daily operations.

LinuxmacOSWindowsDockerSource

Choose install method