Move your Replit app to a permanent URL on a flat bill.
Take the app you built on Replit to a permanent URL, with a real backend (database, functions, email) — on a flat, predictable bill. No credits, no cold sleep on the URL, no account to start. Publish in a single call and re-publishing updates the same URL.
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 Replit to a permanent URL
Three steps. Build it, then publish the output to a permanent home on a flat bill.
Connect or paste
Add the shiply MCP server at https://shiply.now/mcp, or paste the publish prompt into the agent you use to run the build.
Publish the build output
Run the build, then publish the output in one call — via the publish_site MCP tool, the shiply CLI, or a raw POST to /api/v1/publish.
A permanent, claimable URL
The first publish returns a live <slug>.shiply.now URL instantly. Anonymous for 24 hours, claimable in one click, and re-publishing updates the same slug.
Flat and predictable — with a backend that stays on
Replit deployments are usage-priced. shiply is a flat bill with a real backend, in the same one call.
No credits, no cold sleep on the URL
shiply is flat and predictable: $0 on Free, $8 a month on Hobby, $24 a month on Developer, with no usage meter. There are no credits to buy or burn, and the URL does not cold-sleep — the price on the card is the price you pay whether the app gets ten visitors or ten thousand.
- Flat $0 / $8 / $24 per month — no usage meter
- No credits to buy or burn
- No cold sleep on the URL — served from Cloudflare
A real backend, not just files
Static-only hosts stop at files. shiply gives the moved app a Cloudflare D1 database on every plan, Neon Postgres on Developer, Workers Lite edge functions, and a per-site inbox for email. Publish once (npm i -g shiply-cli, then shiply publish ./dir, or a raw POST /api/v1/publish) and re-publishing updates the same URL.
- D1 on every plan, Neon Postgres on Developer
- Workers Lite functions and a per-site inbox
- Re-publishing updates the same URL — never a new one
Why shiply for Replit projects
A flat bill and a real backend — real, factual, on the plans below.
Real databases
Cloudflare D1 on every plan, with Neon Postgres on Developer — real SQL data, not just static files.
Edge functions
Workers Lite functions run dynamic endpoints at the edge. No server to provision or keep running.
Per-site inbox email
Every site gets its own inbox, so a form or contact endpoint can receive email without a third-party service.
Custom domains
Point your own domain at any site. DNS is provisioned through Cloudflare and SSL is issued for you.
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, no credits
Flat $0 / $8 / $24 a month with no usage meter and no credits. A viral day moves your traffic, not your invoice.
Re-publish, same URL
Publishing again updates the same site in place — no new link to pass around.
Instant SSL
Every site is served over HTTPS from the moment it is live — on the shiply.now slug and on your custom domain.
What Replit does well
Replit is a strong cloud IDE — a fast place to build, prototype, and collaborate in the browser.
Replit is excellent for building and iterating in the browser with nothing to install. shiply.now handles the other half of the story: when the app is ready to live somewhere permanent, it gives it a real backend on a flat bill — in a single call, no account in the way.
Replit hosting alternative — common questions
How do I move a Replit app to a permanent URL?
Have your agent run the build, then publish the output to shiply.now in one call. Use the shiply MCP server at https://shiply.now/mcp, the CLI (npm i -g shiply-cli, then shiply publish ./dir), or a POST to /api/v1/publish. Each returns a permanent <slug>.shiply.now URL. No account is needed to make the first site, and re-publishing updates the same slug.
Is shiply a flat-price Replit hosting alternative?
Yes. shiply is flat — $0 on Free, $8 a month on Hobby, $24 a month on Developer — with no usage meter. There are no credits to buy or burn and no cold sleep on the URL: the price on the card is the price you pay whether the app gets ten visitors or ten thousand on its best day. It is predictable spend rather than usage-priced.
Can the moved app keep a real backend?
Yes. shiply gives every site a real backend: a Cloudflare D1 database on every plan, Neon Postgres on the Developer plan, Workers Lite edge functions for dynamic endpoints, a per-site inbox for email, and custom domains through Cloudflare. That is more than a static-only host, which stops at files.
Do sites go to sleep on shiply?
The URL does not cold-sleep. Every site is served over HTTPS from Cloudflare the moment it is live, on the shiply.now slug and on any custom domain. You get a permanent, predictable URL on a flat bill instead of usage-priced deployments.
Move your Replit app to a permanent URL.
No account needed. A real backend on a flat bill, live in a single call.