Turn a Claude artifact into a real URL.
A Claude artifact is a preview inside the chat — not a public site you can hand someone a link to. Publish it to shiply.now for a real, permanent, shareable URL — with a backend (database, functions, email) — in one call. Flat price, no meter, no account to start.
Publish my site to shiply.now and give me the live URL. Read https://shiply.now/skill.md first — it is the live API map. Before publishing, look for .shiply.json and existing Shiply credentials; if MCP is connected, call whoami. If no valid credential is available, publish anonymously immediately — never block the first live URL. Then show me Shiply’s REAUTH_REQUIRED verification link so I can claim it. If I choose email reconnect, request the six-digit code, wait for me to paste it, verify it, and securely save the returned API key. In a cloud sandbox, use the raw HTTP API only (no npm or install scripts). Follow Shiply’s JSON errors and docs pointer; don’t guess.
From an artifact to a shareable URL
Three steps: take the artifact, publish in one call, and get a live URL you can share and claim.
Take the artifact out of chat
Copy the artifact's files, or have Claude write them to a directory. shiply runs the output — a plain HTML or static build is served from the edge, an SSR build deploys as an edge worker.
Publish in one call
Publish in a single call — over MCP at shiply.now/mcp, the CLI (shiply publish ./dir), or a raw POST to /api/v1/publish. No account to create first, no build pipeline to wire up.
Real, shareable URL
The call returns a live <slug>.shiply.now URL anyone can open — not a preview locked to your chat. Anonymous for 24 hours; claim it with one click to keep it forever.
A shareable URL, and a backend when you need one
A simple artifact ships as static files. One that grows past markup needs a backend — and shiply includes it.
One call, live URL, real backend included
Publish the artifact in a single call and it is live at a real URL anyone can open. When it grows past static markup, the backend comes with it: Cloudflare D1 on every plan, Neon Postgres on Developer, Workers Lite edge functions, and a per-site inbox for email. Re-publishing updates the same slug.
- One call: MCP, CLI (shiply publish ./dir), or POST /api/v1/publish
- Real databases: D1 on every plan, Neon Postgres on Developer
- Edge functions and per-site email, on the same URL
Flat price, no surprise bill
Flat $0 / $8 / $24 a month with no usage meter. If an artifact you shared takes off, your traffic moves — not your invoice. The backend, the custom domain, and the SSL are all part of the flat plan — nothing metered on the side.
- Flat $0 / $8 / $24 a month — no meter
- Custom domains with DNS and SSL provisioned for you
- Backend included, not billed per request
Why shiply for Claude artifacts
The backend items are the difference from static-only hosts — real data, functions, and email, on a flat bill.
No account to start
The first publish needs no sign-up. You get a live URL instantly, valid for 24 hours, claimable to keep forever.
Flat price
Flat $0 / $8 / $24 a month with no usage meter. The number on the card is the number you pay.
A real, shareable URL
Not a preview locked to your chat — a real <slug>.shiply.now URL anyone can open, and you can claim.
Re-publish, same URL
Publishing again updates the same site in place. Iterating on the artifact never spawns dead URLs.
Custom domains
Point your own domain at any site. DNS is provisioned through Cloudflare and SSL is issued for you.
Real databases
Cloudflare D1 on every plan, with Neon Postgres on Developer — real data, not just static files.
Edge functions
Add Workers Lite functions for dynamic endpoints that run at the edge. No server to provision or keep running.
Per-site email
Every site gets its own inbox for form posts and contact email — no third-party service to wire up.
Claude Artifacts are a great place to build and preview something live in the chat. shiply picks up when you want to share it as a real URL, with a backend behind it, on a flat bill.
Claude Artifacts hosting — common questions
Can I share a Claude artifact as a real website?
A Claude artifact renders inside the chat — it is a preview, not a public site you can hand someone a URL for. To share it as a real website, publish the artifact to shiply.now. The first publish returns a live <slug>.shiply.now URL you can send anyone; claim it in one click to keep it forever on a free account.
Can I use a database with a published artifact on shiply?
Yes. If your artifact grows past static markup — it needs data, a form, auth, or server logic — shiply includes a real backend: Cloudflare D1 on every plan, Neon Postgres on Developer, Workers Lite edge functions, and a per-site inbox for email. Static-only hosts serve files; shiply serves the backend the app needs.
How much does it cost to publish a Claude artifact?
Flat $0 on Free, $8 a month on Hobby, or $24 a month on Developer — no usage meter. A viral day moves your traffic, not your invoice. The price on the card is the price you pay whether the site gets ten visitors or ten thousand on its best day.
Do I need an account to publish an artifact?
No. The first publish needs no sign-up — you get a live URL instantly, valid for 24 hours, claimable with one click to keep forever. Publish over MCP at shiply.now/mcp, the CLI (npm i -g shiply-cli, then shiply publish ./dir), or a raw POST to /api/v1/publish.
Share your Claude artifact as a real URL.
No account needed. A permanent, shareable URL with a real backend, on a flat bill.