Hosting
You can host collections on familiar infrastructure. The protocol does not require a single platform - it requires stable URLs and clear published files.
What every hosting setup must provide
- a stable
collection.jsonURL - stable item and media URLs
- optional domain discovery at
/.well-known/collections.json - durable access for long-term collection reuse
Storage options inside hosting
Git-based hosting
Good for file-first workflows, version history, and review-based publishing.
- Examples: GitHub, GitLab, Forgejo, Gitea
- Best for: small and medium collections with iterative updates
S3-compatible hosting
Good for larger media delivery and scalable static asset hosting.
- Examples: AWS S3, Cloudflare R2, Backblaze B2 (S3), MinIO, Wasabi
- Best for: media-heavy collections and high-volume delivery
Mixed hosting model
- Keep manifests and item metadata in Git-based hosting
- Keep large media files in S3-compatible storage
- Expose both through stable URLs