# Paperclip AI ## Kurzbeschreibung **“Open-source orchestration for zero-human companies”** **Paperclip** is a self-hosted open-source platform for orchestrating teams of AI agents. The tool organizes agents as “employees” with an org chart, roles, budgets, governance, tasks/tickets, heartbeats, and audit trails. Paperclip is explicitly a Control Plane, not an Execution Plane: the agents run externally via adapters such as Claude Code, Codex, Gemini, Cursor, OpenClaw, shell processes, or HTTP webhooks. ## Claim The human control plane for AI labor ## Geeignet für - Audio / Voice - Marketing & Advertising - Productivity & Planning - Programming / Software Development - Project Management - SEO / GEO Optimization - Social Media - Texts / Content ## Kernfunktionen - Automation - AI Agents - Project Management ## Preismodell - **free:** According to the official website, Paperclip is MIT-licensed, self-hosted, and usable without a Paperclip account. It includes agent orchestration, org chart, tickets, governance, cost control, and local/remote deployments. - **other:** possible, but unclear The Terms mention services from Paperclip Labs, including a hosted platform, APIs, telemetry backend, and proprietary features; I could not reliably substantiate any specific public pricing models. ## DSGVO und Datenschutz **Gesamteinschätzung:** Yes **On-Prem / local hosting: covered** The website explicitly describes Paperclip as self-hosted, runnable locally, and not requiring a Paperclip account. It mentions a local instance, a single Node.js process, embedded Postgres, local files, and alternatively your own Postgres. **Private Cloud / data center: partial** The website mentions a 'remote deploy' and the use of your own Postgres. This suggests deployment in your own or isolated infrastructure. However, a dedicated private cloud offering from the provider or an EU/EEA data center is not specifically stated. **EU SaaS / managed: unclear** While the website does mention 'Services operated by Paperclip Labs, Inc.' and refers to hosted infrastructure, there is no indication of an EU SaaS variant, EU data residency, or EU/EEA data centers. **Hybrid: partial** According to the website, the product is a control plane and integrates external agents, adapters, shell processes, or HTTP webhooks. In addition, both local and remote deployments are possible. This means a hybrid operating model can generally be inferred, but it is not described as a formal hosting offering from the provider. **DPA: unclear** No DPA and no corresponding contractual page were found on the website. **No training: partial** For detailed telemetry, the website explicitly states that it is only collected after explicit activation. At the same time, if detailed telemetry is enabled, the website allows its use for operation, improvement, development, commercialization, as well as the training and improvement of machine-learning models. A general contractual exclusion of training for all content is not stated on the website. **Open source / transparency path: covered** The website clearly describes Paperclip as open source under the MIT license, self-hosted, and not requiring a Paperclip account. It also highlights that users can fork, audit, customize, and transfer the code into their own deployments. **Data processing** According to the website, Paperclip can be operated locally or remotely by the user. For local operation, embedded Postgres and local files are mentioned; alternatively, your own Postgres can be used. According to the website, Paperclip is a control plane, while the actual agents run externally via adapters. For the services operated by Paperclip Labs, the privacy policy mentions data collection relating to account, usage, telemetry, device, and communication data, as well as possible transfers to the USA. Subprocessors, specific data centers, and EU data residency are not stated on the website. **Conclusion** For an EU/EEA tool directory, Paperclip is viewed positively primarily because of the **clearly documented self-hosting and open-source path**. The *best available GDPR path* is self-hosting in EU/EEA infrastructure. The provider’s own services, by contrast, are weakly documented from a documentation perspective: no DPA can be found, no subprocessors, no EU data residency, no certifications, and data transfer to the USA is mentioned. Therefore, the positive GDPR assessment here is tied to self-hosted use, not to a documented EU SaaS offering from the provider. **Sources** - [https://paperclip.ing/](https://paperclip.ing/) - [https://paperclip.ing/tos/](https://paperclip.ing/tos/) For the EU/EEA area, Paperclip can be considered usable in a GDPR-compliant manner in the best available usage form, because the website describes a clear self-hosting/local deployment path without requiring a Paperclip account. This allows a user to operate the software in their own EU/EEA infrastructure. The services operated by Paperclip Labs are significantly more critical from a GDPR perspective, because the website mentions data transfers to the USA, does not specify EU data residency, and describes the use of data for improvement and training. **Positive** Positive aspects are the explicit self-hosting approach, the MIT license, the statement 'no Paperclip account required', local execution with embedded Postgres or the user's own Postgres, as well as the possibility of local or remote deployment. For EU/EEA users, this opens a practical way to process data exclusively within their own European infrastructure. **Negative** Negative is that, for the services operated by Paperclip Labs, the website specifies neither EU data centers nor EU data residency, DPA/AVV, subprocessors, or certifications. The privacy policy also states that data may be transferred to the USA. In addition, the website describes that data may be used to improve the services and to train or improve machine-learning models and algorithms; this is explicitly mentioned for detailed telemetry. **Server location** For self-hosting, the server location can be freely chosen by the user and may be within the EU/EEA area. For the services operated by the provider, no specific server or data center location is stated on the website; the privacy policy merely states that data may be transferred to and processed in the USA, among other places. ## Hosting und Daten - **On-Prem / lokales Hosting:** abgedeckt - **Private Cloud / Rechenzentrum:** teilweise / indirekt - **EU SaaS / Managed:** unknown - **Hybrid:** teilweise / indirekt - **AVV / DPA:** unknown - **Kein Training auf Kundendaten:** teilweise / indirekt - **Open-Source / Transparenz-Pfad:** abgedeckt ## Standort **Land:** USA **Taxonomie:** USA the official Terms name Paperclip Labs, Inc. and subject the Services to the law of the U.S. state of Delaware; additionally, the Privacy Policy mentions international transfers including the USA. A precise operational headquarters is not publicly stated. ## Vorteile - Open Source / MIT, self-hosted, no Paperclip account required. - Fast local setup with embedded PostgreSQL, without an external database. - Governance and control features: board approval, budgets, audit trail, roles/reporting. - Adapter-agnostic and technically flexible. - Clear multi-agent/multi-company positioning instead of individual prompt windows. ## Nachteile - Not a classic end-user SaaS with clearly documented pricing tiers publicly available. - Technical barrier to entry: self-hosting, Node.js/pnpm, and agent adapter setup required. - According to the README, not intended for single-agent use; often overengineered for simple chat/assistant use cases. - Important points such as multiple human users, cloud deployments, and desktop app are still only on the public roadmap. - Privacy/compliance documentation for enterprise procurement currently does not appear to be as developed as that of established SaaS providers. This assessment is based on publicly available sources. ## Quellen - Offizielle Website: https://paperclip.ing/ ## Letzter Datenstand 2026-04-15 ## Originalseite https://kifox.ai/en/ki-tools/paperclip-ai-en/