ballerinevsriskkernel
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ballerine | riskkernel | |
|---|---|---|
| Score | 55/100 | 37/100 |
| Rank in category | #2 of 7 in Compliance | #180 of 206 in AI Agents |
| GitHub stars | 2 455 | 20 |
| Stars, last 30 days | +10 | +0 |
| Stable releases, 12 months | 0 | 10 |
| Latest release | — | v0.9.0 · 20 Jun 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
ballerine scores 55/100 against 37/100 for riskkernel, so it is the safer default.
riskkernel ships more often: 10 stable releases in the past year, against 0 for ballerine.
If you want the quickest setup, riskkernel is easier to run; ballerine needs more configuration.
ballerine is growing faster right now (+10 stars in 30 days).
ballerine is archived, so it won't get fixes. Prefer the other one for anything long-lived.
Key differences
- License: ballerine is Other, riskkernel is Apache-2.0.
- Language: ballerine is written mainly in Typescript, riskkernel in Go.
- Features only ballerine lists: AI, API, Authentication, Compliance and 9 more.
- Features only riskkernel lists: Audit CLI, Crash-resumable checkpoints, Framework adapters, Git-native memory and 10 more.
ballerine details →riskkernel details →