bex-co/bex: The open-source Render alternative — AI-native. Git push → build → deploy on your own infr

3 phút đọc

bex-co/bex: The open-source Render alternative — AI-native. Git push → build → deploy on your own infr – Repository bex-co/bex. Mô tả: The open-source Render alternative — AI-native. Git push → build → deploy on your own infrastructure; agents are first-class users.. 574 stars, 65 forks, ngôn ngữ chính Go, cập nhật 2026-10-19.

1. Repository làm gì?

The open-source, AI-native alternative to Render.

Deploy from Git to HTTPS on infrastructure you own—and give developers and coding agents the same first-class control plane.

Quickstart · Features · Screenshots · Architecture · Render parity · Contributing

bex is in active development and is not ready for production workloads. APIs and configuration can change. The core platform works and is continuously tested; use it today to explore, contribute, and help shape the project.

Render, Heroku, and Railway proved the experience developers want: connect a repo, get a URL, and avoid operating Kubernetes by hand. bex makes that experience open source, self-hostable, and programmable by agents.

Declare a service with the same render.yaml shape many developers and tools already understand:

2. Dữ liệu và cấu trúc đáng chú ý

The Blueprint API compiles that intent into App and Database resources. The operator builds the source, rolls out the workloads, configures routing and TLS, and reports structured status back through every interface. An agent can perform the same deployment with the MCP deploy tool—repo plus manifest in one call.

See the hello-world examples or the full deployment contract.

Some capabilities require optional backing services or explicit configuration and fail closed when unavailable. For the exact REST · GraphQL · MCP · UI status of every capability, use the parity ledger—not this summary—as the source of truth.

This boots the production-shaped local substrate: a kind management cluster, Cluster API, and an app cluster whose machines are Docker containers.

Prerequisites: Docker or OrbStack, Go 1.25+, kubectl, kind, and clusterctl.

An App reports the state an operator or agent needs without scraping logs:

Then add a tenant machine and scale the workload across it:

3. Khả năng ứng dụng và giới hạn

The first bootstrap downloads the Kubernetes and Cluster API dependencies and can take several minutes. For a full platform deployment, start with infra/README.md; for the Go workspace and development commands, see lego/README.md.

All product adapters are thin layers over the same Go core, so authorization, lifecycle behavior, and resource identity do not drift by interface.

Arrows point from a consumer to what it depends on. bex-api owns durable product intent; the database-free operator turns projected Kubernetes objects into workloads; Cluster API provisions the machines beneath them; and operator → types ← backend remains the one-way code dependency described in the architecture panorama.

bex is a working public alpha with a live, production-shaped architecture and broad Render compatibility. It is also a large surface area under rapid development. The project makes that tradeoff explicit:

If you want a PaaS that agents can operate and developers can own, star the repository, try the local cluster, and tell us where the experience breaks. Issues and pull requests are welcome; agent-authored contributions are welcome when the author has reviewed the diff and the tests pass.

Apache-2.0 licensed. See CONTRIBUTING.md and the Code of Conduct.

Số liệu repository có thể thay đổi; nên mở liên kết nguồn để kiểm tra README, giấy phép và trạng thái phát hành.

Nguồn tham khảo: Xem bài gốc