AI Artifacts & Generated Sites

Artifact Hosting

Definition

The phrase covers a small, specific job: taking generated output that currently renders in a chat panel and serving it as an ordinary web page. Because assistants tend to produce self-contained pages, with the CSS and JavaScript written into the same file, the job is closer to uploading a photo than to deploying an application. There is no repository to connect, no build to configure and no runtime to choose. What you need from the host is narrow: it should serve HTML over HTTPS at a stable address, let you replace the file when the next version is better, and not mangle the file on the way in. Anything beyond that — a database, scheduled jobs, server-side rendering — is not artifact hosting, and a static host will not do it.

Why It Matters

Hosting is what turns a demo into a thing people use. A prototype seen only over a screen share gets polite nods; the same prototype at a link gets opened at midnight by someone who then tells you what is wrong with it. The practical difference is measured in friction: a chat panel needs an account, a session and your presence, while a URL needs none of the three. There is a versioning benefit as well. If the host keeps previous uploads, you can publish the fifth iteration in the morning and roll back to the fourth by lunchtime without asking the assistant to rebuild anything.

How It Works

You save the artifact's source as index.html, upload it, and the host writes it to storage behind a CDN and answers requests for your address with those bytes and a Content-Type of text/html. Nothing runs on the server: every button, chart and animation is executed by the visitor's browser, which is exactly how the artifact behaved in the chat panel. Assets the page refers to — an image, a font, a second script — either travel with it as extra files, are inlined as data URIs, or are loaded from a public CDN. Replacing the page later is another upload to the same name, and a host with file versioning keeps the old copy so a bad change can be undone. Password protection, if the host offers it, sits in front of the page for work that should not be indexed or shared onward.

Real-World Example

A designer generates an interactive style guide — colour swatches, type scale, a contrast checker — and ends up with a single 260 KB file. Uploaded to 99helpers under the name lumen-styleguide, it answers at lumen-styleguide.99helpers.site, and the whole team has it bookmarked by the afternoon. Two days later she publishes a revised version over the same name; everybody's bookmark still works, and the previous upload stays available to roll back to.

Common Mistakes

  • Picking a host that needs a repository and a build for a file that needs neither — the setup takes longer than the thing being published and breaks every time a dependency moves
  • Publishing a page that calls a paid API with the key written into the script — it works for a day, then someone views source and the bill stops being yours to predict
  • Uploading under a new name for each revision — the link you already sent goes stale, and nobody knows which of the five addresses is current
  • Forgetting that a static host cannot store what visitors type — form entries vanish unless the page posts them somewhere that does run code

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →