What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To get Paperclip running on a VPS, deploy it from the VPS Application Catalog, open the project in Docker Manager, then create an organization and configure an agent. Add an AI provider credential during deployment if you want agents to run model-powered tasks straight away; you can also connect one later.
What you need before you start
- A VPS and access to its control panel.
- The admin email address and password you will use for the Paperclip instance.
- An AI provider credential if you want to run agent tasks immediately. Deployment can finish without one, but agents cannot execute tasks that require a model until a provider is connected.
The documented catalog route uses Docker, so you do not need to perform a separate manual Docker installation for that flow. For current installation details, see the Paperclip installation guide.
As an Amazon Associate I earn from qualifying purchases.
Deploy Paperclip from the Application Catalog
- Sign in to your VPS provider account and open the VPS management area.
- Open the VPS Application Catalog and select Paperclip.
- Complete the deployment form, including the requested administrator credentials. If the form offers AI provider credentials and you already have them, enter them now; otherwise, you can configure a provider after deployment.
- Start the deployment and wait for it to finish.
- Open Docker Manager, select the Paperclip project, and launch it. Sign in with the admin email and password supplied during setup.
The exact dashboard labels can change. The installation guide describes the catalog deployment and opening the project through Docker Manager.
Recommended Free Tools
Create an organization and configure your first agent
Create the organization
On first login, follow Paperclip’s onboarding to create an organization. This gives the instance a workspace in which to configure agents and define work.
#1 Best Overall
Set up the agent
Configure the agent’s adapter, working directory, and model settings. The adapter determines how the agent is connected to its execution environment; the working directory identifies where it should work. Choose model settings that match the provider connection you configured.
Connect a model provider and assign work
If you did not enter credentials during deployment, add the provider connection in Paperclip before asking an agent to run a task. Then define a small, specific first task and assign it to the configured agent. The setup sequence—organization, agent configuration, then work—is outlined in the Paperclip installation guide.
Rank #2
Provider credentials enable model access; they do not establish that API usage is included with the VPS. Check the provider’s own billing and usage terms, and use Paperclip’s spending limits and monitoring practices to keep agent activity visible. Paperclip discusses these operational controls in its setup documentation.
How much VPS capacity should you choose?
The published starting points differ, and neither cited source provides a workload benchmark. Treat them as separate recommendations rather than a verified minimum or a guarantee of how many agents a server can run.
Rank #3
| Guidance | Published capacity | What it means |
|---|---|---|
| Basic setup recommendation | 2 vCPU cores, 4 GB RAM, and 50 GB SSD | This is presented as a basic configuration for a small team of agents; it is guidance, not an independently tested minimum. |
| Paperclip’s official installation guidance | 1 vCPU and 2 GB RAM | Paperclip says a Linux VPS with these resources is enough to get started. The page does not state a publication year. Paperclip installation guide |
Choose capacity with your expected agent activity and workload in mind. The figures above do not establish performance under a particular number of agents or tasks.
Quick Recap
Rank #4
Catalog deployment or direct installation?
| Route | Best suited to | Trade-off |
|---|---|---|
| Application Catalog with Docker | Operators who want the documented, guided setup | Fewer manual installation steps; the deployment follows the catalog’s Docker-based flow. |
| Direct Docker or terminal installation | Operators who want more control or are using another Linux VPS | You take responsibility for installation and server configuration. The setup tutorial describes a direct Node.js onboarding alternative and lists Node.js 20+ and pnpm; requirements can change, so consult Paperclip’s current installation guide before following that route. Paperclip also documents Docker deployment. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




