A permanent URL for your Bolt app.
Your bolt.new preview runs in an in-browser WebContainer — it is not a permanent public address. Publish the built app to shiply.now for a permanent URL, with a real backend (database, server functions, email) your app actually needs. Flat price, no meter.
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 a Bolt preview to a permanent URL
Three steps: build the app, publish in one call, and get a live URL you can claim and keep.
Build or export from Bolt
Have Bolt run the build, then point shiply at the output — or download the project and build locally. A static build is served from the edge; an SSR build deploys as an edge worker.
Publish in one call
Publish the output 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.
Permanent, claimable URL
The call returns a live <slug>.shiply.now URL right away — not a session-bound preview. Anonymous for 24 hours; claim it with one click to keep it forever on a free account.
A permanent URL, and the backend behind it
Static-only hosts serve files. A Bolt app that needs data or auth needs more — and shiply includes it.
One call, live URL, real backend included
Publish the built app in a single call and it is live at a permanent URL. The backend a Bolt app needs 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 — never a new link.
- 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. A launch, a viral day, or a bot storm moves your traffic, 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 bolt.new projects
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, claimable URL
Not a session-bound WebContainer preview — a real <slug>.shiply.now URL you can share and then claim.
Re-publish, same URL
Publishing again updates the same site in place. Iterating on your Bolt app 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.
bolt.new is a fast way to build and iterate in the browser. shiply picks up when you want that app on a permanent URL, with a real backend, on a flat bill — not a session-bound preview.
bolt.new hosting — common questions
Does my bolt.new preview URL expire?
The URL Bolt gives you runs in an in-browser WebContainer, so it is tied to your session and not a permanent public address. When you want a URL that stays up and is yours, publish the built app to shiply.now. The first publish returns a live <slug>.shiply.now URL right away; claim it with one click to keep it forever on a free account.
Can I use a database with my Bolt app on shiply?
Yes. A Bolt app that needs data, auth, or server logic needs a real backend, and shiply includes one: Cloudflare D1 on every plan, Neon Postgres on Developer, Workers Lite edge functions for dynamic endpoints, and a per-site inbox for email. Static-only hosts serve files; shiply serves the backend your app actually needs.
How much does hosting a Bolt app cost?
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?
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.
Publish your Bolt app in one call.
No account needed. A permanent URL with a real backend, on a flat bill.