Hostinger promises that deploying a self-hosted AI agent organization on a VPS should take minutes, not a weekend. I deployed Paperclip on a KVM 2 plan, ran a full benchmark suite with live containers active, and went through the complete setup flow.
I tested support with genuinely technical questions, and watched an agent complete a real task autonomously.
The results were largely impressive, with one caveat that every new user needs to know before they start. Read on for the full picture.
I evaluated Hostinger Paperclip VPS using our standard hosting review methodology, which covers pricing, features, performance, ease of use, and support.
The scores below reflect a live deployment with Paperclip and Traefik running throughout testing, not a clean bare server.
| Category | Score | Explanation |
|---|---|---|
| Prices | 9.2/10 | Competitive intro pricing across four plans, but renewal rates are notably higher. Refund has a 180-day condition between VPS claims. |
| Features | 9.8/10 | Paperclip and Traefik auto-deploy together, Docker Manager, Kodee AI, AMD EPYC, NVMe, 1 Gbps network, managed firewall, free weekly backups, and browser terminal all included. |
| Performance | 9.2/10 | Near-gigabit symmetric speeds, 11,200 random IOPS on both read and write, linear CPU scaling, and zero stress test failures. All benchmarked with live containers running. |
| Ease of Use | 9.6/10 | Clean checkout flow, intuitive hPanel, and a well-structured Paperclip onboarding wizard. One manual Claude authentication step adds friction for first-time users. |
| Support | 9.0/10 | Kodee handles technical questions well and gave accurate Paperclip-specific guidance. Human wait was 26 minutes. Agent handoff added brief uncertainty, but Itael’s technical depth was excellent. |
| Overall | 9.4/10 | A capable, well-supported platform for self-hosting Paperclip. Strong infrastructure, good onboarding, and enough headroom on KVM 2 for small to medium agent workloads. |
Hostinger offers four KVM VPS plans, and all of them support Paperclip. You are not locked into a specific tier to access the application.
Paperclip itself is MIT-licensed and free. The only ongoing costs are the VPS plan and the AI API usage from whatever model provider you connect.
All plans are billed upfront for the term you choose. The longer the commitment, the steeper the promotional discount. A billing period selector on the order page lets you compare what you pay across different term lengths before committing.
A few things worth knowing before you buy:
Payment methods accepted include card (Visa, Mastercard, Discover, Amex), PayPal, Google Pay, AliPay for China and Hong Kong, and Coingate for cryptocurrency.
Deploying a self-hosted AI orchestration platform sounds like the kind of thing that should require a weekend, a terminal, and three cups of coffee. Hostinger’s pitch is that it does not have to be.
I wanted to test that claim end-to-end, from the moment I landed on the website all the way through to a live Paperclip instance in my dashboard.
I also looked at how the hPanel holds up as your day-to-day management layer once everything is running. Here is what I found.
Getting to Paperclip starts at the Hostinger homepage, and the path is clean. Under the Services menu, VPS hosting sits in the Host and Deploy column with a short description underneath it. No hunting required.
Clicking through takes you to the VPS landing page, which leads with the headline specs and a single Choose Plan button.
The plan comparison page puts all four tiers side by side and is easy to scan:
All four plans support Paperclip. Once you pick your plan, the order page walks you through the remaining configuration:
Clicking it opens a short confirmation modal that explains what Paperclip is before you commit, which is a thoughtful touch.
After confirming, the cart updates to show “Paperclip auto-deploys with your VPS,” which means installation happens as part of provisioning and requires nothing from you afterward.
The order summary on the right stays visible throughout and shows the full breakdown, including the original price, your discounted total, the free domain for the first year, and taxes. No surprises at the final step.
If you are a new user, you register at this stage. The form is minimal:
Payment options are broad. Hostinger covers:
From landing on the VPS page to completing payment, the whole process took me under ten minutes.
After payment, Hostinger drops you into hPanel, which is the central control panel for everything you own on the platform.
The landing page greets you by name and surfaces a “Your to-dos” section at the top, which either flags pending actions or confirms everything looks clean. Below that, your active services appear in organized blocks covering websites, domains, and a dedicated VPS section.
The VPS section on the home screen shows each server with:
The left sidebar keeps navigation clear and logically grouped:
Your Paperclip VPS sits under the VPS section in the sidebar and also appears in the VPS block on the home screen, so you can reach it from either place.
A few things about hPanel stood out to me. The home screen works well as a glance view. You can see which servers are running, when they expire, and what their IPs are without clicking into anything.
Nothing important is buried more than one level deep. The dashboard serves as the management layer for your entire Hostinger account, so if you are running multiple services, it all lands in one place.
If you are here exclusively for Paperclip, the dashboard is slightly broader than you need, but the VPS section is easy enough to navigate straight to every time.
Kodee, Hostinger’s AI assistant, is accessible from the top bar on every page. If you hit a question about your server mid-task, you can open it without leaving wherever you are in hPanel.
With the VPS provisioned and payment done, the next step is getting into Paperclip itself.
From the hPanel home screen, the VPS section shows all your running servers. Clicking Manage next to your server opens the individual VPS overview page, and this is where things get interesting.
The overview page surfaces a lot at a glance:
But the standout detail on this page is the top card. It reads: Docker and Traefik, Built on Ubuntu 24.04, and there is a direct link to the Docker Manager. This is where you go to access Paperclip.
Clicking into the Docker Manager reveals something that genuinely impressed me. Without me doing anything beyond completing checkout, two containers were already live and running:
Traefik is a reverse proxy and load balancer that handles incoming traffic routing and SSL termination. Its job here is to sit in front of Paperclip and manage how requests reach it.
The fact that both containers are up and healthy from the moment you land in the Docker Manager means Hostinger has done the heavy lifting in the background.
You are not staring at a blank server waiting to run docker-compose commands. Everything is already running.
To get into Paperclip, I clicked the Open link on the paperclip container, which launched the Paperclip sign-in page in a new tab. The login uses the same credentials you signed up with on Hostinger.
From there, Paperclip walks you through a four-step onboarding wizard:
The adapter environment check on the Agent step is where I hit the one friction point in this entire process.
Running the live probe returned a warning: the Claude CLI was installed and the working directory was valid, but Claude was not logged in.
The fix required a short detour:
The probe then came back green: Passed.
This Claude authentication step is expected behavior for a self-hosted setup and is not a Hostinger-specific issue.
Paperclip cannot pre-authenticate Claude on your behalf because it needs your personal Claude account or API key. Plan for this step before your first run. The whole process takes about three minutes once you know what to do.
After clicking Create and Open Issue on the launch screen, Paperclip dropped me into its main interface, and the difference from what I expected was striking.
This does not look like a typical AI chat tool. It looks like a project management platform.
The left sidebar is organized into clear sections:
The task I created appeared as a tracked issue, complete with an issue number (HOS-1), a status badge (In Progress), a priority level (Medium), an assignee (Content Researcher), and a project tag (Onboarding).
The Properties panel on the right showed the full metadata: assignee, project, parent task, sub-issues, reviewers, approvers, monitor schedule, created timestamp, and started timestamp. Every task in Paperclip is a structured record, not just a chat prompt.
The Chat tab is where the agent works. Once launched, Content Researcher picked up the task immediately and its activity appeared in real time.
Watching it work was genuinely interesting:
The task was created at 5:59 PM and marked as Done at 6:01 PM. Two minutes from launch to a completed, structured research output, with the status updated automatically in the Properties panel.
The completed output appeared as a formatted document inside the issue, titled “Research Complete: Top 3 VPS Hosting Providers,” with each provider broken down by pricing, performance, standout features, and best-fit use case.
The agent updated the task status from “in progress” to “done” on its own, which also pushed a notification to the Inbox.
The audit trail is immutable. Every action the agent took, every tool it called, and every status change it made is logged with a timestamp and visible in the Activity tab.
If you ever need to know exactly what your agent did and when, the record is there.
Getting from the Hostinger homepage to a live, working Paperclip instance with a completed agent task took me roughly 25 minutes end-to-end. For a self-hosted AI orchestration platform, that is a genuinely fast experience.
The registration and checkout flow is clean and well-thought-out. Hostinger surfaces the right configuration options at the right time, including billing period, data center location with latency figures, and the Paperclip one-click install, without overwhelming you with choices. The cart confirms everything before you pay, and the onboarding has no unnecessary steps.
The hPanel dashboard is organized and easy to navigate, and the VPS management layer gives you instant access to all the controls you actually need without burying them. The Docker Manager being the bridge to Paperclip is logical once you know it, though a more prominent “Open Paperclip” button on the VPS overview page would remove one moment of uncertainty for new users.
The Paperclip onboarding wizard is well structured. The four-step flow from company to agent to task to launch gives you a functional AI organization in a single sitting. The only real friction is the Claude authentication step, which requires a short terminal session before your first agent can run.
This is not a flaw so much as a necessary reality of self-hosted tooling, but clearer in-app guidance at that step would help users who are less comfortable with a terminal.
Once you are past setup, Paperclip itself is impressive. The interface is mature, the issue tracking model makes agent work auditable and manageable, and watching an agent pick up a task, reason through it, use tools, and close the issue autonomously in two minutes makes the promise of Paperclip feel concrete rather than theoretical.
Before getting into the numbers, it is worth setting the scene. The server I tested is a KVM 2 plan running Ubuntu 24.04.4 LTS with kernel 6.8.0-111-generic, hosted in Hostinger’s Phoenix, Arizona data center.
The underlying processor is an AMD EPYC 9354P, a high-core-count server chip, with 2 vCPUs allocated to this plan. Total RAM is 7.8 GiB and disk space is 96 GB usable on a NVMe-backed volume.
One thing that makes this benchmark different from a standard bare-metal VPS test: Paperclip and Traefik were both running as live Docker containers throughout the entire test.
From the hPanel overview, the server showed 2% CPU usage and 12% memory utilization at idle with both containers active, meaning roughly 936 MB of RAM was already committed before a single benchmark ran. Traefik alone was consuming 110.50 MB of RAM from the available pool.
These results reflect real-world conditions, not a clean server. For anyone evaluating whether a KVM 2 can comfortably run Paperclip while still having headroom for agent workloads, that context matters.
I ran sysbench at both single-thread and multi-thread levels, using a prime number limit of 20,000 across both passes.
Single-thread:
Multi-thread (2 threads):
The scaling story here is clean. Going from one thread to two produced 3,178 events per second against 1,638 on a single core, a near-perfect 1.94x multiplier.
That tells you both vCPUs are genuinely available and contributing equally, rather than one core carrying most of the load. The thread fairness standard deviation of 117.00 on the multi-thread run is slightly elevated but within normal range for a shared cloud environment.
For Paperclip, the practical implication is that the KVM 2’s two cores handle concurrent agent activity cleanly.
The agent heartbeat system and task execution do not compete badly with each other at this core count, at least at low to moderate agent volumes.
I used sysbench with a 1K block size and a 10 GiB total transfer for both sequential write and read passes.
Sequential Write: 5,930 MiB/sec
Sequential Read: 6,897.75 MiB/sec
Both passes returned 0.00ms average latency at millisecond precision, meaning memory access is happening faster than the measurement tool can register.
The read speed outpaces write by a healthy margin, which is a normal and desirable pattern for workloads that pull data from memory more than they commit to it.
For Paperclip specifically, this matters because each agent maintains persistent state and reads its context files (HEARTBEAT.md, SOUL.md, TOOLS.md) before acting on any task. Fast memory throughput keeps that retrieval snappy and means agents spend less time loading context before getting to work.
I used fio for disk testing across three scenarios: sequential write, sequential read, and random 4K mixed read/write.
Sequential Write:
Sequential Read:
Random 4K Mixed Read/Write:
The sequential numbers are exceptional. Over 1 GiB/s on sequential reads and 814 MiB/s on writes are results you would expect from a high-end NVMe setup, and the near-symmetrical random 4K IOPS of 11,200 on both read and write simultaneously is the number that matters most for real workloads.
Database reads, Docker layer pulls, and agent log writes all depend on random I/O performance, and 11.2k IOPS on each side at the same time is a strong result for a two-core plan.
The audit trail Paperclip maintains for every agent action is written to disk continuously. Strong random write IOPS means that logging overhead stays low and does not become a bottleneck as task volume grows.
I ran a single Ookla speedtest against the nearest available server.
The results are near-symmetrical gigabit performance with essentially zero packet loss. It is worth being transparent about what this measures: the test server was Hostinger’s own infrastructure in Phoenix, the same location as the VPS.
This reflects the quality of Hostinger’s internal network and local routing rather than general internet throughput to arbitrary destinations.
Real-world speeds to external services and users will vary depending on their location and the paths between them and Phoenix.
That said, 0.38ms idle latency and zero packet loss are exactly what you want from a platform running autonomous agents that make outbound API calls. Every time Content Researcher ran a WebSearch or called the Claude API, those requests went out over this network connection.
I ran stress-ng across all three stressor types for 180 seconds each with 2 workers per test, matching the available core count.
CPU Stress (2 workers, 180 seconds):
Memory Stress (2 workers, 180 seconds):
Disk I/O Stress (2 workers, 180 seconds):
Zero failures across all three stressors. Every worker dispatched came back passed, and not a single result was flagged as untrustworthy.
The server held up cleanly across three minutes of sustained pressure on each subsystem, all while Paperclip and Traefik continued running in the background.
The KVM 2 plan delivers consistently strong numbers across every benchmark. The AMD EPYC 9354P core allocation scales linearly, memory throughput is fast and low-latency, disk I/O is well above what typical two-core cloud VPS plans produce, and the network delivered near-gigabit symmetrical speeds with zero packet loss.
What stands out most for the Paperclip use case specifically is not any single number but the combination of all of them under real conditions.
These benchmarks ran with Paperclip and Traefik already consuming roughly 12% of the server’s memory. The server did not buckle, did not flag untrustworthy metrics, and passed every stress test cleanly. For teams running a small to medium number of agents on a regular heartbeat schedule, the KVM 2 gives you genuine headroom.
The one practical consideration is memory. At 7.8 GiB total with around 936 MB already committed at idle, you have approximately 6.7 GiB available for agent workloads.
As your Paperclip organization grows and more agents run concurrently, that headroom will shrink. If you are planning to run a large agent team or schedule multiple agents to wake simultaneously, the KVM 4 at 16 GB RAM gives you more comfortable operating room without a dramatic price jump.
Hostinger does not run a traditional phone support line. Its primary support model is 24/7 live chat, led by Kodee, an AI assistant integrated across hPanel, the VPS dashboard, and the main website.
For anything Kodee cannot resolve, it escalates to a human agent. Hostinger also maintains a knowledge base, a tutorials library, and Hostinger Academy on YouTube for self-service support.
I tested two things: the live chat experience across both AI and human tiers, and the quality of the knowledge base.
Kodee (AI assistant)
I opened the chat and submitted my first question: how to monitor resource usage as my Paperclip agent count scales, and the safest way to upgrade plans without losing agent data and configurations.
Kodee identified my server immediately by VPS ID and gave a genuinely useful response. It did not send a generic “check your dashboard” reply. It told me exactly where to look:
It then outlined a safe upgrade path: back up the Paperclip data folder and config files, upgrade the plan, and restore only if the upgrade requires a new instance. It also offered to review my current usage numbers and recommend whether KVM 4 or KVM 8 would be more appropriate. That is a practical offer, not a scripted one.
I then asked to speak with a human. Kodee made one attempt to keep me in the AI conversation, noting that it could resolve many issues directly.
When I confirmed I wanted a human, it acknowledged the request, explained that the specialist would see the full chat history, and offered to keep helping while I waited.
I entered the queue at 6:50 PM.
Human Support
The first human agent, Ander, joined the queue at 7:16 PM, making the wait 26 minutes. By the time Ander appeared, I had already submitted my second question to the chat, which Kodee had answered in the interim.
Ander introduced himself and confirmed he was ready to help with the Docker volume migration question.
Ander stepped away shortly after joining, and the chat was handed to a second agent, Itael. The handoff was seamless from my side. Itael picked up the full context from the chat history without me repeating anything.
Itael’s response was the most technically valuable of the entire conversation. While Kodee’s answer on Docker volumes was accurate in general terms, Itael added a critical clarification specific to Hostinger’s infrastructure: on Hostinger KVM plans, upgrading from KVM 2 to KVM 4 is an in-place resource addition, not a migration to a new server.
CPU, RAM, and disk are added to the existing instance, which means Docker containers, bind mounts, and persistent volumes stay exactly where they are. No manual migration is required.
This is exactly the kind of platform-specific detail that separates a genuinely knowledgeable support agent from one reading off a general script.
Itael still recommended a manual backup as a safety net before any upgrade, and provided the specific command to compress the Paperclip data directory:
tar -czvf paperclip_backup.tar.gz /path/to/data
He also noted that after the disk resize, the new allocation can occasionally take up to two hours to reflect in the OS, and advised waiting before troubleshooting if it does not appear immediately.
The chat was eventually closed by Itael after I stepped away, with a note that I could reopen anytime and the thread would continue.
Overall chat assessment:
The Hostinger knowledge base at support.hostinger.com is organized into clearly labeled categories that cover the full range of Hostinger’s product lineup.
The depth is impressive:
The search bar at the top of the page is prominent and works well. I searched “paperclip” and got four results back, including a dedicated article titled “Hostinger VPS: Getting started with Paperclip.” The other results covered Docker Catalog applications and container deployment guides, all of which are relevant to anyone running Paperclip.
The Paperclip getting-started article itself is well structured. It walks through the full deployment and setup flow in clearly separated sections:
The article includes screenshots at each step and reflects the actual product interface rather than outdated documentation.
For a relatively new addition to Hostinger’s application catalog, having a dedicated and accurate getting started guide already published is a good sign that the knowledge base is being maintained alongside product updates.
Hostinger’s support setup works well for the majority of questions a Paperclip user is likely to ask. Kodee consistently gave specific, actionable answers rather than vague redirects, and the knowledge base has dedicated Paperclip content that is accurate and up to date.
The 26-minute wait for a human agent is the most notable limitation. For routine questions, Kodee handles things well enough that you may never need to escalate. But if you are dealing with a production issue, a failing agent deployment, or a time-sensitive upgrade, that wait matters. The agent handoff added a small layer of friction, though Itael’s technical depth once he joined was genuinely reassuring.
For a self-hosted AI orchestration platform, the level of support Hostinger provides is better than you might expect. They know the Paperclip stack, they understand Docker on their own infrastructure, and at least one of their agents understood the nuances of how KVM plan upgrades work well enough to give an answer that Kodee itself did not.
Yes. If you want to run a self-hosted AI agent organization without spending days on infrastructure setup, Hostinger Paperclip VPS delivers on that promise. Paperclip and Traefik deploy automatically with your VPS, the Docker Manager handles everything visually, and the underlying hardware holds up well under real workloads.
The KVM 2 plan gives you a functional starting point, with clear upgrade paths as your agent count grows.
The main things to go in with eyes open: the promotional pricing is attractive, but budget for the renewal rate from day one. The Claude authentication step during agent setup requires a short terminal session that first-time users may not expect. And if you need a human support agent quickly, the 26-minute wait means Kodee is your best option in a time-sensitive situation.
For developers, operations teams, and business owners looking to deploy autonomous AI workflows on infrastructure they fully control, Hostinger Paperclip VPS is a platform we would recommend.
| Description | Expert Review |
|---|---|
| Budget-friendly hosting with high performance and easy management tools. | Read Shared Hosting Review |
| Fast and secure WordPress hosting with one-click installation and premium features. | Read Wordpress Hosting Review |
| Scalable VPS hosting with dedicated resources and root access. | Read VPS Review |
| Fast, flexible cloud hosting with excellent uptime and scalable resources. | Read Cloud Hosting Review |
| Secure and private hosting solutions with offshore data center locations. | Read Offshore Hosting Review |
| Secure and reliable email hosting with professional-grade features. | Read Email Hosting Review |
| Reliable Python hosting with flexible environments for developers. | Read Python Hosting Review |
| High-performance PHP hosting with full support for dynamic websites and applications. | Read PHP Hosting Review |
| Reliable Windows VPS hosting with full control and customization options. | Read Windows VPS Review |
| Fast and flexible hosting tailored for Node.js applications with optimal performance. | Read Nodejs Hosting Review |
| Optimized hosting for WooCommerce stores with high speed and secure integration. | Read Woocommerce Hosting Review |
| Dedicated server hosting for seamless Minecraft gaming experiences. | Read Minecraft Server Hosting Review |
| Scalable hosting solutions with advanced features for digital agencies and developers | Read Agency Hosting Review |
| Fast, secure hosting optimized for Magento ecommerce websites. | Read Magento Hosting Review |
| High-performance Linux-based hosting for stable and secure website operations. | Read Linux Hosting Review |
| Robust Java hosting solutions for dynamic web applications and projects. | Read Java Hosting Review |
| Optimized hosting for ecommerce websites with secure, fast, and reliable performance. | Read Ecommerce Hosting Review |
| Reliable Django hosting with fast speeds and secure environment. | Read Django Hosting Review |
| Easy-to-use cPanel hosting with robust performance and reliable support. | Read Cpanel Hosting Review |
| Powerful hosting for businesses with fast speeds, security, and scalability. | Read Business Hosting Review |
| Easy-to-use website builder with drag-and-drop tools and customizable templates. | Read Website Builder Review |
| Optimized hosting for Joomla sites with one-click installation and reliable performan... | Read Joomla Hosting Review |
| Powerful hosting with full PostgreSQL database support for data-driven applications. | Read PostgreSQL Hosting Review |
| Flexible hosting with MongoDB integration for scalable, modern web applications. | Read MongoDB Hosting Review |
| AI-powered website creation platform for building professional sites in minutes. | Read Horizons Review |
| Reliable hosting for n8n workflow automation with easy setup and management. | Read n8n Hosting Review |
| VPS hosting with Docker support for containerized application deployment and scaling. | Read Docker VPS Review |
| Dedicated SMTP server hosting for reliable and secure email delivery. | Read SMTP Server Review |
| Fast and optimized hosting tailored for Ruby on Rails web applications. | Read Ruby on Rails Review |
| Feature-rich hosting with OpenClaw integration for building and managing claw machine... | Read OpenClaw Review |
| Fast and reliable hosting with UK-based servers for optimal local performance. | Read UK Hosting Review |
| Affordable and dependable hosting with India-based servers for low-latency access. | Read India Review |
| Read Singapore Review | |
| Read Australia Review | |
| Read AI Agent Review | |
| Read Hermes Agent Review |
Yes. All four KVM VPS plans (KVM 1 through KVM 8) support Paperclip. You select it during checkout from the OS and application selector, and it deploys automatically when your server provisions.
Yes, Hostinger offers a 30-day money-back guarantee on KVM VPS plans. One condition applies: more than 180 days must have passed since your last VPS refund. Plan upgrades and crypto payments are not eligible for refunds under any circumstance.
Not necessarily. Claude Code, the recommended adapter for Paperclip, supports both API key authentication and subscription-based login via your Claude account (Pro, Max, Team, or Enterprise). You authenticate by running claude login inside the Paperclip container terminal after deployment.
Hostinger KVM upgrades are in-place resource additions, not migrations to a new server. Your Docker containers, bind mounts, and persistent volumes stay exactly where they are. Hostinger still recommends taking a manual backup of your Paperclip data directory before any upgrade as a safety net.
Hostinger VPS is self-managed, meaning you are responsible for server configuration and maintenance. However, Kodee, Hostinger’s AI assistant, can execute many common server management tasks directly via chat, including monitoring resource usage, managing firewall rules, and handling backups, which significantly reduces the technical burden for users who are not sysadmin specialists.
Answer a few simple questions and find the perfect solution for you!
Start Hosting Search
