Pay for the people who build. Everyone else reads free.
A seat is a person who connects an agent and publishes. Viewers, commenters and the agents themselves are never seats, and limits are pooled across the workspace.
Team3–25 builders
5 seats included, then $8 a seat a month.
Builders3–25 on Team- Team, 5 seats included
- $39
- Total a month
- $39 / month
- Both sizes
- Pooled limits across the workspace
- "Anyone at your workspace" as an audience
- A private team template shelf
- Removing someone revokes their agents
- Unlimited artifacts and versions
- Team adds
- Pay by card, cancel any time
- Seats follow membership, prorated
- Only on Business
- Audit log, kept a year, exportable
- Admin policies: sharing, approval, default roles
- Yearly by invoice or purchase order, net 30
- Domain capture: colleagues find the workspace
- 500 GB pooled storage
Viewers are free and unlimited. Only people who publish use a seat.
SSO and SCIM are not built yet. Enterprise is where that conversation happens.
What each plan includes
Every limit here is enforced. Nothing is listed that the product does not already refuse.
| Capability | Free | Solo | Team | Business | EnterpriseComing soon |
|---|---|---|---|---|---|
| What you can build | |||||
| Artifacts | 100 | 1,000 | Unlimited | Unlimited | Unlimited |
| Versions kept | 100 | 2,000 | Unlimited | Unlimited | Unlimited |
| Storage | 250 MB | 5 GB | 50 GB | 500 GB | Unlimited |
| Collections | 2 | Unlimited | Unlimited | Unlimited | Unlimited |
| Workspaces | 2 | Unlimited | Unlimited | Unlimited | Unlimited |
| Serving and sharing | |||||
| Views and bandwidth | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
| Private by default | Included | Included | Included | Included | Included |
| Serve without the Super Artifacts header | Not included | Included | Included | Included | Not decided yet |
| Custom social share previews | Not included | Included | Included | Included | Not decided yet |
| Live and data | |||||
| Open a live room | Included | Included | Included | Included | Not decided yet |
| People in one live room | 10 at once | 200 at once | 500 at once | 500 at once | Unlimited |
| The marketplace | |||||
| Install a blueprint | Included | Included | Included | Included | Included |
| Publish a blueprint | Not included | Included | Included | Included | Not decided yet |
Cheaper than building it
An internal equivalent — hosting, access control, a data layer, an MCP server, live rooms — is 2 to 8 engineer-months to build and 15–25% of that a year to keep. Estimates, from public salary data.
- Team, 5 seats, a year
- $390
- 0.4% of a base-case build year.
- Team, 25 seats, a year
- $1,990
- 2% of a base-case build year.
- Business, 100 seats, a year
- $10,490
- About $8.74 a seat a month. 11% of a base-case build year.
How billing works
$20a month
- Charged
- Every month, on the day you subscribe.
- Over a year
- $240
- Works out at
- $20 a month
- If you cancel
- Solo runs to the end of the month you have paid for.
$200a year
- Charged
- Once, on the day you subscribe.
- Over a year
- $200
- Works out at
- $16.67 a month
- If you cancel
- Solo runs to the end of the year you have paid for.
Annual is $40 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. Team and Business follow the same two intervals, and the annual rate locks the year it pays for.
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.
- Team and Business are real and chargeable. The pricing cards carry the launch prices, the Team card does the seat arithmetic for whatever number you type, and the first workspaces to subscribe keep that price for 24 months. Viewers are free and unlimited; only people who publish use a seat. Plans and pricing has the plain-language version.
- 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.
- SSO and SCIM are not built. Enterprise is where that conversation happens. Custom domains are still not built either, and are not listed as a feature for that reason.
Cancelling keeps your plan 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.