Let the pull requestpublish the site
Copilot's coding agent works in the repo and hands you a pull request. Connect that repo to dplooy and merging it is the entire deploy step — build included.
An agent that works in git needs a host that does too
If the agent's output arrives as a pull request, the deploy should happen when you merge it — not in a second tool afterwards.
Deploying by hand after every merge
- Merge, then remember to build, then remember to upload
- The live site quietly drifts from main
- The build command lives in one person's shell history
- Rollback means hunting for the last good ZIP
- Nothing links a commit to what visitors actually see
Repo connected to dplooy
- Deploy on every push — merging is the whole workflow
- Framework detected from package.json, build command pre-filled
- Builds run on GitHub's runners, output deploys here
- Live build status and history in your dashboard
- One URL that always matches your branch
Set it up once, forget about it
Let Copilot work as it already does
Assign an issue to the coding agent and it opens a pull request, or use agent mode in your editor and commit the result yourself. Nothing about your workflow changes — the repo is still the source of truth.
Connect the repo to dplooy
On your dashboard, click Deploy from GitHub, authorise your account, and pick the repository and branch you want live. If the site's HTML sits in a subfolder, set the Root Directory field to point at it.
Set up the build if it 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 already filled in. Confirm it and we commit a workflow file and an encrypted API key secret.
Merge to deploy
Turn on Deploy on every push and each merge updates the live site on its own — build pipeline projects do this by design. Same URL, same analytics, same custom domain. If a build fails, the site you're already serving is left untouched.
Static output only
Dplooy serves files rather than running Node, so what gets deployed has to be plain HTML, CSS, JS and assets. A Next.js repo needs output: "export" in next.config; server actions, route handlers and middleware won't run. Plain HTML repos deploy with no build at all — the root just needs an index.html.
What the deployed repo gets
Everything a static host should give you, without a pipeline you have to maintain yourself.
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 Copilot deploy without going through GitHub?
Yes, through MCP. Copilot's agent mode supports MCP servers in VS Code and JetBrains, and Dplooy publishes a local server you run with npx plus a remote one over HTTPS. That said, if the code is already heading for a pull request, the GitHub route is fewer moving parts.
What 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 requires your explicit click, and repos you don't deploy are never touched.
My repo is already plain HTML. Do I need a build at all?
No. If the root directory — or the Root Directory you set — contains an index.html, the files deploy exactly as they are. No workflow, no package.json, no build.
Does this work with a private repo?
Yes. The connection is OAuth against your account, so private repositories you can access are deployable the same way public ones are.
What if a build fails?
Nothing changes on the live site. The deploy step only runs after the build step succeeds, so a broken commit can't replace a working deploy. Your dashboard shows the status and history so you can see which commit did 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 the merge the deploy
Create a free account, connect the repo Copilot works in, and stop deploying by hand.