Rakazo vs Solace Agent Mesh
Solace Agent Mesh leads on trust: 80.2/100 (Grade A) against 69.7/100 (Grade B), a 10.5-point gap. Rakazo leads on transparency and maintenance; Solace Agent Mesh leads on supply-chain integrity and provenance, and rests on broader evidence.
Open-source Grok Bot alternative. Choose your own model and sandbox.
Choose Rakazo if transparency and maintenance matter most.
- +4.9Maintenance: last push today, against 10d ago
- +2.1Transparency: OSSF Scorecard 7.5 against 5.1
Platform for building and running AI agents across the full lifecycle — build, test, deploy, monitor, improve. Hosts your agents, runs their tools, and coordinates them over an event mesh, with sessions, artifacts, auth, evaluators, and observability built in.
Choose Solace Agent Mesh if supply-chain integrity and provenance matter most.
- +7.2Identity / Provenance: package provenance attested, against none
- +3.6Safety / Integrity: package provenance attested, against none
- +2.9Adoption
- B vs CEvidence coverage: 3 of 5 independent signal types, against 2
Where they differ
An independent, evidence-based trust comparison of Rakazo and Solace Agent Mesh, two Multi-Agent Systems projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | Rakazoelie222/rakazo | Solace Agent MeshSolaceLabs/solace-agent-mesh |
|---|---|---|
| HVTrust score | 69.7 | 80.2 |
| Evidence grade | B | A |
| Coverage grade | C | B |
| Overall rank | #388 | #192 |
| Rank in Multi-Agent Systems | #5 | #3 |
| GitHub stars | 8.4k | 4.9k |
| Last updated | today | 10d ago |
| Build provenance | No | Yes |
| OSSF Scorecard | 7.5 / 10 | 5.1 / 10 |
| License | Apache-2.0 | NOASSERTION |
| Downloads | — | 376/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 14.4 | 18.0 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 14.9 | 12.8 |
| Maintenance / 20 | 20.0 | 15.1 |
| Adoption / 20 | 9.4 | 12.3 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | — |
| External providers | 2 — OpenRouter, Postgres | — |
| Requires API keys | Yes | No |
| Plugin surface | plugins | — |
| Provenance drift | — | Match |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →