// the find
labring/sealos
Deploy real projects from GitHub or your AI coding agent, then keep them running with AI-powered operations.
Sealos is a Kubernetes-based multi-tenant PaaS: cloud IDEs (DevBox), managed databases (Postgres/MySQL/Mongo/Redis), an app store for one-click deploys, and account/billing controllers for running it as a hosted service. It's aimed at teams that want to offer or run something like a self-hosted Heroku/Vercel on top of their own k8s clusters, not at developers looking for a library to drop into an existing app.
The controllers (account, app, billing, debt/suspend) implement real multi-tenant SaaS mechanics — workspace quotas, RBAC, and automatic suspension on non-payment — not just a demo CRD. CI runs actual e2e suites against multi-node k3s and k8s clusters (separate workflows for each), which is more cluster-level test coverage than most k8s tooling bothers with. The DevBox flow integrates with real editors (VSCode, Cursor) over a devcontainer-style connection instead of a bespoke web IDE.
Despite the GitHub OSS trappings (badges, contribution guide), it ships under a custom 'Sealos Sustainable Use License' that explicitly forbids using it to provide cloud services to third parties — a dealbreaker if the plan is to build a hosting business on it, and easy to miss until you open LICENSE.md. Adopting it means running their full controller stack and CRDs in your cluster, not integrating a component — this is a platform commitment, not a dependency. The billing/debt/suspension logic is baked into the core controllers, so even a purely internal, non-monetized deployment carries payment plumbing it doesn't need. It's a large multi-module Go + TypeScript monorepo with years of changelog history; customizing behavior beyond what the App Store/Launchpad UI exposes means reading through several go.mod boundaries.