INFRASTRUCTURE & OWNERSHIP

The order has to
land somewhere.

When an AI agent completes a purchase on a customer's behalf, that transaction request goes to a server. That server either belongs to you — or it belongs to someone else, and so does the transaction. This is not a philosophical position. It is the specific, measurable reason agentic commerce requires a VPS.

By Sid Ratnam · April 2026 · 6 min read

The transaction architecture

When ChatGPT's Operator places an order on a customer's behalf, the sequence is precise: it reads the store's ACP discovery file, identifies the purchase endpoint, sends a structured purchase request to that endpoint, and waits for a response from your backend. That backend processes the order, charges the customer through your Stripe account, and returns a confirmation.

Every part of that chain that runs on infrastructure you don't control is a part of your commerce operation you don't own. The discovery file can be yours. The purchase endpoint must be yours. The backend that processes the transaction must be yours. If any of those live on a SaaS platform — a managed service, a third-party tool, a vendor's server — the arrangement is a rental. Access-based. Conditional. Revocable.

A VPS — a Virtual Private Server — is a server you rent from a hosting provider (Hostinger, GoDaddy, DigitalOcean, Vultr, SiteGround, Linode, and others) 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.

What VPS ownership actually means in practice

The practical implications of infrastructure you control:

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
Your ACP discovery file and agent purchase endpoint are hosted on your server — not managed by a third-party platform that can revoke access

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.

Server hardware with dramatic moody lighting — owned infrastructure, golden highlights on dark — Your VPS — the fixed-cost foundation where agents run on your terms, not a vendor's pricing schedule

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.

For the full structural argument on why renting your commerce infrastructure is a long-term liability — with a worked example across commerce, payments, and content — see Proposal №002: Stop Renting Your Commerce.

A cinematic balance scale tipping toward ownership — the break-even point where owned infrastructure outperforms SaaS rental costs — Break-even at 12–25 months depending on SaaS spend — after that, $20/month is the only overhead

Every major VPS provider works — here is the full list

The agent stack deploys to any VPS with root access and at least 2GB RAM. That covers the full range of providers store owners are already running on:

Hostinger VPS — the most common starting point. KVM plans from $10–20/month include managed options. Hostinger agentic commerce deployments are the most frequent setup in this build.
GoDaddy VPS — widely used by store owners who already manage their domain through GoDaddy. GoDaddy VPS plans with root access are fully compatible.
DigitalOcean — popular with developers and technical store owners. DigitalOcean Droplets in the $12–24/month range are a clean, well-documented starting point.
Vultr — reliable, straightforward pricing, multiple data center locations. Vultr Cloud Compute instances deploy the agent stack without modification.
Contabo VPS — strong value for stores that want more RAM and storage at lower cost. Contabo's generous specs make it a good fit for Full Suite deployments.
SiteGround VPS — familiar to WooCommerce and WordPress store owners. SiteGround managed VPS plans reduce configuration overhead.
Bluehost VPS — a common choice for store owners who started with shared hosting and want to step up. Bluehost VPS plans with root access are compatible.
A2 Hosting VPS — known for speed optimization. A2 Hosting VPS plans work cleanly for agent deployments.
Namecheap VPS — straightforward and affordable. Namecheap VPS plans with root access meet the minimum requirements for Foundation builds.
Hetzner Cloud — popular in Europe, excellent price-to-performance. Hetzner agentic commerce builds are a strong choice for stores with European customer bases.
Linode / Akamai Cloud — developer-friendly, reliable infrastructure. Linode plans in the $12–24/month range are a common choice for agent builds.
OVHcloud VPS — European alternative with strong data residency positioning. OVHcloud VPS plans with root access work for the full agent stack.

The only hard requirement: root access and at least 2GB RAM. If your VPS meets those specs — on any provider — the build deploys to it.

ACP compliance requires a purchase endpoint hosted on infrastructure you control. A SaaS-hosted store cannot own that endpoint. A VPS you control can. Google's AP2 (Agent Payments Protocol) follows the same model: a server-side endpoint your infrastructure exposes. Stores that own their VPS today will be AP2-ready when the protocol ships.

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.

READY TO OWN YOUR STACK

Built on infrastructure
you control.

Foundation at $5,000 — no payment until your agents are live and working. Full Suite at $20,000 · Both Together at $25,000. Applications take 10 minutes.

Apply for a build → ← Back to Agentic Commerce overview