A decade ago, an "artifact" meant a Figma export, a build output, maybe a PDF a client was waiting on. The hosting question was boring: drop it on S3, or a static host, or - if it was Friday and nobody was looking - WeTransfer.
That definition has quietly stopped making sense.
These days an artifact is whatever your agent just made. A landing page Lovable spat out. A Claude artifact that lives inside a chat window and dies when you close the tab - the kind of thing you'd want to publish a Claude artifact somewhere with an actual URL before the conversation rolls off. A v0 prototype your PM wants to look at before the sprint review. A Framer draft a designer wants to send to a client without exposing the whole project. The artifact is no longer something a human exported - it's something a model produced, often several of, and somebody needs to put a URL on it in the next ninety seconds.
Hostsmith exists because the hosting layer never caught up with that change, and because the category that's best described as artifact hosting didn't really exist as a named thing.
The handoff is where everything cracks
The surprising thing about the agentic shift isn't the generation step. The models are fine. The models are ridiculous. The bit that breaks is the handoff.
You've got a thing. You need a URL. The URL needs to:
- sit on a sensible domain, not a random hash on preview.platform.dev
- gate behind a password, because the client hasn't paid yet and the work shouldn't leak
- carry your branding, not somebody else's
- ideally let the recipient leave a comment without spinning up a Figma seat
And the bill for stitching that together adds up fast. On Vercel you take the Pro plan and bolt on Advanced Deployment Protection just to get the password bit. Webflow puts its site password gate behind its paid plans. Tiiny Host will do password but doesn't really do the rest. Cloudflare Access will gate things on its free tier, but it's a Zero Trust access product built for guarding your own apps - a lot of machinery to stand up just to hand a client a preview link. With Netlify you hand-wire Basic Auth into a _headers file and hope nobody fat-fingers it.
So you end up paying three vendors, owning four dashboards, and still doing the bit where you DM the client a password in a separate channel. For one artifact. The pattern is familiar - people were setting up gated client preview URLs with .htaccess files in 2003, and twenty-plus years later the experience hasn't materially improved.
What "agentic-first" actually means
The question we kept circling when sketching Hostsmith was a stubborn one. If a designer drags a ZIP onto a browser, and an agent pushes the same bytes through an MCP call thirty seconds later, why should those two paths feel like different products? Same file, same URL shape, same gating, same domain logic, same bill at the end of the month. The platform shouldn't notice - and certainly shouldn't charge differently - just because the actor at the keyboard happens to be a model.
That sounds obvious until you try to build it on a stack that assumes a human is the actor. A lot of hosting platforms still expect you to click through three screens to attach a custom domain, paste a verification record, wait for DNS, then go back and toggle password protection in a different menu. That's fine when you ship a site a month. It's not fine when an agent is producing artifacts faster than you can name them.
So Hostsmith leans the other way:
- One job: give it a file or a folder, get back a live URL.
- One MCP server that exposes that job to whatever agent you're driving - Claude, Cursor, your own scripts. (Worth flagging: Hostsmith ships an MCP server you call to publish. We don't host third-party MCP servers or running agents - that's a separate planned product, not what's live today.)
- Private Sites - password or email whitelist - included from the Pro plan, not buried behind enterprise sales. The email whitelist is the part the simple file hosts skip: the client gets a magic link to their address and nobody has to DM a password anywhere.
- Custom domains on the same job, attachable to any resource.
- Optional architectural EU residency on the higher tiers, for teams that actually need it - not a DPF/SCC sticking plaster bolted on at the perimeter.
The bit that took the most work is the boring bit: a designer using Framer and a developer hitting it from an MCP client end up at the same URL shape, with the same gating, on the same plan. The platform doesn't care which one of them was an agent.
Why this matters even if you don't think you're "agentic"
Here's an unscientific test worth running on yourself: pull up your last five working days and count how many artifacts started in or passed through a model. On a typical working week now, four out of five tend to have an LLM in the loop somewhere - a Claude-generated comparison page, a Lovable mock that needs a private link, a Cursor-built CLI demo with a docs page. None of them need a CMS. All of them need the same handoff: gated URL, sensible domain, no faff.
If you run that audit honestly, you'll probably land somewhere similar. The "agentic" workflow isn't a future thing you opt into - it's the default for anyone shipping client work, demos, prototypes, or content right now. The hosting layer is just lagging.
Where we're aiming next
Hostsmith is currently focused on the part of this story where it hurts most acutely: freelance designers shipping client previews from AI builders. Today the loop looks roughly like this. A designer finishes a Framer draft that Lovable or v0 helped them rough in. They want it gated at a custom subdomain - acme-preview.theirstudio.com, say - with an email whitelist so only the two people at the client can open it. With Hostsmith that's one MCP call from inside Claude, or three clicks from the dashboard, and the link lands in the client's inbox in under a minute. No password DM, no shared Google login, no enterprise quote.
Get that one workflow right and the same plumbing covers every other agent-made artifact you can throw at it: the v0 prototype, the Bolt.new draft, the Cursor-built CLI demo's docs page, the ZIP a colleague sent that needs to be behind a URL by lunchtime.
If any of that friction sounds familiar - or if you're an agent author looking for somewhere sensible to drop the static artifacts your agents produce - Hostsmith is at hostsmith.net, and the MCP server is one config block away from whatever agent you're driving.