What Paperclip Is
Paperclip is an open-source “human control plane for AI labor.” Its core metaphor is the org chart: you create an agent organization with roles, reporting structures, and goals — and the agents work within that structure. The board (you) can hire agents, approve strategic directions, override decisions, and terminate agents. Each agent has a budget that auto-pauses when hit.
Paperclip is MIT-licensed, self-hosted, and runtime-agnostic — it works with Claude Code, Cursor, or any agent runtime. It’s an impressive project with genuine thinking about the human oversight problem.
What Sentrely Is
Sentrely is a managed control plane for Claude Code agents, focused on policy enforcement, audit trails, and production-grade governance. It models agent permissions as YAML policies: claude-deploy-01 can push to feature/* but not main, can read from specific S3 prefixes, requires human approval for production deployments. Human oversight happens through real-time Slack and Telegram approval gates. Every action produces an immutable audit log designed for compliance auditors.
Sentrely is a fully managed service — no infrastructure to operate.
Same Problem, Different Approach
Both products address the same core problem: autonomous AI agents need human oversight and bounded permissions. The approaches diverge significantly.
Paperclip’s approach: Model agent governance as organizational structure. Agents have roles in a hierarchy, goals that cascade from the top, and budgets allocated like headcount. The metaphor makes sense for teams thinking about AI labor as something that needs management like human labor.
Sentrely’s approach: Model agent governance as infrastructure policy. Agents have RBAC policies scoped to specific resources, approval gates for specific operations, and immutable audit trails. The metaphor comes from security engineering — think AWS IAM, not an org chart.
| Dimension | Paperclip | Sentrely |
|---|---|---|
| Core metaphor | Company org chart | Infrastructure policy engine |
| Licensing | MIT open-source | Managed service (OSS also available) |
| Self-hosted | Yes (required) | Managed cloud or Enterprise VPC |
| Runtime support | Claude Code, Cursor, others | Claude Code focused |
| Per-agent budgets | Yes | Yes — per-session hard caps |
| Human approval gates | Board-level approvals | Slack/Telegram with full context |
| RBAC (resource-level) | No — role/goal based | Yes — per-resource, per-action |
| Immutable audit trail | Basic | Purpose-built for compliance |
| Slack/Telegram integration | No | Yes — Butler bot |
| Web dashboard | No | Yes |
| Multi-agent A2A messaging | No | Yes |
| SOC 2 / HIPAA evidence | No | Yes |
| Pricing | Free (self-hosted) | Starter $49/mo |
When Paperclip Makes Sense
Paperclip is a strong fit if you:
- Want fully self-hosted, open-source agent governance with no vendor dependency
- Prefer the organizational metaphor — thinking about AI labor like managing a team
- Are using multiple agent runtimes beyond Claude Code
- Want to experiment with agent governance without committing to a paid service
When Sentrely Makes Sense
Sentrely is a stronger fit if you:
- Need resource-level RBAC: “this agent can read S3 bucket A but not B, can push to feature branches but not main”
- Need human-in-the-loop approval workflows that route to Slack with full context
- Need compliance evidence for SOC 2 or HIPAA — immutable, auditor-ready logs
- Don’t want to operate infrastructure yourself
- Are deeply invested in the Claude Code ecosystem
The Honest Assessment
Paperclip is the most philosophically interesting open-source project in this space. If you’re willing to run infrastructure and want maximum control over the governance model, it’s worth exploring.
Sentrely trades the openness of DIY for the completeness of a managed product: resource-level RBAC, Slack approval workflows, immutable audit trails, and a dashboard that works out of the box. For teams that need to show SOC 2 or HIPAA evidence — or who just don’t want to build and operate their own governance infrastructure — Sentrely closes the gap faster.
The real competition between the two isn’t features. It’s the build-vs-buy question applied to agent governance: do you want to own it or operate it?