Pay when it earns it
Start free and stay free if that is enough. Solo adds live data and lets you serve without our header, with 14 days to decide.
This deployment has no payment configuration, so nothing on it can be bought. The prices are real; this copy of the site cannot take one.
What each plan includes
Every limit here is enforced. Nothing is listed that the product does not already refuse.
| Capability | Free | Solo | BusinessComing soon | EnterpriseComing soon |
|---|---|---|---|---|
| What you can build | ||||
| Artifacts | 100 | 1,000 | Unlimited | Unlimited |
| Versions kept | 100 | 2,000 | Unlimited | Unlimited |
| Storage | 250 MB | 5 GB | Unlimited | Unlimited |
| Collections | 2 | Unlimited | Unlimited | Unlimited |
| Workspaces | 2 | Unlimited | Unlimited | Unlimited |
| Serving and sharing | ||||
| Views and bandwidth | Unlimited | Unlimited | Unlimited | Unlimited |
| Private by default | Included | Included | Included | Included |
| Serve without the Super Artifacts header | Not included | Included | Not decided yet | Not decided yet |
| Custom social share previews | Not included | Included | Not decided yet | Not decided yet |
| Live and data | ||||
| Open a live room | Included | Included | Not decided yet | Not decided yet |
| People in one live room | 10 at once | 200 at once | Unlimited | Unlimited |
| The marketplace | ||||
| Install a blueprint | Included | Included | Included | Included |
| Publish a blueprint | Not included | Included | Not decided yet | Not decided yet |
How billing works
$19a month
- Charged
- Every month, on the day you subscribe.
- Over a year
- $228
- Works out at
- $19 a month
- If you cancel
- Solo runs to the end of the month you have paid for.
$190a year
- Charged
- Once, on the day you subscribe.
- Over a year
- $190
- Works out at
- $15.83 a month
- If you cancel
- Solo runs to the end of the year you have paid for.
Annual is $38 less over a year — two months free.
Both include the 14-day trial and exactly the same Solo features. You can switch between them in the billing portal, and Stripe prorates whatever you have already paid.
What is actually true today
- Solo is real and chargeable. Card details go to Stripe and never touch our servers; the subscription belongs to a workspace, not to a person, and every member of that workspace gets its capabilities.
- Business is not built. There is no product, no price and no way to be put on it, which is why the card carries no number. It is shown because it will be the self-serve tier when it exists, and hiding the name of a tier people ask for is how a pricing page ends up answering a question nobody asked.
- The limits printed on the cards are enforced. Passing the artifact or storage cap refuses the next deploy with a message naming what to delete or upgrade; everything already published keeps serving and can still be redeployed.
- Custom domains are still not built. They are no longer listed as a Solo feature for that reason.
Cancelling keeps Solo until the end of the period you have already paid for, and a failed payment does not switch anything off while Stripe is still retrying it.
Start on Free
Frequently asked questions
Something your agent builds and deploys to a URL people open — a tracker, a survey, a playlist. Not a transcript you have to explain, and not a code block somebody has to run: a page.
Those render something in a window you look at. A super artifact is deployed at a URL with a database behind it, so real people can open it on their phones, use it, and have what they typed flow back to the agent that built it. It is the same idea, plus the half those tools stop at: the data loop.
One MCP URL. Point the harness at it —
claude mcp add --transport http super-artifacts https://api.superart.page/mcp— the harness offers a Connect button, the consent screen names the account, and the key stays in the harness where you can revoke it.Into a database that comes with the artifact. What the artifact may collect and who may read it is a policy the deploy declares, enforced per row: an artifact that says a visitor reads only their own entries cannot hand them anybody else’s, and an artifact marked private serves nothing to somebody who has not been named.
Erasing a visitor erases their rows on both the serving plane and in the database, and deleting an artifact closes the whole surface behind it.
No. Every byte comes out of your agent’s model, on your tokens, in your environment. There is no endpoint here that takes a prompt and returns a page, and there is not going to be one — an agent that expects the platform to generate the artifact will post a prompt and get back an empty page.
There is no per-artifact analytics report yet — the view and error pipelines are live and the gallery shows counts, but the page that breaks them down is not built. There is no
supercommand-line tool, only the HTTP endpoint it would wrap. Custom domains are not built either, which is why they are not listed as a Solo feature.