eigr/spawn
This system is a distributed actor framework for building stateful, durable applications on Kubernetes. It provides a complete runtime for managing actor lifecycles, state persistence, and cross-node communication via NATS and gRPC. The platform includes a Kubernetes operator for automated resource management, an Elixir SDK for developer integration, and a CLI tool for local development and deployment.
41.5
Weak · 4 August 2026
28k
lines of production code
Elixir
primary language
1
bus factor · 17 authors in all
3
measurements over time
How it got here
2022 · monorepo and SDK initialization
This period established the foundational architecture of the Spawn project by organizing the codebase into a structured monorepo with distinct applications for the SDK, proxy, and Kubernetes operator. It introduced the core Elixir SDK for actor management, implemented state storage and distributed registry components, and set up the initial test coverage and configuration for the new system.
56 changes
2023–2024 · Platform expansion and infrastructure
The period focused on expanding the platform's infrastructure by introducing Kubernetes resource generation, gRPC sidecar capabilities, and diverse state store adapters for PostgreSQL, MariaDB, and Mnesia. It also established core cluster coordination, security (ACL, TLS), and CLI tooling to support a multi-language SDK and local development environments.
55 changes
2025 · Infrastructure and observability expansion
This period focused on expanding the project's operational and development infrastructure, introducing new tools for containerized execution, local development environments, and process monitoring. It also addressed missing protocol buffer definitions and established a plugin architecture for the Kubernetes operator, alongside comprehensive observability configurations.
6 changes
Survey your own repository
eigr/spawn was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit d2c3a55dae — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.