Host a site Kimi generatedon your own subdomain
Kimi will hand over the code it wrote. Download it, drop it into dplooy, and the same site runs on an address you own — with free SSL, analytics and an editor you don't have to prompt.
Generated on their platform, hosted on yours
One-click publishing inside an AI product is convenient right up to the moment you want the site to be yours.
Left on the platform's link
- The address is issued by the tool and reserved words are taken
- Your site's uptime depends on the account you built it in
- No analytics you can export
- No control over robots.txt or the sitemap
- Migrating later means redoing the work anyway
Exported and hosted here
- yourname.dplooy.com, or your own domain on Pro
- Free SSL, managed and renewed for you
- Views, visitors, countries and referrers with CSV export
- robots.txt, sitemap.xml and a 25-point SEO audit
- Editable on the live page, no prompt required
Export, upload, live
Export the code from Kimi
Kimi can package up the files it generated for you to host yourself, rather than only publishing to its own link. Download the package and unzip it so you can see what you actually have — one HTML file, or a folder with CSS, JS and images beside it.
Ask for one self-contained file if you can
For a single-page site, asking Kimi for "one self-contained HTML file with the CSS and JavaScript inline" makes the rest of this trivial. It's also the shape that survives being moved between hosts without anything breaking.
Drop it into dplooy
One file: drag it onto the deploy area or click Browse files. A folder: click Choose folder and pick the top-level directory. A ZIP: drag it in and choose ZIP to site. Then pick your subdomain.
It's a website you own
Served over HTTPS at yourname.dplooy.com with free SSL, open to anyone with no account and no sign-in wall. Analytics start counting from the first visit.
Platform accounts and databases don't come with the export
If Kimi built you a full-stack site, the login system and the managed database it used belong to Kimi's platform and stay there — the exported code is the front end. That's fine for landing pages, portfolios, documentation and brochure sites, which is most of what people build. If you need form submissions, create a dplooy form endpoint and point your form's action at it; you get an inbox, email notifications and CSV export without running a server.
What the exported site gets
The same pages, on infrastructure that answers to your account rather than someone else's.
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
Why export at all when Kimi can publish it?
Convenience versus ownership. A platform link is fine for a draft. Once the site matters — a business page, a client deliverable, something you want ranking in search — you want the domain, the analytics and the ability to move hosts to be yours.
My export is a folder, not one file. Does that work?
Yes. Use Choose folder and pick the top-level directory. We keep the structure exactly as it is, so relative paths to ./styles.css and ./images/logo.png keep resolving, and links between pages carry on working.
What if the export contains package.json and a src folder?
Then it's source code, not a website, and it has to be built before anything can serve it. Run npm install and npm run build, then upload the output folder — usually dist or build. Or push it to GitHub and let Dplooy detect the framework and run the build for you.
Do visitors need a Kimi account?
No. Once it's hosted here it's an ordinary web page. No account, no sign-in, no rate limits, and it opens in every browser.
Can I edit it afterwards?
Yes. The visual editor lets you click text, images and colours on the live page and change them, on any plan. Pro adds a full code editor in the browser.
Can I use my own domain?
Yes, on Pro. Connect a domain you own, add the DNS records we show you, verify, and the site answers on your 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.
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.
Own the address, not just the code
Create a free account, drop the export in, and it's live on your own subdomain in minutes.