Guide · 26 September 2026

aiput.site vs shared hosting vs a VPS vs AWS: how hard is it to put a website online?

Your AI agent has made a website: a folder with an index.html, styles and images. There are many ways to put it online. Here are the four most common, compared by the one thing that matters most if you are not a developer — how much work each takes, the first time and afterwards.

The site in question is static: HTML, CSS, JavaScript and images. That is what AI agents produce when you ask for a landing page, and it is what aiput.site hosts.

At a glance

	aiput.site	Shared hosting	VPS	AWS
What you sign up for	One account, with Google or email	A hosting account	A cloud provider account	An AWS account with billing and access settings
Who uploads the files	Your AI agent	You, through a file manager or FTP	You, over SSH	You, through the console or the command line
Web server and HTTPS	Nothing to set up	Run by the host; HTTPS is usually a switch in the panel	You install and configure both	You assemble them from several services
Your own domain	Yes	Yes	Yes	Yes
Server-side code	No, static sites only	Usually PHP and databases	Anything	Anything
Ongoing upkeep	None	Little	Updates and security are yours	Settings and the bill need watching
First publish, if you have never done it	Minutes	About an hour	An afternoon or more	Several hours

aiput.site: the agent publishes

You sign in, choose a plan and paste one message from your dashboard into the chat with your agent. The agent connects over MCP, creates a site and uploads the files. You get an address on workers.dev with HTTPS already working. For a domain of your own, ask the agent: it finds a free name, sends you a link to pay and connects the domain to the site. Updates work the same way: you ask, the agent publishes, and earlier versions stay available for a rollback.

The key your agent receives works with your sites and nothing else. It cannot open servers or run up a bill: the number of sites is capped by your plan, the price is fixed per month, traffic is not charged, and a domain is paid for by you, through the link.

What you give up: the site has to be static. If you need a database or a shop backend, aiput.site is not the right tool.

Shared hosting: a folder on someone else's server

The classic option. You choose a hosting company, create an account, pay and get a control panel. To publish, you upload the files through the panel's file manager or an FTP client into the right folder, often called public_html. HTTPS is usually a free certificate you switch on in the panel. To use your own domain, you point its DNS records at the host.

None of this is hard, but every step is yours, and every host's panel looks different. Your agent can write the files; uploading them means either giving it your FTP password or doing it yourself. Prices are low, but first-year discounts often end with a noticeably higher renewal price — check it before you pay.

Shared hosting is a good choice when you need PHP, for example for WordPress, or email on your own domain.

VPS: your own small server

A virtual private server is a whole machine in a data centre, rented by the month. You get an IP address and root access over SSH. Everything else is up to you:

choose an operating system image and create the server;
log in over SSH, create a user, set up keys and a firewall;
install a web server such as nginx and configure it for your site;
get an HTTPS certificate, for example from Let's Encrypt with certbot, and make sure it renews;
copy the files over with scp or rsync;
point your domain's DNS at the server's IP address.

Then keep it that way: install security updates, watch the disk and the logs, renew what expires. A forgotten server does not stop working at once — it slowly becomes the easiest target on its network.

An AI agent with terminal access can do most of these steps, but it needs your SSH key, and whatever it gets wrong stays on a machine open to the whole internet. A VPS makes sense when you need to run your own code: a backend, a database, a bot. For a landing page it is a lot of machine to look after.

AWS: building blocks for everything

Amazon Web Services can host a static site cheaply and very reliably, but it gives you parts, not a product. The usual setup for a static site with HTTPS on your own domain involves:

an S3 bucket for the files;
CloudFront in front of it, because S3 website endpoints do not serve HTTPS on their own;
a certificate from AWS Certificate Manager, which for CloudFront has to be requested in the us-east-1 region;
Route 53 or another DNS provider for the domain;
IAM users, roles and policies, so that the right services can reach the bucket and nothing else can.

Each piece has its own settings, and a wrong policy can either break the site or open more than you meant to. Billing is per use — storage, requests, traffic. For a small site that is cheap, but set a budget alert: a misconfiguration or a traffic spike shows up only on the invoice.

AWS Amplify Hosting packs much of this into one service and is the easier path inside AWS. It still means an AWS account, billing and access settings.

AWS is the right tool when the website is part of a bigger system that already lives there.

Which one to choose

You have a website from your AI agent and want it online today: aiput.site. The agent does the publishing, and there is nothing to maintain.
You need PHP, for example for WordPress, or email on your own domain: shared hosting.
You need to run server code: a VPS, with time set aside to maintain it.
Your project already lives on AWS: AWS, ideally through Amplify Hosting.

For the aiput.site side step by step, see how aiput.site works.