Let the repo deploywhat Codex writes
Codex already works where your code lives. Connect the same repo to dplooy, and merging a Codex pull request is all it takes to build the site and put it live on your own domain.
The deploy step nobody should be doing by hand
An agent that works in git deserves a host that works in git. Anything else means a human copying files between two systems.
Manual deploys after every change
- Merge, then remember to build, then remember to upload
- The live site drifts from main without anyone noticing
- Build steps live in someone's shell history
- Rollback means finding the last good ZIP
- Nothing connects a commit to what's actually served
Repo connected to dplooy
- Deploy on every push — merge is the whole workflow
- Framework detected from package.json, build command pre-filled
- Builds run on GitHub's servers, output deploys here
- Live build status and history in your dashboard
- One URL that always reflects your branch
Wire it up once
Let Codex work in a repo as usual
Nothing changes about how you use it — Codex reads the repo, makes changes and opens a pull request. Review and merge exactly as you would a human's.
Connect the repo to dplooy
On your dashboard, click Deploy from GitHub, authorise your account, and pick the repository and the branch you want live. If your site's HTML sits in a subfolder, set the Root Directory field to point at it.
Set up the build if the repo needs one
For framework source we read package.json, detect Vite, Next.js, Astro, SvelteKit, Nuxt, Angular or Create React App, and offer Set up build & deploy with the right command and output folder pre-filled. Confirm it and we commit a workflow file plus an encrypted API key secret to your repo.
Merge to deploy
Turn on Deploy on every push and each merge to your branch updates the live site by itself — build pipeline projects do this by design. Same URL, same analytics, same custom domain. Or click Redeploy now whenever you want one on demand.
Static output only, and Next.js needs an export
Dplooy serves files rather than running Node, so the deployed thing has to be plain HTML, CSS, JS and assets. A Next.js project needs output: "export" in next.config so the build writes an out folder; server actions, route handlers and middleware won't run. Plain HTML repos deploy with no build at all — the root directory just has to contain an index.html.
What the deployed repo gets
Everything a static host should give you, without a pipeline you have to maintain.
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 Codex deploy directly, without GitHub?
Yes, through MCP. Codex supports MCP servers — codex mcp add writes the entry into ~/.codex/config.toml — and Dplooy publishes both a local server you run with npx and a remote one over HTTPS. The local server can read your disk, so Codex can deploy a folder it just built. For a repo you're going to merge into anyway, the GitHub route is still less work.
What exactly gets committed to my repo?
Only if you ask for the build pipeline: a workflow file at .github/workflows/dplooy.yml and an encrypted DPLOOY_API_KEY secret. We request the repo and workflow scopes to do it, every install needs your explicit click, and repos you don't deploy are never touched.
My repo is already plain HTML. Do I need a build?
No. If the root directory — or the Root Directory you set — contains an index.html, we deploy the files as they are. No workflow, no build, no package.json required.
Can I change which branch is live?
Yes — run Deploy from GitHub again and pick a different branch. Note that a repo maps to one dplooy project per account: deploying it again updates that same project and URL rather than creating a second site, which is what you want when redeploying and worth knowing before you try to preview two branches side by side.
What happens if a build fails?
The live site stays exactly as it was — a failed build never replaces a working deploy. Your dashboard shows the build status and history so you can see which commit broke it.
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 and renew.
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.
Make merging the deploy
Create a free account, connect the repo Codex works in, and stop deploying by hand.