Static hosting on VM0
Publish what an agent built to a real link anyone can open, with every version kept.
Runtime · No setup · No per-call charge; included in the run
An agent that builds a report, a dashboard or a deck still has to hand it over. The file sits somewhere nobody can reach, which is not the same as being finished.
Publishing turns it into a link anyone can open, on a phone or a laptop, with no account of yours behind it. Every publish is kept, so you can see what was sent when, and pull a version back to change one thing instead of rebuilding it.
What Static hosting is
The gap between an agent finishing something and a person being able to look at it is bigger than it sounds. A file on the agent's disk is not something you can send to anyone.
Publishing takes the finished thing and puts it at a link. Single-page apps work properly, and an HTML deck can be published as a presentation so it opens as one.
Publishing again does not overwrite anything. Each publish is kept as its own version at the same link, you can see the history, and you can pull a version back down to edit and republish it.
The same job people describe as static site hosting, publishing HTML to a URL, or finding something simpler than a deploy pipeline for one page. There is no account, no token and no build step here: what the agent produced becomes a link at the end of the run.
What Static hosting can do
What an agent can do with it, and what comes back when it does.
Coverage and limits
What it does not do, said up front, so nobody plans a workflow around something that is out of scope.
Finished pages, not running software
It serves the pages and files the agent built. Anything that needs a server, a database or a queue behind it belongs on your own platform.
Links are public
Anyone with the link can open it. That is right for sharing a report and wrong for anything confidential.
Nothing is overwritten
Publishing again adds a version rather than replacing one, which makes the history reliable. A mistake is corrected by publishing a fix, not by editing what already went out.
Images have to be real files
Pictures embedded directly into the page are not reliable here. They should be real files published alongside it, and worth checking on the published link rather than locally.
What Static hosting costs
Web services are billed in credits per call, not per token. There is no separate vendor bill to reconcile.
zero hostThere is no charge for publishing. It comes with the run, so the cost is the work of building the thing rather than a fee per publish or per visitor.
Setup and access
Nothing to set up
Nothing to connect. No hosting account, no tokens, no deploy pipeline, no DNS. What the agent built plus a name for the site is the whole thing.
Who can use it
Publishing comes with the run, so what matters is what goes into it. A published link is public, so anything confidential should be delivered another way.
What teams use Static hosting for
Delivering a report someone will actually read
A quarterly summary, an audit or an analysis becomes a link that opens on a phone, instead of a file that lands in a folder nobody visits.
Sharing a prototype
A landing page or interface concept an agent built becomes a real link you can send for feedback, republished each time it changes, with the earlier versions still there.
Presentations that stay current
A deck published as a link is something you can send, reopen and update, rather than a file emailed around in four slightly different versions.
When not to use Static hosting
Skip it for anything that needs a server, a database or a framework running behind it, and use your own platform instead. Skip it for confidential material, because published links are public. And skip it when what somebody asked for is the file itself.
What this is called elsewhere
The same thing goes by several names in the market. If you have shopped for one of these, this is how it maps to what you get here.
Static site hosting
Serving finished pages and files at a URL. That is what this is, with no account, no build configuration and no per-visitor cost.
Publishing HTML to a URL
The plainest version of the job: a page exists, and now it has an address someone can open on their phone.
A deploy pipeline you do not set up
Netlify, Vercel and a bucket behind a CDN all do this well and all need an account, a token and a project. Here it happens inside the run.
Sharing a report link
Why most people use it. A link updates in place and keeps every earlier version, which beats emailing a file that goes stale immediately.
Single-page app hosting
Apps with their own client-side navigation work properly, so a dashboard an agent built behaves the way it did locally.
Static hosting compared
Static hosting vs a hosting provider you set up
Netlify, Vercel or a bucket behind a CDN are all excellent and all need an account, a token, a project and a deploy step. This is one step with no account, which is the right trade when the thing being shared is a report rather than a product.
Static hosting vs sending the file
A file is a copy that goes stale the moment anything changes. A link updates in place and keeps every earlier version, which is usually what you want for a recurring report.
Static hosting vs a preview only the agent can see
A server running inside the agent's own environment is useful for the agent to check its work and unreachable for everybody else. Publishing is what makes the result something a person can open.
The short version
The difference between an agent finishing a job and somebody being able to see it. Finished pages only, public links, every version kept.
Frequently asked questions
Do I need a hosting account?
No. Publishing happens inside the run. There is no provider account, token or deploy pipeline on your side.
Can I host an app with a backend?
No. It serves the pages and files the agent built. Anything needing a server, a database or a framework running behind it belongs on your own platform.
Is a published link public?
Yes. Anyone with the link can open it, so it is right for a shareable report and wrong for confidential material.
What happens when I publish again?
It becomes a new version at the same link, and the previous ones are kept. You can see the history and pull a version back down to edit.
Do single-page apps work?
Yes. Client-side routes resolve properly, so an app with its own navigation behaves as it should.
Why do my images break?
Pictures embedded directly into the page are not reliable here. They should be published as real files alongside the page, and checked on the published link.
Is this an alternative to Netlify or Vercel?
For publishing something an agent produced, yes, and it needs no account, token or project. For running a product, no: those platforms do builds, functions and custom domains, and this serves finished pages.
Can I publish a single HTML file?
Yes, along with the images and files it needs. Pictures embedded directly into the page are the one thing that does not travel reliably, so they should be real files published alongside it.
Is publishing free?
There is no charge for publishing and no per-visitor fee. It comes with the run, so what you pay for is the work of building the thing.
Can I use my own domain?
Published sites live on a VM0 address. Anything that needs your own domain, or a login in front of it, belongs on your own platform.
How you ask for Static hosting
You describe what you want in plain language. The agent works out which service it needs and makes the calls.
“Build a one-page summary of this quarter's results and publish it so I can share the link.”
“Turn this concept into a page, publish it, and send me the link for feedback.”
“Change the headline on the report you published yesterday and republish it at the same link.”