Ybkkasi screenshot thumbnail

Ybkkasi

Enterprises keep buying AI tools and wondering why output does not compound, when the real gap is governance: nobody can say which agent owns what, what it may touch, or what it cost. Ybkkasi answers those three questions in one console for every MCP server, skill, agent, and AI application you run. Register each asset and move it through a lifecycle state machine from discovery to retirement, with 85 permission points deciding who can view, call, publish, or approve at every step. Work itself is organized as goals that break into projects and tasks, assigned to digital employees who each carry a home organization, a human supervisor, and a roster status. Approvals route through a dedicated center where lifecycle changes and sensitive actions wait for a human decision instead of happening silently. Every call is metered, so usage and cost reports attribute spend by department, by agent, and by skill, making showback a query rather than an argument. The audit log records who did what to which asset and when, giving compliance a trail they can actually read. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
Paperclip screenshot thumbnail

Paperclip

With over 77,000 GitHub stars accumulated in under five months since its March 2026 launch, Paperclip has become the default control plane for teams running multiple AI agents in production. Rather than juggling dozens of terminal tabs with Claude Code sessions, Codex instances, and Gemini CLI workers, Paperclip organizes all agents into a company structure with org charts, reporting lines, role-based permissions, and per-agent monthly budgets that trigger hard-stops when exceeded. The platform supports any runtime through its adapter system — Process adapters manage local CLI agents like Claude Code, Codex, Cursor, Pi, and OpenCode as child processes, while HTTP adapters trigger remote agents via webhooks to OpenClaw, serverless platforms, or custom endpoints. Heartbeat-based execution wakes agents on configurable schedules, injecting goal context, budget state, and workspace paths directly into the invocation payload. The Work and Task System provides atomic checkout with execution locks, first-class blocker dependencies, and structured work products to eliminate duplicate effort. Governance features include approval workflows, decision tracking, emergency stops, and full audit trails tracing every mutation to an actor. Deployment runs as a single Node.js process with embedded PostgreSQL locally or scales to external Postgres for production, installable in one command via npx paperclipai onboard. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy