{"id":30927,"date":"2026-05-15T10:00:00","date_gmt":"2026-05-15T08:00:00","guid":{"rendered":"https:\/\/contabo.com\/blog\/?p=30927"},"modified":"2026-05-31T16:56:39","modified_gmt":"2026-05-31T14:56:39","slug":"what-is-paperclip-ai","status":"publish","type":"post","link":"https:\/\/contabo.com\/blog\/what-is-paperclip-ai\/","title":{"rendered":"What Is Paperclip AI? Features, Pricing, and Alternatives Compared [2026]\u00a0"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Running a single AI agent is manageable. Running five of them simultaneously across overlapping tasks, while tracking costs, preventing duplicate work, and making sure each agent understands what the others are doing? That’s a completely different challenge. Paperclip AI was built to solve that second problem. <\/p>\n\n\n\n

Launched on March 2, 2026, by a pseudonymous developer known as @dotta, Paperclip is an open-source AI orchestration platform that wraps individual AI agents inside a company structure. Instead of managing a pile of disconnected scripts and terminal tabs, you define an org chart with roles, reporting lines, budgets, and governance, then let your agents work autonomously within that structure. The project crossed 30,000 GitHub stars within its first three weeks and surpassed 53,000 by early April 2026, placing it among the fastest-growing open-source agent projects ever released. <\/p>\n\n\n\n

At its technical core, Paperclip is a Node.js server paired with a React dashboard, backed by PostgreSQL. It runs entirely self-hosted, with no Paperclip account required. <\/p>\n\n\n\n

Where Paperclip AI Fits: Orchestrator vs. Assistant vs. Framework\u00a0<\/h2>\n\n\n\n

Paperclip AI occupies a specific and relatively new position in the AI tooling landscape. It’s not a coding assistant like Claude Code or a chat interface like Claude. It’s not a framework for building agents from scratch like LangChain or AutoGen. It’s an AI orchestrator, a layer that sits above existing agents and coordinates how they work together toward a shared business goal. <\/p>\n\n\n\n

The simplest way to understand the distinction: if OpenClaw is an employee, Paperclip is the company. Individual agents handle the execution. Paperclip handles the coordination, the accountability, and the governance. For a full breakdown of how Paperclip compares head-to-head with other agent frameworks, see our dedicated comparison at \/blog\/paperclip-ai-alternatives\/. <\/p>\n\n\n\n

How Paperclip AI Works: Agents, Companies, and the Heartbeat Loop\u00a0<\/h2>\n\n\n\n

Company Modeling and Organizational Hierarchy\u00a0<\/h3>\n\n\n\n

The central abstraction in Paperclip is the company. When you set up Paperclip, you’re not configuring a workflow or a pipeline. You’re defining an organization. That organization has a mission, a set of goals, projects, and a roster of Paperclip AI agents occupying specific roles. <\/p>\n\n\n\n

Those roles map to a genuine org chart. You might configure a CEO agent at the top, reporting to you as the board. Beneath it, a CTO agent oversees a backend engineer and a QA agent. A marketing director manages a copywriter. Each agent carries a title, reporting relationships, defined permissions, and a monthly spending budget. A single Paperclip AI company deployment can also run dozens of separate companies from one install, with complete data isolation between them. This makes it practical to run separate ventures, test strategies in parallel, or use portable org templates for repeatable configurations. <\/p>\n\n\n\n

Goal Alignment, Task Routing, and the Heartbeat Loop\u00a0<\/h3>\n\n\n\n

One of the more technically distinctive features of Paperclip is how it handles agent context. Rather than giving each Paperclip AI agent an isolated prompt and hoping for coherent output, the platform builds goal ancestry into every task. When an agent picks up a piece of work, that task carries the full chain of context leading back to the company mission: which project it belongs to, which goal it serves, and why the task matters. The agent consistently sees the why, not just a title. <\/p>\n\n\n\n

Task routing flows through the org chart. When work needs to be delegated, it moves to whichever agent is best positioned for the job. Cross-team requests are routed automatically without manual intervention. <\/p>\n\n\n\n

The mechanism that drives execution is the heartbeat loop. By default, Paperclip AI agents don’t run continuously. They wake on a defined schedule, typically every four, eight, or twelve hours depending on configuration. When a heartbeat fires, the orchestration software checks the agent’s task queue, injects context and skills, enforces the budget, and invokes the adapter. Agents can also wake immediately on event-based triggers: direct task assignments or @-mentions bypass the schedule and activate the agent at once. This scheduled, context-aware approach prevents the runaway loops that cause unexpected API bills when agents operate without guardrails. <\/p>\n\n\n\n

Governance, Budgets, and Cost Controls\u00a0<\/h3>\n\n\n\n

Paperclip treats governance and cost control as first-class features of the orchestration platform, not afterthoughts. Key controls built into the system include: <\/p>\n\n\n\n

Each agent receives a hard monthly spending cap. At 80% utilization, a soft warning fires. At 100%, new tasks are blocked and the agent auto-pauses. As the board, you can override the limit at any time. <\/p>\n\n\n\n

Task checkout is atomic. When an agent claims a task, an execution lock is placed on it, preventing any other agent from picking up the same work simultaneously. No duplicate runs, no wasted tokens. <\/p>\n\n\n\n

Approval gates cover structural changes. Hiring new agents, modifying strategic plans, and certain configuration changes require board sign-off before they execute. <\/p>\n\n\n\n

All agent actions are logged in an append-only audit trail that records which agent did what, at what cost, and in what task context. Configuration changes are versioned and bad changes can be rolled back safely. <\/p>\n\n\n\n

Core Features of the Paperclip AI Platform\u00a0<\/h2>\n\n\n\n

Multi-Agent Orchestration and Role Assignment\u00a0<\/h3>\n\n\n\n

Paperclip’s AI orchestration model differs from pipeline-based orchestration software in a meaningful way. Most tools assemble agents into a linear or branching workflow where steps execute in sequence. Paperclip instead models your agents as an organization operating continuously toward long-running goals. Tasks are assigned to agents by role, agents can delegate to one another through the org chart, and work persists across sessions rather than resetting with each run. <\/p>\n\n\n\n

Each Paperclip AI agent has a role, a title, reporting relationships, and defined skills. Agents aren’t interchangeable. They’re specialists. A research agent using Gemini CLI for its large context window handles a different class of work than a backend engineer running on Codex. The orchestration platform routes tasks to whichever agent is best suited, without requiring manual management of that routing. <\/p>\n\n\n\n

Adapter Ecosystem: Claude, Hermes, Codex, Gemini CLI, and More\u00a0<\/h3>\n\n\n\n

Paperclip is unopinionated about which agent runtime you use. Its adapter system is the mechanism that makes this possible. An adapter is the integration layer between Paperclip’s scheduler and a specific execution environment, and Paperclip ships with an extensive set of them. <\/p>\n\n\n\n

The Claude Code adapter is the most widely documented path and the one recommended in Paperclip’s onboarding wizard. It wraps a local Claude Code session, injecting goal context, budget state, and runtime skills directly into the agent’s environment before execution begins. <\/p>\n\n\n\n

The Codex adapter connects Paperclip to OpenAI’s Codex CLI, with model discovery that merges locally configured models with options fetched from the OpenAI API. Custom or fine-tuned models show up automatically in Paperclip’s selector. <\/p>\n\n\n\n

The Gemini CLI adapter provides full local support for Google’s Gemini CLI, including API key detection, turn-limit handling, sandbox and approval modes, and skill injection. It suits tasks requiring large context windows or multimodal reasoning. <\/p>\n\n\n\n

Paperclip Claude integration also extends to MCP through the @paperclipai\/mcp-server package, which exposes the Paperclip REST API as a set of MCP tools. This means you can connect Claude Desktop to your Paperclip instance and manage agents, create issues, and approve actions through natural language. <\/p>\n\n\n\n

The Paperclip Hermes integration is maintained by Nous Research as a standalone package called hermes-paperclip-adapter. It brings Hermes Agent into the Paperclip company structure with persistent session state across heartbeats, structured transcript parsing, and access to Hermes’s native 30-plus tools and 80-plus skills. <\/p>\n\n\n\n

Additional built-in adapters cover Cursor, Pi, OpenCode (a multi-provider CLI), and the OpenClaw Gateway for remote HTTP-based agents. The Paperclip AI plugins system, added in a subsequent release, allows third-party adapters to be installed as npm packages or loaded from local directories. As Paperclip’s own documentation puts it: if it can receive a heartbeat, it’s hired. <\/p>\n\n\n\n

Open-Source Architecture and the Paperclip GitHub Repository\u00a0<\/h3>\n\n\n\n

Paperclip AI is MIT licensed and fully self-hostable. The Paperclip GitHub repository at github.com\/paperclipai\/paperclip contains the complete source, including the Node.js server, the React UI, all adapter packages, CLI tooling, and the onboarding wizard. There’s no proprietary core. <\/p>\n\n\n\n

The codebase is organized as a monorepo managed with pnpm. Adapter packages live under packages\/adapters\/, each wrapping a specific CLI runtime. Skills, the markdown context files that teach agents how to use Paperclip’s API, are stored under .agents\/skills\/ and are adapter-agnostic. The same SKILL.md files work across Claude Code, Codex, Gemini CLI, and any other connected runtime, and upgrading a skill upgrades every agent that uses it without a redeploy. <\/p>\n\n\n\n

Locally, a single Node.js process manages an embedded PostgreSQL instance and local file storage, so there’s no external database to configure for a development install. For production, you point Paperclip at an external Postgres instance and deploy it to whatever infrastructure your stack uses. <\/p>\n\n\n\n

Dashboard, Observability, and Agent Monitoring\u00a0<\/h3>\n\n\n\n

The Paperclip app has drawn consistent comparisons to Linear. It uses a dark theme, sidebar navigation, and an issue-tracker layout that developers find immediately familiar. The resemblance is intentional. Paperclip surfaces agent work as tickets, not raw logs, so you manage your agents the way you would manage a team. <\/p>\n\n\n\n

From the Paperclip AI dashboard, you can view the full org chart, track which agent holds which task, review run transcripts, and monitor per-agent and per-project spending. Cost visibility is granular: you can see which agents are expensive, which tasks are burning tokens, and which projects are running over budget. The dashboard also surfaces approval queues, agent heartbeat schedules, and an inbox that groups incoming work, @-mentions, and board actions in one place. The Paperclip docs at paperclip.ing cover the full dashboard reference including API documentation for teams that want to build on top of the platform programmatically. <\/p>\n\n\n\n

Paperclip AI Use Cases: Who’s Building With It?\u00a0<\/h2>\n\n\n\n

Autonomous Product Development Teams\u00a0<\/h3>\n\n\n\n

The most active use case in the Paperclip community involves software product development. A typical Paperclip factory AI setup for an engineering team assigns a CTO-level manager agent to decompose feature requests into sub-tasks, which are then routed to backend engineer agents running on Claude Code or Codex, a QA agent that validates the output, and a documentation agent that keeps written specs current. The whole team operates on heartbeat schedules, with approvals gating any architectural decisions or dependency changes. For any Paperclip AI company already managing multiple coding agent sessions manually, this model replaces ad-hoc coordination with a defined org structure that persists across reboots and keeps a full cost audit trail automatically. <\/p>\n\n\n\n

AI-Driven Marketing and Content Operations\u00a0<\/h3>\n\n\n\n

Paperclip has found a practical fit in content and marketing operations, where work is repetitive, well-structured, and easy to decompose by role. A content-focused Paperclip AI company typically includes a research specialist that pulls topic briefs and competitive data, a copywriter agent that drafts from the brief, a reviewer that checks structure and coverage, and a publishing agent that formats output for the target CMS. Each role runs on a heartbeat schedule aligned to the content calendar, with a director-level agent handling task routing between them. The automation orchestration tools built into Paperclip manage session continuity and cost tracking across the entire pipeline without manual intervention between steps. <\/p>\n\n\n\n

End-to-End Business Automation\u00a0<\/h3>\n\n\n\n

Early Paperclip companies have demonstrated that the platform extends well beyond engineering or content pipelines. Example workflows running in production or advanced testing include: <\/p>\n\n\n\n

A B2B outreach pipeline where a lead researcher identifies prospects, a copywriter drafts personalized sequences, and a QA agent validates tone and deliverability before anything is sent. <\/p>\n\n\n\n

An internal knowledge management setup where Paperclip AI agents continuously process meeting transcripts, update documentation, and flag open action items to the relevant team member. <\/p>\n\n\n\n

A product QA loop where agents run regression tests after every deployment, file issues for any failures, and escalate to a human reviewer only when confidence falls below a defined threshold. <\/p>\n\n\n\n

A competitive intelligence workflow where agents monitor defined sources on a recurring schedule, extract key data points, and produce weekly briefings automatically. <\/p>\n\n\n\n

Paperclip AI Pricing: Is It Free? Open-Source vs. Hosted Plans\u00a0<\/h2>\n\n\n\n

Paperclip AI is free. There are no license fees, no subscription tiers, and no managed cloud offering as of mid-2026. The MIT license means you can download the code, self-host it, and run it without paying Paperclip anything. This makes it a genuinely free, open-source alternative to commercial orchestration tools. <\/p>\n\n\n\n

What you do pay for is infrastructure and LLM usage. You’ll need a server capable of running Node.js, a PostgreSQL instance, and you’ll incur API costs from whichever model providers your agents use. Claude Code Max at $200 per month is widely used in the Paperclip community for heavier workloads, as it bundles usage allocation rather than charging per token individually. Running multiple Paperclip AI agents on raw API credits can get expensive quickly, particularly for workflows with frequent heartbeats across many agents. <\/p>\n\n\n\n

A hosted or managed plan has been discussed on the roadmap, but hadn’t launched publicly at the time of writing. The Clipmart marketplace, which would allow importing and sharing of portable company templates from github.com\/paperclipai\/companies, is also in active development but hasn’t launched yet. <\/p>\n\n\n\n

How to Get Started With Paperclip AI\u00a0<\/h2>\n\n\n\n

Getting Paperclip running locally requires a single command. With Node.js version 20 or later installed, run: <\/p>\n\n\n\n

npx paperclipai onboard --yes\u00a0<\/code><\/pre>\n\n\n\n
The onboarding wizard handles database setup, authentication configuration, and the creation of your first company. It defaults to a trusted local loopback mode for the fastest first run. For network access, you can bind to a LAN or Tailnet preset instead. <\/p>\n\n\n\n
Adapter setup comes next. The wizard recommends Claude Code and Codex as the starting point, and walks you through environment checks for each before your first agent goes live. Full deployment documentation, adapter configuration references, and skill authoring guides are available in the Paperclip docs at paperclip.ing. For teams planning a production VPS deployment, a detailed Ubuntu self-hosting tutorial on Contabo covers the full server setup, so those steps aren’t repeated here. <\/p>\n\n\n\n
Frequently Asked Questions About Paperclip AI<\/h2>\n\n\n\n
What is Paperclip AI and how does it work?\u00a0<\/strong> 
Paperclip AI is an open-source AI orchestration platform that models a team of AI agents as a company with an org chart, roles, budgets, and governance. You define the company structure and assign tasks. Agents wake on scheduled heartbeats, receive goal ancestry from the task hierarchy, and act using whatever execution runtime their adapter connects to. Paperclip handles the coordination, cost tracking, and approval logic. The agents handle the actual work.\u00a0<\/p> <\/div> 
Is Paperclip AI free and open source?\u00a0<\/strong> 
Yes. Paperclip AI is MIT licensed and completely free to use. The full source code is available on the Paperclip GitHub repository at github.com\/paperclipai\/paperclip. There’s no paid plan and no account required to run it. Your costs are limited to the server infrastructure you deploy it on and the LLM API usage your agents generate. A hosted cloud option is on the roadmap but hadn’t launched as of mid-2026.\u00a0<\/p> <\/div> 
What adapters and LLMs does Paperclip AI support?\u00a0<\/strong> 
Paperclip ships with built-in adapters for Claude Code, Codex, Gemini CLI, Cursor, Pi, OpenCode, and OpenClaw. MCP support is available through the @paperclipai\/mcp-server package, which exposes the Paperclip API as callable tools for any MCP-compatible assistant. The Paperclip Hermes adapter is available as a separate package from Nous Research. The Paperclip AI plugins system also allows third-party adapters to be installed as npm packages. Paperclip is model-agnostic at the orchestration layer. The LLM is determined by the adapter and agent configuration, not by Paperclip itself.\u00a0<\/p> <\/div> 
What type of tool is Paperclip AI?\u00a0<\/strong> 
Paperclip AI is an AI orchestration platform, described by its own team as the human control plane for AI labor. It sits above individual agent runtimes and coordinates how multiple agents work together within a company structure. It’s not a coding assistant, a chatbot, or an agent-building framework. It’s the organizational layer that turns a collection of independent AI agents into a managed, goal-aligned team operating within defined budgets and governance rules.\u00a0<\/p> <\/div> 
What types of businesses or teams use Paperclip AI?\u00a0<\/strong> 
The primary adopters as of 2026 are technical founders building autonomous product development workflows, content and marketing teams orchestrating multi-agent pipelines, and developers experimenting with Paperclip factory AI configurations across multiple companies from a single deployment. The platform is most practical for anyone already running two or more agent sessions simultaneously and finding coordination and cost tracking unmanageable without dedicated tooling. Larger Paperclip companies with multiple agent roles and ongoing goal hierarchies benefit\u00a0<\/p> <\/div> <\/div>\n","protected":false},"excerpt":{"rendered":"
What is Paperclip AI and is it right for you? This guide covers how the open-source AI orchestration platform works, its key features, real use cases, pricing, and how it compares to LangChain, AutoGen, and other agent frameworks.<\/p>\n","protected":false},"author":50,"featured_media":30642,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[18],"tags":[],"ppma_author":[1491],"class_list":["post-30927","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials"],"uagb_featured_image_src":{"full":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip.webp",1200,630,false],"thumbnail":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip-150x150.webp",150,150,true],"medium":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip-600x315.webp",600,315,true],"medium_large":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip-768x403.webp",768,403,true],"large":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip.webp",1200,630,false],"1536x1536":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip.webp",1200,630,false],"2048x2048":["https:\/\/contabo.com\/blog\/wp-content\/uploads\/2026\/05\/blog-head_what-is-paperclip.webp",1200,630,false]},"uagb_author_info":{"display_name":"Tobias Mildenberger","author_link":"https:\/\/contabo.com\/blog\/author\/tobias\/"},"uagb_comment_info":0,"uagb_excerpt":"What is Paperclip AI and is it right for you? This guide covers how the open-source AI orchestration platform works, its key features, real use cases, pricing, and how it compares to LangChain, AutoGen, and other agent frameworks.","authors":[{"term_id":1491,"user_id":50,"is_guest":0,"slug":"tobias","display_name":"Tobias Mildenberger","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/077178d5dce6c3d4c0c0396857a7e544bfdf8adf04145fff5160b33a22e28b1f?s=96&d=mm&r=g","0":null,"1":"","2":"","3":"","4":"","5":"","6":"","7":"","8":""}],"_links":{"self":[{"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/posts\/30927","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/users\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/comments?post=30927"}],"version-history":[{"count":1,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/posts\/30927\/revisions"}],"predecessor-version":[{"id":30928,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/posts\/30927\/revisions\/30928"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/media\/30642"}],"wp:attachment":[{"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/media?parent=30927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/categories?post=30927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/tags?post=30927"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/contabo.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=30927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}