Zeabur

Deploy and run your services on your own Kubernetes, simply and securely.

Zeabur is an open-source platform you host yourself. It runs in your cluster (or on your machine), shows the cluster as projects and services, explains what is wrong in plain words, and lets you change things safely. It works with the objects you already have, never acts with more rights than you have, and keeps no state of its own: no database, no custom resources.

oss.zeabur.com/zeabur shows what Zeabur does, and the documentation covers installing, deploying, configuring and operating the cluster, and leaving Zeabur, in English, 繁體中文 and 简体中文.

Status: pre-alpha (0.1.1). The API may still change, and it has been tried on few clusters. Do not point it at a cluster you cannot afford to break.

What needs you, across every project, grouped by where each problem comes from.	One page per project: a map or a list, with what needs attention and what happened.
Diagnoses in plain words, with what to do and the evidence.	Rollouts, usage and domains: progress, CPU and memory against the limits, and whether each domain answers.
Databases with their connection details and a warning when nothing would take over.	The cluster: Kubernetes support dates, node pressure, backups, notifications and components.

_{Screenshots of the built-in demo data (cargo run -p zeabur-api --example demo), taken by scripts/docs-shots.sh docs/readme-shots.yaml.}

Get started

• One Linux server: the installer sets up K3s (or RKE2), Zeabur Identity and Zeabur. Install on a single server
• An existing Kubernetes cluster: install the Helm chart, with sign-in through Zeabur Identity. Install in an existing cluster
• Just you, with your kubeconfig: zeaburctl ui opens Zeabur in your browser on your own computer. Personal use and zeaburctl

Releases lists what a release contains and how to verify it.

Build from source

In the Nix dev shell, which provides every tool:

git clone https://github.com/zeabur-oss/zeabur && cd zeabur
nix develop
./scripts/build-ui.sh
ZEABUR_UI_DIST="$PWD/web/dist" cargo build --release --locked -p zeaburctl
./target/release/zeaburctl ui                  # --context <name> for another context

zeaburctl ui listens on a random loopback port, opens the browser, and makes every request with your current kubeconfig context.

Contributing

• Contributing: environment, checks, dependency policy, tests.
• Developer docs: crates, testing, wording, releasing.
• docs/ holds the sources of the documentation; edit a page there and it is published to oss.zeabur.com.

Licence and credits

Apache-2.0. Contributions are accepted under the Developer Certificate of Origin.

Third-party content in this repository:

• Zeabur Catalog, embedded from its release bundle at the commit in flake.lock (Apache-2.0).
• Kubernetes' release schedule in crates/zeabur-catalog/src/versions.rs, from kubernetes/website data/releases (CC BY 4.0, The Kubernetes Authors).
• Rendered manifests of upstream Helm charts in fixtures/charts, test input only, each under its chart's licence (Apache-2.0 or MIT; listed in fixtures/charts/README.md).

The web interface is built with @zeabur/design-system (Apache-2.0), which contains shadcn/ui's components, theme and base styles (MIT), the Inter and JetBrains Mono fonts (SIL Open Font License 1.1) and the Zeabur logo; its README lists their notices. The built interface, embedded in the binary and the image, includes those fonts and the logo.

The container image includes Mozilla's CA certificate bundle as packaged by nixpkgs (MPL-2.0).