The gap between built and shipped
Agents got good at building things and stayed bad at handing them over. A folder of files on somebody's laptop is not something you can send to a person on a bus.
What it is
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.
How it is put together
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.
What is not true yet
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:
- Artifacts cannot collect visitor data. The loop that sends survey answers and tracker entries back to the agent is designed and not built.
- There is no per-artifact analytics report. Views and errors are collected and the gallery shows counts; the page that breaks them down is not there.
- There is no command-line tool. Deploying is one HTTP request, which is what the tool would wrap.
- Pricing is a placeholder. No payment exists, every account is on Free, and the numbers on the pricing page are invented.
- Custom domains, team accounts and abuse scanning are undecided.