#116116th of 146 in Backends, databases and hosting

ergo

Actor model framework for Go with supervision trees and clustering

Stars
4.7k
License
MIT
Last commit
Nov 2026
Last release
Sep 2026
Language
Go
Stars, last 29 weeks+230
22 Apr 2026: 4,469 stars29 Apr 2026: 4,505 stars6 May 2026: 4,515 stars13 May 2026: 4,525 stars20 May 2026: 4,533 stars27 May 2026: 4,543 stars3 Jun 2026: 4,551 stars10 Jun 2026: 4,560 stars17 Jun 2026: 4,568 stars24 Jun 2026: 4,580 stars1 Jul 2026: 4,585 stars8 Jul 2026: 4,592 stars15 Jul 2026: 4,599 stars22 Jul 2026: 4,603 stars29 Jul 2026: 4,608 stars5 Aug 2026: 4,609 stars12 Aug 2026: 4,612 stars19 Aug 2026: 4,617 stars26 Aug 2026: 4,623 stars2 Sept 2026: 4,628 stars9 Sept 2026: 4,646 stars16 Sept 2026: 4,652 stars23 Sept 2026: 4,662 stars30 Sept 2026: 4,666 stars7 Oct 2026: 4,668 stars14 Oct 2026: 4,676 stars21 Oct 2026: 4,679 stars28 Oct 2026: 4,689 stars4 Nov 2026: 4,696 stars11 Nov 2026: 4,699 stars

4,469 on 22 Apr 20264,699 on 11 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

Ergo is a Go framework modeled on Erlang/OTP. Isolated processes exchange messages, are restarted by supervision trees, and are addressed the same way locally or across nodes. It ships an Observer web UI with an MCP endpoint, Prometheus metrics, tracing, and Erlang distribution protocol support. It is a general distributed-systems library, not an AI-specific project.

Who it is for: Go engineers building distributed or real-time backends with OTP-style actors

Strengths

  • Zero external dependencies; pure Go, requires Go 1.21 or newer
  • Supervision trees with One For One, All For One, Rest For One strategies
  • Same messaging API locally and across nodes; README reports 25M+ msg/sec local on a 32-core Threadripper
  • Observer web UI plus MCP endpoint for inspecting a running cluster from AI clients

Weaknesses

  • Requires learning actor and OTP concepts; not a drop-in replacement for goroutines
  • Go-only; mixed-language clusters work only with Erlang/Elixir via the Erlang protocol
  • Not an AI framework; agent patterns must be built on the actor primitives
  • Throughput numbers come from the project's own benchmark on specific hardware

What it needs

  • no GPU

What changed

  1. “Applications must embed app.Application. ApplicationBehavior gained lifecycle callbacks and Load lost its node gen.Node parameter:”

  2. “mTLS support - new gen.CertAuthManager interface for mutual TLS with CA pool management”

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 146
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.7k stars+697 (+0.7%) in 30 dayscustom license93 out of 100
2appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58.1k stars+546 (+0.9%) in 30 daysBSD-3-Clause93 out of 100
3ormTypeScript ORM for PostgreSQL and MongoDB with a plugin SPI and agent skills47.7k starsApache-2.093 out of 100
#4strapiHeadless CMS that generates REST and GraphQL APIs from content models Live demo ↗ (opens in a new tab)73.5k starscustom license92 out of 100
#5traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.5k starsMIT92 out of 100