MILabs
Tools

Paperclip self-hosted AI agents: setup and business uses

Paperclip is a self-hosted AI agent project. Learn what it does, how MILabs sets it up and which businesses it suits.

Updated 2026-03-15

What Paperclip is

Paperclip is a self-hosted AI agent project and its source code is published on GitHub. Self-hosted means the software is installed and run on infrastructure that a business or its technical contact chooses, rather than used only through a vendor's hosted service. That gives the owner more say over where the software runs and which systems it connects to. A business would typically use a project like this to run AI agents against its own tools and data, with each agent's behaviour set by the team that builds it. Because the code is public, a technical reviewer can read the project before deciding whether to install it, which is a useful step for a small business. Paperclip sits beneath the accounting, booking or CRM software a business already runs, and it is one option among several for teams that want agents inside their own environment.

Paperclip: official site

Paperclip in plain language

An AI agent is a program that takes a goal, works out a sequence of steps, and calls other software to carry those steps out. A chat assistant answers a question in a window. An agent can, in principle, read a message, look up a record, check a rule and then prepare a reply or update a field, with a person deciding how far it is allowed to go. Projects in this area differ mainly in where the agent runs, how its tools are connected, and how much of its behaviour is written by the builder compared with left to the underlying model.

Paperclip belongs to the group of projects that let a team run agents in its own environment. Its appeal lies in control: the logs, the data path and the connections sit with the people running it. Running it means someone installs it, keeps it current and watches what it does. Readers comparing it with hosted products can look at who handles uptime, where prompts and records pass through, and whether the team can diagnose a failed step. Those questions usually matter more than a feature list, which changes between releases.

What businesses use it for

  • Running an internal assistant that answers staff questions from the business's own documents.
  • Triaging incoming enquiries before a person reads them, so the right team sees them first.
  • Drafting first versions of routine replies that a team member checks before sending.
  • Routing approvals and handoffs between the systems the business already uses.
  • Keeping sensitive records on a server the business controls rather than a third-party platform.

Who it suits

  • Owners who want AI agents running on infrastructure they choose.
  • Technical teams that can maintain a self-hosted deployment.
  • Businesses with existing software that needs agent work added beside it.

How MILabs sets it up

The easiest first step is to say hello through the enquiry form, and we'll take it from there. MILabs starts with the owner, and together you agree which process the agent should handle, what it may read and what it may change. The team then decides how Paperclip will be hosted and checks the setup against the business's security and data rules. Next, the systems the business already uses, such as a shared inbox, a booking calendar or a CRM, are connected to the agent layer one at a time. Permissions let each agent reach only the records its task needs. Last, you and MILabs agree who looks after the installation day to day, covering updates, credentials and what happens when an agent gets a task wrong.

Builds it fits

Industries it fits

Paperclip in practice

Inside a business, the work usually begins with a single queue that is costing staff time. It might be a shared inbox where enquiries arrive in mixed form, or a folder of policy documents that people keep asking about. The team lead chooses one queue, and the build defines what the agent reads, what it proposes and where its output lands. In the first version the agent drafts or tags and a person approves, so the team sees where its judgement agrees with theirs.

Once the agent is running, the work shifts toward the rules around it. Someone decides what the agent may write into a customer record, which fields it may change, and who is notified when it is unsure. Logs of each run become the team's main way to review behaviour, so they stay somewhere the owner can read. Staff who did the task by hand often become the most useful reviewers, because they know the edge cases a short test set would miss.

good questions, straight answers

Frequently asked questions

Can MILabs build on top of Paperclip?
Yes. MILabs can build workflows, assistants and integrations on top of Paperclip where the business's process and chosen deployment support it. Work usually starts with a scoping conversation about the process, the systems involved and who will use the result. The build is then tested against that process before anything is handed over. Scoping also shows which base suits each task, so the business hears an honest view before committing.
What does a Paperclip setup need from me?
A setup needs a named owner who decides what the agent should do, and a technical contact who confirms where Paperclip will run. You also provide access to the existing systems the agent connects to, and a clear view of which records it may read or change. Expect to agree who looks after updates and credentials after handover. We handle the configuration and connections, while decisions about data and responsibility stay with the business.
What does Paperclip not do?
Paperclip is an agent project, so it does not decide on its own what a business should automate. It does not supply the judgement about which tasks suit an AI agent, and it does not remove the need for someone to own the result. Hosting it yourself also means the business, or its contractor, keeps it running and up to date.
Is Paperclip suitable for a small business?
Yes, Paperclip suits a small business that has someone technical to keep it running and a clear reason to host its own agents. A business without that capacity may get more from a hosted tool, and MILabs will say so plainly. Running a server and keeping it patched takes ongoing effort, which is the main cost to weigh. Start by naming the process you want help with, then decide whether self-hosting is needed.
Is Paperclip safe to use with customer data?
Yes, customer data can stay on infrastructure the business chooses, which is the main reason to consider self-hosting. Safety depends on how the server is secured, who holds the credentials and which systems the agent may reach. MILabs sets permissions so each agent sees only the records its task needs, and we agree how access is reviewed.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.