Self-Hosting

Category: Self-Hosting under Infrastructure & Cloud

AGPL-licensed platform for self-hosted cloud development environments: provision Terraform-defined workspaces and govern AI coding agents on infrastructure you control, with no per-seat SaaS fees.

Kubernetes-native backup and disaster recovery: snapshot cluster state and volumes to your own object storage, then restore or migrate. Apache-2.0; ownership is shifting from Broadcom to the CNCF.

CNCF-graduated Kubernetes operator that runs Ceph as self-healing storage: object, block, and file from cluster disks. Fully open; the cost is the Ceph expertise it abstracts but never removes.

CNCF Kubernetes storage running in userspace, with pluggable engines from local volumes to replicated NVMe-oF. Apache-2.0 core, but external KMS and management GUI sit in DataCore's commercial tier.

CNCF-governed, fully open block storage for Kubernetes: HA volumes with encryption, synchronous replication, and S3/NFS backup. No open-core paywall: the only paid tier is optional vendor support.

Apache-2.0 distributed storage with S3 and POSIX, tuned for billions of small files, simpler than Ceph. Day-2 self-healing repair and point-in-time recovery sit behind a paid Enterprise tier.

Unified distributed storage that serves one cluster as S3 object, block, and POSIX file. Foundation-governed, standards-based, with no per-GB cloud fees, but it demands real cluster-ops expertise.

AGPL-3.0 personal cloud OS: a sandboxed K3s app platform for self-hosting files, services, and local AI on hardware you own. Trade-offs are a dedicated-hardware footprint and AGPL network copyleft.

Self-hosted PaaS for deploying applications, databases, and services on your own infrastructure, a sovereign alternative to Heroku and Vercel with no per-deployment fees.