Step 1
Connect your published address
Open GitHub Sync in your account, paste the address your site is already published at and choose which of your hosting services to copy it to. The first copy starts straight away.
GitHub Sync · Included with every hosting plan
Build it your way. Publish on your own domain, automatically.
Bring your published site from GitHub Pages, Netlify, Vercel, Cloudflare Pages or Lovable. We check it every hour and copy changes onto your own hosting, ready for visitors at your own domain.
Built with Lovable, Bolt or v0, by your developer or by you — connect the published address and keep building your way.
Safety checks protect the copy on your hosting. See what happened at each check, pause updates or resume them from your account.
Want no code at all? Try our Website Builder, or read the guide to choosing your route.
Connect once
From your published site to your domain
Keep using the builder or tools you know. Publish to one of the five supported hosts and GitHub Sync takes care of copying the static site.
Step 2
We check every hour
We check your published site for the latest version. When something has changed, we fetch the static files and check them before copying.
Step 3
Changes appear on your domain
Once the safety checks pass, your visitors see the new version on your hosting. Your account keeps a history of what each check did.
Keep your domain and your way of working
A home for the site you already built
Lovable, Bolt and v0 can build your site and publish it to a supported host. Bring the static result here for your own domain, email and forms, while you keep using your chosen builder.
Lovable puts custom domains behind a paid plan ($25/month, about £18.55, about £223/year), but its GitHub sync is free on every plan, including Free. You can build free, publish free on a supported host, and connect the published address here for your own domain.
None of the five source hosts provides email at your domain. Keep your domain, email and forms on your own hosting, while your developer or AI tool keeps working where they choose. Forms need a working endpoint on your hosting; copying a site does not set that up for you.
GitHub Pages' terms restrict business use, and GitHub can remove a site that breaks its rules. Vercel's free Hobby plan is for non-commercial personal use only. Netlify and Cloudflare Pages do allow commercial use. Our GitHub Pages and web hosting comparison explains the differences. The published source still needs to follow its host's rules, even when you copy it here.
How a real customer uses it
A customer's friend built their site with AI on GitHub Pages. The customer wanted it on their own hosting. Now every change the friend pushes and publishes appears on the customer's domain by the next hourly check, once the safety checks pass.
Checked before and after each copy
How the safety checks work
- Only real changes We check your published site for the latest version every hour and copy only when something changed.
- Never a blank site If the source host has removed the site, served an empty page, or left files out, nothing is copied and you see why in your account.
- Put back if it breaks After a copy we load your site. If it does not answer properly, the previous good version goes back automatically.
- Pauses itself Three failed checks in a row pause the sync so it does not keep trying. Resume it whenever you are ready.
- Your files stay yours We update the copied static files. Existing files with other names are never deleted, so your own PHP, .htaccess and WordPress stay put.
- Static sites only Only the published static files are copied, whichever supported host you use. Forms and email still run on your hosting.
These are the same safety checks shown in your account, where you can read each result.
What you can connect
Works with any static site generator
Next.js static export, Astro, Hugo, Jekyll or plain HTML: publish the static output on GitHub Pages, Netlify, Vercel, Cloudflare Pages or Lovable, then connect its address.
The published files, ready to copy
Your site is copied as served by your chosen source host. GitHub Sync does not build your repository or run server-side applications.
PHP files are never uploaded by the sync. You can run PHP and MySQL applications separately on your hosting; browse the included open-source apps or try the free Website Builder.
A few practical limits
- Static files only.
- Up to 3 syncs per account.
- For GitHub Pages, the repository must be public. The other hosts just need the site published and publicly reachable.
- Connect the site's github.io, netlify.app, vercel.app, pages.dev or lovable.app address.
The published site must pass the safety checks before it can be copied.
Free with every hosting plan
GitHub Sync is included
Start with 15 GB for your website and email, with 1 TB bandwidth, SSL and daily backups included. There is no extra charge for GitHub Sync.
Use a domain you already own or find a new domain separately.
Need a hand connecting your site? Send us a message and a real person will reply.
Before you connect
A few practical questions
Do I need a GitHub account?
No. You need a Gravity Host account with an active hosting service and the published address from one of the five supported hosts. If you use GitHub Pages, your friend or developer can own the GitHub account and public repository. You do not need to give us a GitHub password or access token. The other hosts just need a published, publicly reachable site.
Can my developer keep using GitHub or an AI builder?
Yes. They can keep editing, committing and publishing to GitHub Pages, or use Lovable, Bolt or v0 to publish a static site on a supported host. We check every hour and copy the changed published site after it passes the safety checks. You can also choose Check now in your account.
What happens if the source host removes the site?
The copy on your hosting stays as it is. We do not copy the source host's missing-site page or an empty page over it. The check history explains what happened, and three failed checks in a row pause the sync. Once the published source site is available again, you can resume it.
Does it overwrite my WordPress?
No. Your own PHP, .htaccess and WordPress stay put. The sync updates the copied static files; existing files with other names are never deleted. You choose the hosting service and folder for the static site. Use a separate folder when adding a static site alongside an existing WordPress site.
Can I turn it off?
Yes. Pause or remove the sync from GitHub Sync in your account. Your hosted files stay in place. Resume a paused sync whenever you are ready for hourly checks again.
Your next update, on your own domain
Bring the site you built to your own domain
15 GB hosting is £45 for your first year, then £75 a year. GitHub Sync is free with every hosting plan.