No Lock-In: You Own Your ShiftPress Site (and Its GitHub Repo)
If you've read our comparisons of Wix, Squarespace or Jimdo, you'll have seen the same warning each time: the catch with those builders is that you can't cleanly take your site with you, so leaving means a rebuild. That lock-in is the thing we set out to avoid. This article is the honest answer to the fair question a careful buyer asks: "What actually happens if I want to leave ShiftPress?"
The lock-in problem we built against
Most website tools quietly hold your site hostage. Wix and Squarespace don't give you your code; Jimdo has no full export at all; a hosting-company builder ties your pages to its bundle. In each case, "moving" means rebuilding from scratch on a new platform. We compare the whole field on exactly this test in the website builder comparison, and the pattern is consistent: cheap or easy to enter, expensive to exit. ShiftPress is built to be the opposite.
What you actually get: your own GitHub repository
When your site is set up, ShiftPress creates a private GitHub repository just for it. That repo is the real source of your website, not a marketing promise:
- Every page as a clean Astro/HTML file.
- All your content, the text, headings and structure, in plain, portable files.
- Your images and assets, your styles and design, and your SEO metadata, titles, descriptions, structured data.
- Your redirects and sitemap, so the site's search setup travels with it.
It's ordinary, readable code in an open format, the same thing a developer would build by hand, not a proprietary export that only we can open. You can be granted access whenever you ask.
How to leave, if you ever want to
Because it's a standard static site, moving is genuinely simple:
- Get access to your repo. Ask, and the GitHub repository is yours to clone or take over.
- Build it anywhere. It's a normal Astro project, so it builds to plain static files.
- Deploy to any host. Netlify, Vercel, Cloudflare Pages, GitHub Pages or your own server all serve it happily. If you'd rather hand it to a developer, they'll recognise the setup immediately. We walk through the static-host route in moving a site to GitHub Pages.
No support ticket to unlock an export, no penalty, no waiting. The site is already in a form you can walk away with.
What keeps working, and what doesn't (the honest part)
We won't pretend everything survives a move untouched, because that wouldn't be true of any platform. The split is simple: files come with you; services don't. Anything that lives as a file in your repo is yours and keeps working. Anything that needs a live backend is a service you'd re-provision or replace elsewhere, the same as on any static host.
| Stays yours and keeps working | Stops working off-platform (a service, not a file) |
|---|---|
| All pages and content | Contact and lead-capture forms (submissions need a backend) |
| Design, styles and images | Meeting bookings / scheduler |
| Blog posts (as static pages) | The website chat widget (AI answers + human takeover) |
| SEO metadata, structured data, sitemap | Blog autopilot and auto-translation |
| Redirects and URL structure | The AI editor, and A/B experiments |
| Page speed (it's still static) | Managed analytics and instant indexing |
In plain terms: your website looks and reads exactly the same after a move, and it's still fast. What you'd give up are the conveniences that only exist because something is running behind the scenes. A contact form on a plain static site, for example, needs a form handler wired up wherever you host it, which is true whether you came from ShiftPress or built the site from scratch. Those are features you rent, not things we hold over you.
Why we do it this way
Lock-in is a way to keep customers who would otherwise leave. We'd rather not have that lever. If someone stays with ShiftPress, we want it to be because the hosting, the SEO, the AI editor and the managed features are genuinely the easiest, best way to run their site, not because escaping is painful. Handing every customer their own repository is us putting that in writing. It also keeps us honest: we have to keep earning the subscription every month. If you want the fuller picture of what a managed platform adds over hosting the static files yourself, we lay it out in ShiftPress vs self-hosting.
A site that's genuinely yours
ShiftPress builds your site as clean code in your own GitHub repo, hosts it fast, and runs the SEO, forms, bookings and AI editing for you, without ever holding your website hostage. Start free now.
Migrate my site ↗Frequently asked questions
Do I own my ShiftPress website?
Can I self-host my ShiftPress site or move it elsewhere?
What happens to my forms and bookings if I leave?
Is there any lock-in with ShiftPress?
The bottom line
Lock-in is the quiet cost buried in most website tools, and it's the one we designed out. Your ShiftPress site lives as clean code in your own GitHub repository, so the website itself, every page, all your content, the design and the speed, is yours to take anywhere, any time. The managed features that make the site easy to run are services you'd swap out if you left, and that's the honest trade. What you never have to fear is being stuck. That's the point.