SOMA-Control
shippedIAM, secrets vault, feature flags, and licensing — your entire control plane in one Rust binary. Replaces Auth0, HashiCorp Vault, and LaunchDarkly.
Learn more →Open-source · Self-hosted · Apache 2.0
Your whole startup's backend, in a few MB of RAM.
Making software production-ready requires a control plane: identity, secrets, feature flags, observability, audit. Each piece ships today as a separate product with its own runtime stack. SOMA builds the features those products actually need, in Rust, adding more only when real usage demands it.
SOMA is in beta. Some components are earlier-stage than others — the roadmap shows where everything stands.
soma up
resolving services...
shippedsoma-control (IAM · Vault · Flags · Licensing)
shippedsoma-observe (metrics · logs · traces · errors)
shippedsoma-analytics (event pipeline)
shippedsoma-audit-server (append-only log)
usablesoma-notify (campaigns · journeys · webhooks)
wipsoma-ai (agents · RAG · memory · evals)
soma up --done
✓ services ready · live footprint of this site below
boot sequence illustrative — live metrics below
live process · this server right now
6MB
RSS
9.8
Req/s
0ms
p50 latency
0.8%
CPU
What plumbing costs today
Figures below are vendor-documented minimums for idle load. Each grows with usage.
| Category | Incumbent (documented minimum) | SOMA |
|---|---|---|
| Identity | Keycloak — 1,250 MB/pod, min. 2 services | soma-iam — measured 5.152 MiB idle (combined in soma-control, linux/arm64, 2026-07-31) · this site: live RSS above |
| Secrets | Infisical — ~16 GB across 3 services (app, Postgres 8 GB, Redis 4 GB) | soma-vault — measured 5.152 MiB idle (combined in soma-control) |
| Feature flags | GrowthBook — 2 GB / 1 vCPU per instance, 3+ instances, MongoDB required | soma-flags — measured 5.152 MiB idle (combined in soma-control) |
| Analytics | PostHog — 4 vCPU / 16 GB RAM, 9+ containers | soma-analytics — design target: a few tens of MB |
| Observability | SigNoz — ~28 cores / ~72 GiB across 5 component types | soma-observe — design target: a few tens of MB |
| Notifications | Novu — 4 vCPU / 8 GB + MongoDB (2 GB, AVX) + Redis (2 GB) | soma-notify — design target: a few tens of MB |
Derived from the documented minimums above: a minimal conventional self-hosted stack ≈ 18–21 containers, ≈ $540–640/month on AWS on-demand, before the first customer.
Vendor minimums are for idle/light load and grow with usage. soma-control figure is measured (linux/arm64, Docker Desktop on Apple Silicon, 2026-07-31, commit de4f858); remaining SOMA figures are design targets pending measurement. Full methodology at soma.dev/en/footprint. Sources: keycloak.org · infisical.com/docs · growthbook.io · posthog.com/docs · signoz.io/docs · docs.novu.co · AWS us-east-1 on-demand 2026-07.
The platform
Four self-hosted suites, each a self-contained binary. Run what your stack needs. A hosted track for focused API services is on the roadmap.
SOMA-Insights
shippedOTLP metrics, logs, traces, event analytics, and an immutable audit log — all on Postgres. No JVM, no proprietary time-series DB.
Learn more →SOMA-Growth
usableNotifications, social intelligence, and web extraction in one binary. SOMA-AI (multi-agent orchestration, RAG, guardrails) is in active development.
Learn more →SOMA-Delights
usableLean business applications built on the SOMA substrate. The reference point is HRMS-class: complete platforms that run on Postgres without an enterprise team. The delivery-operations product in the repo is the first.
Learn more →DevKit & Open Source
shippedsoma-infra, soma-schema, soma-ui, soma-audit, and SDK libraries — the shared foundation consumed by every suite. Apache 2.0.
Learn more →