Score7.8
Popularity1.0
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity5.7
Open-source/build8.4
Evidence7.2
Workflow potential9.3
Setup ease6.4
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for engineering teams, AI agent developers, Slack-native tool builders, Kubernetes users, self-hosted platform operators, AI-curious readers tracking the multi-agent space, engineering teams wiring shared agents to their workflows, and any team wiring a Slack-native + isolated-sandbox + BYO-harness + shared-tools + durable-workflows + credential-boundaries agent platform to their team workf
Who should use it
Engineering teams, AI agent developers, Slack-native tool builders, Kubernetes users, self-hosted platform operators, AI-curious readers tracking the multi-agent space, engineering teams wiring shared agents to their workflows, and any team wiring a Slack-native + isolated-sandbox + BYO-harness + shared-tools + durable-workflows + credential-boundaries agent platform to their team workflow -- and who can pair paradigmxyz/centaur with the Slack bot for the Slack-native surface, the isolated Kubernetes sandbox for the execution-environment surface, the k3s local cluster for the local-setup surface, the BYO harness (Amp, Claude Code, Codex) for the agent-harness surface, the shared tools Python plugins for the shared-tools surface, the durable workflows engine for the durable-workflows surface, the credential boundaries for the security surface, the replayable state for the state-recovery surface, the organization overlays for the customization surface, and a target team workflow (Slack channel, agent harness, shared tools) for the eval surfaceEngineering teams + AI agent developers that want the Slack-native surface (mention the bot in Slack, get progress and final answers in the thread) -- the right Slack-native primitive for any engineering team that has been using a non-Slack-native agent platformEngineering teams + Kubernetes users that want the isolated Kubernetes sandbox (each conversation runs in an isolated sandbox with shell, workspace, git, Python, Node.js, Bun) -- the right sandbox primitive for any engineering team that has been using a non-isolated agent platformEngineering teams + multi-agent users that want the BYO harness (Amp, Claude Code, Codex, or deployment-specific harnesses) -- the right harness-portability primitive for any engineering team that has been locked to a single agent harnessEngineering teams + durable-orchestration users that want the durable workflows (jobs that can sleep, resume, wait for events, start child agents, survive service restarts) -- the right durable-orchestration primitive for any engineering team that has been writing a custom durable flow engineEngineering teams + security-conscious users that want the credential boundaries (agents use approved services without raw API keys) -- the right security primitive for any engineering team that has been worried about agents holding raw API keysEngineering teams + engineering teams that want the replayable state (messages, executions, events, delivery state stored so clients can reconnect without losing the result) + the organization overlays (layer in own tools, workflows, personas, skills, prompts without forking the base) + the k3s local cluster + the dual Apache-2.0 OR MIT license -- the right state-recovery + customization + local-setup + transparency primitive for any engineering team that has been using a non-replayable non-overlay non-local-setup agent platform
Who should skip it
Consider paradigmxyz/centaur lower priority if you already have a working solution in this category.
About this signal
paradigmxyz/centaur is tracked by RepoRadar as a dual apache-2.0 or mit (raw main in the Centaur: Multiplayer Self-Hosted Agents for Team section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. paradigmxyz/centaur leads on workflow potential (9.3) and open-source/build quality (8.4); its lowest signal is maturity (5.7), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned paradigmxyz/centaur a composite score of 7.8 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
The 828* repo is at active maintenance (pushed 2026-07-08) but the project is in the early-adopter phase (828 stars) -- the consumer SHOULD benchmark the platform on the consumer's specific team workflow before adopting; the consumer SHOULD pin the Centaur version and review the changelog; the consumer SHOULD verify the BYO harness surface against the consumer's specific agent harness (the README documents Amp; Claude Code.
Evidence links
Closest alternatives / related signals
open-sourceapache-2-0mitdual-licensespdx-license-identifier-apache-2-0-or-mitcentaurparadigmxyzmultiplayer-agents
