Ownership
The keys are yours.
Most agencies hand you a website and keep the way in. We do the opposite. On launch day the code, the content, the hosting account and the domain are all in your name — and you can walk away with every one of them.
- /contentStructured content, exportable as JSON
- /mediaEvery image and file, original quality
- /srcTemplates, components and styles
- /redirectsEvery old URL, mapped to its new home
- .gitFull history of every change
- README.mdHow to edit, build and deploy
Illustrative layout. Your handover is tailored to your site.
Five things you hold on day one.
Ownership isn’t a promise in a contract. It’s a list of accounts and files, each with your name on it.
-
01
The code
The complete source lives in a Git repository on your own account, with the full history of every change. Nothing is minified, hidden or licensed back to you.
Held byYou — your Git account -
02
The content
Posts and pages live as structured, typed content in a database on your own account, with a documented API and a full JSON export any future platform can import.
Held byYou — your own database -
03
The media
Your images, downloads and documents come across at original quality and live in storage on your own account, not trapped in someone else’s media library.
Held byYou — your storage account -
04
The hosting
The site is deployed from your repository to a hosting account you create. It runs on any major cloud, a serverless platform or your own server.
Held byYou — your hosting account -
05
The domain
Your domain stays registered to you throughout. At launch, one setting is pointed at the new host. We never take it over.
Held byYou — your registrar
Side by side
Renting a website versus owning one.
| The question | Typical WordPress site | With bsize |
|---|---|---|
| Can you export everything? | Posts and pages export. Theme settings and plugin data often stay behind. | The code is already in your repository, and content exports as JSON through a documented API, any time. |
| Who holds the code? | A mix of theme, page builder and plugin licences, each with its own terms. | You do. The full source sits in your own repository. |
| Can you change host? | Possible, but it means moving a database, a PHP setup and a set of plugins that may not all survive. | Deploy the repository to a new host and copy the database across. A move, not a rebuild. |
| What if your developer vanishes? | Someone has to learn a bespoke theme and plugin stack before touching it. | Any web developer can read the repository and carry on. |
| What do you pay for licences? | Recurring licences for page builders, forms, SEO and security plugins. | No licence keys and no per-plugin renewals. |
| How readable is your content in 20 years? | Tangled up with shortcodes and page-builder markup that only those plugins understand. | Clean, structured content with a documented schema. Readable by any tool, today and long after. |
The walk-away test
If you leave us, nothing breaks.
The easiest way to trust a handover is to imagine the worst case. Here is what happens if you ever decide to part ways.
- 01
You keep the site
It is already running from your hosting account, built from your repository. Nothing is switched off when the working relationship ends.
- 02
You keep the instructions
The README explains how to edit content, build the site and deploy it, written for someone who has never met us.
- 03
You hand it on
Give the repository to another developer, or a different agency, and they pick up exactly where we stopped. No permission needed from us.
Questions owners ask
The fine print, in plain English.
Do I have to keep paying bsize to keep my site?
No. The site runs on a hosting account in your name, so it keeps running whether or not we are involved. Any ongoing support is optional and agreed separately.
Who owns the design and the code we build?
You do. At handover, the repository and everything in it belong to you.
What about third-party tools and fonts?
Anything we use is listed in the handover notes, with its licence. We favour open-source tools and fonts you can use freely.
How do I edit content after launch?
You get a simple editor and a short walkthrough, so your team can update pages without touching code. Drafts and version history let you preview changes and roll them back.
What if I want to move to something else later?
Take the repository with you. Content is structured and exports as JSON, so it imports cleanly into most modern platforms.
Get your website back.
Send your URL. You’ll get a plain-English plan: what moves, what goes, and what it costs.