SILO: S3-Compatible Object Storage by Pigsty

SILO // STORAGE NODE PGSTY-01S3 API:9000APPLICATION TRAFFICOBJECT STORAGE CORE SILO S3-COMPATIBLECONSOLE:9001OPERATOR ACCESSERASURE SET // DISTRIBUTED DISKSD01ONLINED02ONLINED03ONLINED04ONLINECOMMUNITY FORKMAINTAINED BY PIGSTYKEY METRICSMaintained in public, visible at a glanceVALUE PROPOSITIONWhat upstream dropped, SILO picks upMinIO's community edition gutted its console, stopped shipping binaries, and archived its security updates. SILO restores all three—on the same code, at the same performance.WEB CONSOLEThe full console, restored Manage buckets, identity, monitoring, and replication in the browserUpstream stripped the AGPL web console down to a stubSILO ships the full management UI: buckets, IAM, monitoring, site replicationNo paywall, no feature gate—the console every operator remembersThe console upstream took away, back in your browserRELEASE ARTIFACTSBinaries, prebuilt and signed From source to signed, runnable packagesNo self-build requirement, no detour through a closed commercial downloadVersioned binaries, RPM / DEB / APK, and multi-arch container imagesGPG-signed packages with published checksumsThe delivery surface, maintainedCOMPATIBILITYA drop-in replacement Swap the image name; your data stays in placeThe delivery surface is renamed silo; the protocol and data are notS3 API, MINIO_* variables, metrics, routes, and disk format unchangedSee the compatibility audit and migration guide, rollback includedPoint the image at pgsty/silo—everything else staysS3 INTERFACEThe interface your stack already speaksSilo renames the product and its delivery surfaces—never the protocol. The S3 API, MINIO_* configuration, and on-disk format stay as your stack expects, with every difference recorded in the compatibility audit.OBJECT STORAGE CAPABILITIESUSER VOICESReal migration reports, with the caveat intactPublic third-party records from February–July 2026.

Every promise and every refusal is written down in the Silo Manifesto.MAINTAINED SURFACEWhat stays maintainedBuilds and dependencies for the active release lineApplicable security fixes and advisoriesFocused fixes for reproducible defectsVersioned artifacts and documentationA release typically every 1–2 months, at most a quarterEXPLICIT BOUNDARYWhat is not promisedA full continuation of the upstream roadmapHistorical releases or multiple support branchesUntested, item-by-item compatibility guaranteesResponse or remediation-time SLAsFAQCommon questions, answered straightShort answers, with links to the long ones.Q1Why does this project exist?Because upstream wound down its community edition: the web console was stripped, prebuilt binaries stopped, and the repository was archived. Silo exists so that a maintained, feature-complete, S3-compatible community object storage keeps existing—Pigsty runs it in production as its PostgreSQL backup storage. The full reasoning lives in the Silo Manifesto.Q2What problem does it solve?It keeps existing MinIO-compatible deployments viable: versioned binaries and packages you can download, security fixes with public advisories, and the full web console—no self-building, no commercial license. It is maintenance and continuity, not a new product roadmap.Q3What do you promise?A deliberately narrow list: AGPLv3 forever with no CLA (DCO only); no paywalls, registration walls, or telemetry; a release typically every 1–2 months, at most a quarter; and a public advisory for every security fix. What we refuse to promise—fix-time SLAs, an upstream roadmap continuation—is written down with the same care in the Manifesto.Q4Who maintains this fork?A straight answer, with names: the fork is maintained under the PGSTY organization by Ruohang Feng (Vonng)—author of the Pigsty PostgreSQL distribution. He has deployed and managed a 25 PB MinIO cluster and brings deep packaging experience. The continuity arrangements are written down in advance in Article 9 of the Manifesto.Q5What role do coding agents play?Agents are the main workforce for feature development and code review. The commitment that comes with that: every change must pass CI and human review, and every constructive change is merged only after a human has weighed its trade-offs. The agents' full reasoning records are archived, and their trade-off analyses are preserved as design documents for future reference; the security chronicle and release notes show this way of working and its output in public.Q6Will the on-disk format change?No. The .minio.sys metadata directory and object layout stay as upstream left them, frozen by a CI compatibility guard, and remain interoperable with MinIO in both directions. New capabilities do not touch the disk format by default; any exception would be opt-in and flagged before you enable it. See the compatibility audit.Q7How compatible is it?It is a drop-in replacement: the S3 API, MINIO_* environment variables, minio_* metrics, x-minio-* headers, and /minio/* routes are unchanged—in a container deployment, migration is one image-name change, with a rehearsed rollback path. Every difference is recorded in the compatibility notes; the migration guide covers Docker and packages.Q8Can I run it in production?Yes—this is the very build we run in production ourselves: Pigsty's production PostgreSQL backups sit on Silo, so the artifacts you download are the ones we operate. This page also lists third-party adoption reports with public sources; as always, pin a release, validate against your own workload first, and keep the rehearsed rollback path from the migration guide.Q9What does the AGPL mean for my app?The short version: we pledge never to pursue AGPL claims against you, and never to use the license to make your life difficult. Silo is AGPLv3 like the upstream it forked, and will never change license; our stated position (a position, not legal advice) is that using Silo through its S3 API does not make your application a derivative work. With no CLA and DCO-only contributions, even relicensing is structurally impossible—see Article 3 of the Manifesto.Q10What if maintenance stops one day?We will make our best effort to keep every released artifact and document available. The build is documented and provenance-attested, so anyone can rebuild equivalent artifacts from source without us; and if active maintenance ever stops for six months, we will say so publicly and archive the project tidily—the full exit arrangements are in Article 9 of the Manifesto.DOWNLOADGet SILOChoose the server or admin client first, then use the install path that matches your operating system, architecture, and deployment model.