#185185th of 275 in Backends, databases and hosting

bex

Open-source Render-style PaaS that deploys from Git, operable by agents via MCP

Releases and problems feed (RSS)

Stars
813
License
Apache-2.0
Last commit
Nov 2026
Last release
Nov 2026
Language
Go
Stars, last 29 weeks+222
29 Apr 2026: 591 stars6 May 2026: 591 stars13 May 2026: 592 stars20 May 2026: 593 stars27 May 2026: 593 stars3 Jun 2026: 593 stars10 Jun 2026: 593 stars17 Jun 2026: 593 stars24 Jun 2026: 593 stars1 Jul 2026: 593 stars8 Jul 2026: 593 stars15 Jul 2026: 596 stars22 Jul 2026: 597 stars29 Jul 2026: 598 stars5 Aug 2026: 600 stars12 Aug 2026: 601 stars19 Aug 2026: 601 stars26 Aug 2026: 604 stars2 Sept 2026: 605 stars9 Sept 2026: 740 stars16 Sept 2026: 745 stars23 Sept 2026: 751 stars30 Sept 2026: 752 stars7 Oct 2026: 755 stars14 Oct 2026: 758 stars21 Oct 2026: 761 stars28 Oct 2026: 763 stars4 Nov 2026: 764 stars11 Nov 2026: 765 stars18 Nov 2026: 813 stars

591 on 29 Apr 2026813 on 18 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

bex is a self-hostable platform-as-a-service written in Go that deploys Dockerfile or native-build projects (Go, Node.js, Python, Ruby, Rust, Elixir) from Git to HTTPS. It reads Render-style render.yaml Blueprints and exposes REST, GraphQL, MCP, a Render-compatible CLI and Kubernetes CRDs over one core. A Kubernetes operator runs workloads on Cluster API machines: Docker containers locally, Hetzner in production-shaped clusters. The README calls it an alpha, not ready for production.

Who it is for: Self-hosters wanting an open-source Render alternative that agents can drive

Its own README calls it an alternative to Heroku.

Ranked among open-source alternatives to Heroku (#4 of 4).

Strengths

  • Reads render.yaml Blueprints and reuses the upstream Render CLI commands
  • Dashboard, REST, GraphQL, MCP, CLI and CRDs all sit on one Go core
  • Covers managed Postgres with PITR, Valkey-compatible Key Value, cron jobs, workers and static sites
  • Render parity gaps are tracked in a documented evidence ledger

Weaknesses

  • README warns it is not ready for production; APIs and config can change
  • Local quickstart needs kind, Cluster API, clusterctl and Go 1.25+; no Docker or compose install
  • Some capabilities need optional backing services and fail closed without them
  • Production-shaped clusters are described only for Hetzner machines via Cluster API

What it needs

  • no GPU
  • Docker
  • Needs Docker or OrbStack, Go 1.25+, kubectl, kind, clusterctl, Cluster API, PostgreSQL, Zot registry
  • README: alternative to Heroku

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Also in Backends, databases and hosting

See all 275
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.8k stars+659 (+0.7%) in 30 dayscustom license94 out of 100
2coolifySelf-hosted Heroku and Vercel alternative that deploys apps and databases over SSH66.3k stars+3,121 (+4.9%) in 30 daysApache-2.093 out of 100
3traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.6k stars+406 (+0.6%) in 30 daysMIT93 out of 100
#4appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58.4k stars+641 (+1.1%) in 30 daysBSD-3-Clause93 out of 100
#5medusaNode.js commerce platform with modular products, carts, orders and payments37.3k stars+563 (+1.5%) in 30 dayscustom license93 out of 100