# ergo-services/ergo

An actor-based Framework with network transparency for creating event-driven architecture in Golang. Inspired by Erlang. Zero dependencies.

Repository: https://github.com/ergo-services/ergo
Canonical: https://ross.abutalabs.com/products/ergo
Homepage: https://ergo.services
Language: Go
License: MIT
License Family: permissive
Topics: erlang, golang, elixir, supervisor, otp, otp-applications, distributed-systems, framework, microservice, microservices-architecture, go, distributed, actor-model, actors, event-driven, event-driven-microservices, network-transparency, ergo-framework, workflow, workflow-engine
Last push: 2026-08-26T19:37:58+00:00

## Health v2 (maintenance only)
Score: 78/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 37, longevity 100
- inputs: {"age_days": 3268, "days_push": 7, "days_rel": 210, "gap_med": 258.5, "n_releases_24m": 3}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4633, forks 188 (observed 2026-08-28T04:08:55.382230+00:00)

## What it is
Ergo Framework is a Go framework implementing the actor model with network transparency, inspired by Erlang/OTP design patterns. It provides supervision trees, distributed messaging, service discovery, and ready-to-use components for building fault-tolerant, event-driven distributed systems with zero external dependencies.

## Use cases
- build distributed event-driven microservices in Go
- implement actor-based concurrent systems with message passing
- create self-healing systems with supervision trees and restart strategies
- build clustered applications with network-transparent actor communication
- replace goroutine/mutex complexity with isolated message-passing processes
- set up service discovery and pub/sub events across nodes

## When to choose
- you want Erlang/OTP-style reliability patterns in pure Go
- you need distributed actors that communicate identically locally and remotely
- you want zero-dependency framework with supervision and fault recovery
- you're building event-driven microservices or clustered systems

## When to avoid
- you need a simple HTTP/REST API framework rather than actor messaging
- your team is unfamiliar with actor model concepts and Erlang patterns
- you require a mature ecosystem with extensive third-party integrations
- project is small enough that goroutines and channels suffice

## Facets
- artifact type: framework
- maturity: active
- function: concurrency, rpc, message-queue, microservices, serialization, networking
- domain: microservices, backend, developer-tools
- platform: go, windows, cross-platform
- tags: actor-model, erlang-inspired, supervision-trees, network-transparency, event-driven, otp, zero-dependencies, fault-tolerance, linux, macos

## Member repositories
- ergo-services/ergo (main) score 78

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:55.382230+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:19:35.481626+00:00, confidence not recorded.
  - readme: https://github.com/ergo-services/ergo (fetched 2026-08-28T04:08:55.382230+00:00, sha 9a417cda1612)
  - homepage: https://ergo.services (fetched 2026-08-29T09:04:18.360161+00:00, sha 5372b79a1ea8)
  - site_page: https://docs.ergo.services (fetched 2026-08-29T09:04:18.369857+00:00, sha 9f30053590eb)
- Data as of 2026-08-30T08:39:29.467469+00:00.