Why does agentic commerce
require a VPS?

The ownership problem with SaaS-hosted AI

When an AI tool runs on a SaaS platform's infrastructure, the arrangement is a rental. You pay a monthly fee. The tool runs on their servers. Your customer data passes through their systems. If they raise prices, deprecate a feature, change their terms of service, or shut down, the capability you built your operations around disappears. The agents are not yours — they are access rights to someone else's agents, and access rights can be revoked.

This is not a hypothetical risk. Klaviyo has raised prices every year for the past three years. Drip was acquired and gutted. Mailchimp has degraded its feature set while increasing costs. Every SaaS tool in the commerce stack is an ongoing negotiation between you and the vendor about what access costs. Agents that run on your own VPS are not part of that negotiation.

What VPS ownership actually means in practice

A VPS — Virtual Private Server — is a server you rent from a hosting provider (Hostinger, DigitalOcean, Linode, etc.) where you have root access and full control over what runs on it. Your agents live there. Your customer data stays there. The code that powers the agents is in your repository, not locked in a vendor's proprietary format.

The practical implications:

• You can modify the agents at any time — extend them, retrain them, redirect them
• You can hire any developer to maintain or extend the code
• There is no per-action pricing, no usage tier, no "you've hit your monthly limit"
• Your customer behavioral data does not leave your infrastructure
• If the original builder is unavailable, the code still runs and someone else can pick it up

For a store doing $30,000/month, the operational agents might make 10,000 decisions per month — surfacing recommendations, sending recovery messages, instrumenting checkout sessions. On a usage-based SaaS platform, 10,000 agent actions per month is a line item that compounds as the business grows. On a VPS you own, it is a fixed infrastructure cost that does not change as volume increases.

What a VPS does not require from you

You do not need to be a systems administrator. You do not need to understand Linux internals, configure firewalls from scratch, or write deployment scripts. The build includes deployment — the agents get set up, configured, and running before handoff. What you need is access to a server with root credentials, and someone technical enough to restart a process if something breaks. That is all.

Hostinger's VPS plans at $10–20/month are configured by their support team on request and come with managed options that handle OS updates, backups, and basic monitoring. For the vast majority of commerce stores in the $10k–$100k/month revenue range, a $20/month VPS with managed hosting is the right starting point.

The cost comparison is not close

A typical SaaS stack for cart recovery, recommendations, and post-purchase automation runs $500–$2,000/month for a store doing $30k/month in revenue. At $1,000/month over 24 months, that is $24,000 in access fees — and at the end of 24 months, you own nothing. The agents are still rented.

A custom agent build at $25,000 + $20/month VPS costs $25,480 over 24 months — and at the end of 24 months, you own working code that will continue to run for as long as you want it to. The break-even point against a $1,000/month SaaS stack is 25 months. Against a $2,000/month SaaS stack, it is 12 months.

Infrastructure you own compounds in your favor over time. Infrastructure you rent compounds in the vendor's favor. The VPS requirement is not a barrier to the build — it is the mechanism that makes ownership real.

Getting a VPS before the build starts

If you do not have a VPS yet, the setup takes about 30 minutes. Hostinger's VPS plans work well for this use case and their support is responsive for initial configuration. You need a VPS with at least 2GB RAM, 50GB storage, and root access before the build can begin — these are entry-level specs that most $10/month plans meet.

The application for agentic commerce asks whether you have a VPS and its current specs. If you do not have one yet, the application is still worth submitting — the VPS can be set up in the period between application approval and build start.