Somewhere in the process of choosing a managed website service, a version of this question shows up: if I hand my website to someone else, what happens when I want to leave? Do I own the site, or do I own a login to somebody else’s software?
It’s a fair question, and most vendors answer it with marketing instead of an answer. We’d rather just answer it, including the parts that don’t flatter us. Surmado keeps the code behind your website. Here’s exactly what that means, what it doesn’t mean, and how it compares to the other ways small businesses get a website handled.
Ownership, mapped
Ownership on the web splits into layers that don’t always travel together: the words and photos that describe your business, the domain name, and the code and software that make the site run. Here’s how those layers land across the market.
| Where the site lives | Who owns the code | Who owns your content | Who does the ongoing work |
|---|---|---|---|
| Self-hosted WordPress | You | You | You (or whoever you hire) |
| Wix or Squarespace | The platform | You | You |
| An agency build | Depends on the contract | Usually you, confirm it in writing | Them, for a retainer |
| Surmado | Surmado | You | Surmado, with your approval |
The rest of this post is what that table hides. Ownership isn’t one fact. It’s several, and the one that actually matters is usually the one nobody thought to ask about.
Self-hosted WordPress: you own the code, and the job that comes with it
WordPress is open source. Per WordPress.org’s own licensing page, the software runs under the GPL, and when you self-host it on your own hosting account, the code is unambiguously yours. No vendor can take it away or hold it hostage at cancellation, because there’s no vendor in the loop to do the holding.
That ownership comes with the job attached. Themes, plugins, updates, security patches, and hosting decisions are all yours, or your hired help’s. Outdated WordPress software is one of the more common entry points for attacks on small business sites, and the damage is often invisible from the front end. One of our customers, a moving company in Fort Worth, had 32 spam backlinks injected into their WordPress code before anyone noticed. No plugin flagged it. Nothing looked wrong on the page itself.
Full ownership is real here. So is the maintenance queue that comes bundled with it.
Website builders: you own your words, not the software
Wix and Squarespace sit in the middle. You own what you create on them, your text, images, and other content. Wix’s own Terms of Use say the user owns the intellectual property in their User Content, while Wix retains ownership of the platform and its software. Squarespace draws a similar line in its Terms of Service: you keep your content, its templates stay Squarespace’s.
Where it gets more consequential is what happens if you leave. Wix’s help center is direct about this: there’s no built-in way to export a full, working Wix site to run on another host, because the site depends on Wix’s own infrastructure to function. Squarespace lets you export your content as a file, which is genuinely useful if you’re moving into WordPress, but its own documentation confirms the design and templates don’t travel with it. Read both companies’ current terms yourself before you decide anything. Policies change, and it’s your business on the line, not ours.
The layer neither company advertises: even while you stay, you’re still the one doing the work. Updates, backups, SEO, page structure, the ongoing tinkering. It’s your site and your job, in one package.
If your complaint about Wix or Squarespace was ever “I don’t want to be the one doing this,” it’s worth reading how the broader alternatives actually compare, because most “alternatives” just hand you a different editor.
Agencies: ask before you sign, not after
Agency ownership terms vary enormously, and there’s no single industry norm to report here, which is itself the honest answer. Some agencies build on your own hosting and accounts and hand over full access at project end. Others build and host everything on their own infrastructure, license you the use of the site, and keep the underlying files if you leave. It’s common enough that owners only learn which arrangement they signed up for when the relationship ends and they ask for the keys.
None of that makes agencies a bad option. Custom strategy and complex builds are frequently worth an agency’s price and pace. It does mean the ownership question belongs in the contract conversation before you sign, not after. Ask, specifically: who owns the design files, who owns the CMS setup, and what do I actually receive if I cancel? Get the answer in writing.
Surmado: you keep the content, we keep the code
Here’s our version of the same three questions.
You keep your content. Business information, your logos and photos, the copy on your pages, your reviews, your offers, all of it stays yours, in Surmado’s own terms as much as in practice. Surmado doesn’t claim ownership of your content or the customer-facing copy published on your site.
You keep your domain. It’s yours, full stop, unless you’ve separately agreed otherwise in writing, which is rare.
You can get your content out. Our terms let you export your content and your site’s published copy in a usable, commercially reasonable format, on request while you’re a customer, and for 30 days after you cancel. That’s not a hypothetical clause. It’s the actual policy, and you can go read it right now.
What you don’t get to take with you is the code: the templates, the generated HTML, CSS, and JavaScript, the schema markup and structured data, the automations that keep it all running. That’s Surmado Materials, and it stays ours.
That last part is the trade this whole post is about, so it deserves an explanation rather than just a statement.
Why we keep the code
Keeping the code isn’t a lock-in tactic. It’s the only way we can make the promises that actually matter to a small business owner.
If you owned the code, security patching would become your job again, the exact job WordPress owners inherit and often defer until something breaks. Dependency updates, the unglamorous background work of keeping every library and framework piece current, would become optional, and optional security work gets skipped. Structured data and schema markup, the part of a site that helps AI platforms understand what your business actually does (part of what’s called AEO, Answer Engine Optimization), would drift out of date the moment nobody was watching it. Accessibility compliance would be a one-time pass instead of an ongoing standard. And a bilingual site would slowly become two sites that stop matching each other, because nobody keeps translations in sync by hand forever.
Owning the code and running it centrally is what lets us guarantee those things stay current across every customer, continuously, instead of promising it once at launch and hoping. You’re not buying a codebase you’ll maintain yourself. You’re subscribing to a maintained site, with a company on the hook for keeping it that way. That’s the actual product.
Membership includes hosting and your domain, maintenance and security updates, human support with a 42-point quality check on every change, and changes made by Surmado’s AI or, when it’s more involved, the team behind it. You ask in plain English, and the change goes live once you approve it. You also get to see the rebuild before you pay anything: Surmado rebuilds and previews your site first, and you decide whether to move forward. If you do, and it turns out not to be right for you, the 7-day money-back guarantee covers that too.
Membership starts at $99 a month billed annually, or $150 month to month. Pro+ at $199 a month billed annually adds a custom chatbot, up to five additional languages, and weekly blog posts. The full current numbers live on our pricing page, because prices are the kind of detail that shouldn’t be buried in a blog post that outlives them.
We might be the wrong fit, and that’s fine
If what you actually want is the code itself, in your own repository, something you or a developer you hire can open and modify directly, we’re honestly not your vendor. That’s not a hedge. It’s the plain answer. Surmado is built around running one platform well for every customer on it, and that’s what makes the maintenance guarantees above possible in the first place. It’s also why the code doesn’t leave.
If owning the code outright is the priority, two paths get you there honestly: self-hosted WordPress with a developer you trust, where the code is yours from day one, or a freelancer or agency that will contractually assign you the finished files and design at project end (get that assignment in writing; see the agency section above). Both cost you either your own time or someone else’s hourly rate, in exchange for that ownership. That’s a real trade, and for some businesses it’s the right one.
For everyone else, the actual question isn’t “who owns the code.” It’s “do I want to be the one responsible for it.” If the honest answer is no, that’s what a managed service, ours included, is for. Our FAQ covers more of the practical details on cancellation and export if you want them before deciding either way.
The bottom line
Every option in this post is honest about ownership once you read past the pricing page. WordPress gives you the code and the job that comes with it. Builders give you your words and a platform you can’t take with you. Agencies give you whatever you negotiated, so negotiate it. Surmado gives you your content, your domain, and a way out with your words intact, in exchange for us keeping the engine that runs underneath.
That’s the deal. We think it’s a fair one, but you should be the one who decides that, not our marketing page.
See what’s included in Surmado Sites, or go read the actual terms yourself before you take our word for any of it.