Self-hosting concern: MinIO dependency after repository archival

[gautamkrishnar]

While reviewing Cap’s self-hosted setup, I noticed MinIO is currently a core dependency for storing recordings/media assets.

This has become a concern because the official MinIO repository was recently archived and moved to read-only status: https://github.com/minio/minio

We should think about migrating to a better alternative. I think https://rustfs.com/ would be a better one.

[linear]

CAP-697

[tembo]

Thanks for flagging this. The MinIO archival is a real concern, and there are already a few related PRs worth being aware of:

• fix: use minio/minio instead of bitnami/minio #1444 switches from the deprecated bitnami/minio to the official minio/minio image
• Update compose template to patch vulnerable minio service and include healthchecks #1510 addresses CVE-2025-62506 by switching to ghcr.io/coollabsio/minio (a community-maintained build from Coolify) and adds healthchecks to all services
• fix(infra): remove anonymous public read access from MinIO bucket #1750 removes the anonymous public bucket access that was being set in the minio-setup container

Regarding RustFS as an alternative: it's promising (Apache 2.0 license, claims 2.3x faster for small objects, designed as a drop-in binary replacement for MinIO), but their docs currently say "do NOT use in production environments" since it's still in alpha. Worth watching but may be premature for the default self-hosted setup.

The good news is that Cap's S3 integration is already provider-agnostic. The packages/env/server.ts config explicitly notes that CAP_AWS_* env vars work with "any S3-compatible service" (see lines 33-35). Users can point to AWS S3, Cloudflare R2, Backblaze B2, Wasabi, or any other S3-compatible provider by setting the endpoint and credentials accordingly. The self-hosting docs at apps/web/content/docs/self-hosting.mdx already mention this flexibility.

For the default docker-compose setup, the immediate fix is probably merging one of the existing MinIO PRs (#1444 or #1510) to move off the deprecated image. Longer term, documenting that users can swap MinIO for any S3-compatible service would reduce the dependency concern without requiring a specific replacement recommendation.