Host a Replit buildwithout keeping a Repl awake
If what you built is a front end — a landing page, a portfolio, a React app that talks to an API — it doesn't need a running container. Export it once and dplooy serves it as static files on your own subdomain.
A front end doesn't need a server
Replit is a great place to build. Once the front end is finished, keeping a container alive to serve a folder of files is doing a lot of work for nothing.
Serving it from the Repl
- A whole runtime kept alive to hand out static files
- The URL names Replit, not you
- Cold starts and container limits sit in front of your visitors
- Analytics mean wiring up a third-party script
- Your hosting is coupled to your editor
Serving it from dplooy
- Plain static files on a global CDN — nothing to keep awake
- yourname.dplooy.com, or your own domain on Pro
- Free SSL, managed and renewed for you
- Views, visitors, countries and referrers built in
- Keep building in Replit; redeploy whenever you want
Two routes, pick the one that fits
Get the code out of Replit
For a one-off, open the three-dot menu in the file tree and choose Download as zip. For anything you'll keep working on, link your GitHub account in Replit's connected services and connect the repo from the Git pane instead — that route can redeploy on every push.
Build it, if it's a framework project
Plain HTML, CSS and JS can be deployed as-is. A Vite or React project has to be built first: run npm run build and you get a dist folder (or build, on Create React App). That folder is the website; the src folder is not.
Deploy the ZIP, the folder, or the repo
Drag the ZIP onto the deploy area and choose ZIP to site when we ask what to do with it. Or click Choose folder and pick your dist folder. Or click Deploy from GitHub, pick the repo and branch, and let Dplooy set up the build.
It's live on your subdomain
Served over HTTPS at yourname.dplooy.com with free SSL, no container, no sleep, no cold start. Analytics start on the first visit.
The backend half stays where it is
Dplooy hosts static files — HTML, CSS, JS, images. If your Repl also runs an Express server, a Flask app or a database, that part needs somewhere that executes code, and Replit is a perfectly good home for it. Host the front end here, point it at your API's URL, and make sure the API allows requests from your dplooy domain.
What you get once it's off the container
Static hosting sounds like less. In practice it's a faster site with more tooling around it.
Your own subdomain
yourname.dplooy.com instead of a link that names somebody else's product. Point a custom domain at it on Pro.
Free SSL, always on
Every site is served over HTTPS with a certificate we manage. Nothing to buy, configure or renew.
Real analytics
Views, unique visitors, countries, referrers and devices — for the whole site, exported as CSV whenever you want it.
Findable in search
robots.txt and sitemap.xml are generated for you, and the SEO analyser scores 25 checks and tells you what to fix.
Editable after publishing
Change text, images and colours on the live page with the visual editor, on any plan. Pro adds a full in-browser code editor.
Private when you need it
Password-protect the whole site on Pro, or put an email gate in front of it and collect the addresses.
Frequently asked questions
Can I deploy straight from GitHub instead of downloading a ZIP?
Yes, and it's the better route if the project is still moving. Link Replit to GitHub, then in dplooy click Deploy from GitHub, pick the repo and branch, and turn on Deploy on every push. Every commit updates the site at the same URL, with analytics preserved.
My Replit project is React. Will it just work?
Not as source code — .jsx files can't be served to a browser directly. It has to be built. Either run npm run build locally and deploy the dist folder, or deploy through GitHub: Dplooy reads package.json, detects Vite or Create React App, and offers Set up build & deploy so the build runs on GitHub's servers and the output lands here on every push.
What about my database and my API routes?
They stay on Replit, or on any host that runs code. This is static hosting: we serve files, we don't execute your server. Most Replit front ends work unchanged once you point them at the API's public URL and allow your dplooy domain in the API's CORS settings.
Will the site sleep if nobody visits?
No. There's no container to sleep. Your files sit on a CDN and are served the same on the first request of the day as on the thousandth.
Can I use my own domain?
Yes, on Pro. Connect any domain you own, add the DNS records we show you, and the site answers on your own address with SSL we manage.
Is it free?
Yes, on the free plan: 3 hosted projects, free SSL and analytics. Free-plan sites are removed after 3 days. Plus and Pro sites stay up indefinitely, and Pro adds custom domains and password protection.
How do I update the site after I change the Repl?
Redeploy the same project so the URL and its analytics stay intact. On a GitHub-connected project, click Redeploy now — or Rebuild & deploy if it uses the build pipeline — and if Deploy on every push is on, you don't have to click anything at all.
Other ways to get there
Hosting for the other AI builders
Same platform, same free plan. Whichever tool wrote the site, it ends up on an address you own.
Ship the front end. Skip the server.
Create a free account, export the Repl, and have it live on your own subdomain in minutes.