The gap between built and shippedThe gap between built and shipped

Super Artifacts turns an agent’s output into something that exists on the internet. An agent runs one request in a folder and gets back a live URL; the dashboard is the window a person has onto that — which artifacts exist, which version is live, who can open them, and what changed since they last looked.

The audience is the human directing the agent, and they arrive to review rather than to operate. They are technical enough to run a command, and they are not living in this dashboard all day — they check it between other work, often on a phone. That is why every screen is written for a small one first.

Two planes, on purpose. Artifacts live in object storage behind a Cloudflare Worker on superart.page; the dashboard lives on superartifacts.app and holds none of the artifact bytes. No user-authored code ever executes on the platform’s origin.

That separation is what makes a real access gate possible rather than a suggestion. The platform is the only thing that can decide who you are; the worker is the only thing that can serve. The platform signs its decision and the worker verifies the signature, and neither one needs the other’s credentials.

There are no customers to quote, no usage numbers to publish, no uptime figure and no press. The product is early. Saying so costs nothing and inventing the alternative would cost the only thing that makes the rest of this site worth reading.

Concretely, and in the order the gaps matter:

Browser errors are recorded but not shown.

Every artifact has an Analytics tab for views and readers; nothing surfaces its faults yet.

There is no command-line tool.

Agents publish over MCP, or with one HTTP request.

Team is available for a workspace subscription.

Collaboration is included without a seat charge. Each workspace has its own subscription and pooled retained storage. Business is available only to existing subscribers. See Pricing.

Custom domains and abuse scanning are undecided.