Zeabur Offers Self-Hosted Platform-as-a-Service for Kubernetes Clusters

Zeabur is an open-source, self-hosted Platform-as-a-Service (PaaS) designed to run directly on your own Kubernetes cluster or local machine, according to its public repository documentation. The project aims to translate cluster management into straightforward projects and services while providing plain-word explanations for issues.

According to the documentation, Zeabur operates without maintaining its own separate state, database, or custom resources, and functions using existing Kubernetes objects while adhering to user permission limits.

Deployment Options

• Single Linux Server: An installer is available to set up K3s or RKE2 alongside Zeabur Identity and the platform itself.
• Existing Kubernetes Cluster: Users can install the platform via a Helm chart and sign in using Zeabur Identity.
• Personal Use: Individuals using a `kubeconfig` file can run `zeaburctl ui` to open the interface locally in a browser.

Documentation and Resources

• Official documentation covers installation, deployment, configuration, cluster operation, and uninstallation procedures.
• Documentation is provided in English, Traditional Chinese, and Simplified Chinese.
• The project repository includes developer guidelines, contribution rules, and testing environments configured via a Nix development shell.

Licensing and Verification

The software is licensed under the Apache-2.0 license, with contributions accepted under the Developer Certificate of Origin. Users can review official release lists and repository documentation to verify releases and inspect third-party components, such as embedded catalog bundles and font licenses.

Practical Implications

Adopting a self-hosted PaaS like Zeabur requires administrative access to a Kubernetes environment and familiarity with container orchestration tools. Teams evaluating the platform should review the official GitHub repository, check release notes, and test installations in a non-production environment before deploying to production clusters.