The rocket that proves our point: why we moved our website off HubSpot
For months we have been making one argument in different forms. When we wrote about the Balancer, it was about not tethering yourself to a single AI provider you cannot replace. The thread running through it is deceptively simple: you should own what you depend on, and you should be able to leave if the ground shifts beneath you. There was, however, one conspicuous place where we had not taken our own advice. Our own website.
To be precise about what this is and is not: this is not the data sovereignty question we have written about elsewhere, where the issue is who can compel access to your data regardless of where it sits. A public marketing site holds nothing a foreign subpoena would want. This is the simpler, more universal question that sits underneath all of it. Could you walk away from your platform at all, and at what cost?
01 · The hypocrisy we couldn't ignore
It ran on HubSpot, as many company sites do, and we should be clear that HubSpot is a genuinely capable platform; this is not a hit piece or a complaint about the product itself. But it is, in miniature, precisely the kind of rented foundation we keep warning clients about. Your pages, your forms, your design logic, and a non-trivial slice of your customer-facing experience all live inside someone else's system, shaped by what that system permits, priced according to terms you do not set, and quietly difficult to walk away from once every form, tracking pixel, and landing page is wired into the machine. It is convenient at the start, and only reveals how hard it is to leave once you have settled in. We had written almost those exact words about AI vendors, all while our own front door sat on land we did not control.
So we moved it.
02 · Dependency is not captivity
Here is where we have to be honest about something more uncomfortable than a HubSpot bill, and it matters more given what we offer at the end of this post. We are not innocent bystanders in the platform economy. When we integrate a client into our stack, we are creating dependency; the software works precisely because it embeds itself into their operations and becomes difficult to casually replace. In that narrow sense, we are doing exactly what HubSpot does. We will not pretend otherwise.
The difference is not that we have eliminated gravity. It is that what we build sits on standard patterns and transparent integrations rather than a proprietary system designed to make leaving painful. The code is yours, the data is yours, and the architecture is the kind you can read, export, and hand to another team if you ever decide to. If we are doing our job, you stay because the work is good and the cost of switching is not worth it, not because we have quietly removed the exit.
Dependency is inevitable when a tool is doing its job well. Captivity is a choice the vendor makes when leaving is deliberately hard.
We build for the former and actively avoid the latter, and the test of that claim is simple: you could take what we build and run it somewhere else. Most of our clients will not want to, which is rather the point. But the door is real.
03 · The honest cost of doing it yourself
The migration itself was fast. Because we were moving only the website and not our CRM data, our marketing automation, or our back-office workflows, the scope was disciplined, and because we control the layer underneath, there was no platform fighting us, no export limits to work around, and no waiting on someone else's roadmap. It took hours rather than the days we had budgeted.
That speed is the least interesting part of the story, and if we left it there we would be doing exactly what we warn clients about: selling the easy bit and going quiet on the bill. So here is the bill. Self-hosting did not delete the cost of running a website. It moved it, and unlike a migration the moved cost keeps arriving every week. There is the virtual machine to provision, patch, and keep current. There is redundancy and failover, so a single machine going down at the wrong moment does not take the site with it. There is security hardening, monitoring, and alerting, so you find out about a problem before your customers do. There are backups you have actually tested, certificates that renew without anyone remembering to renew them, and ultimately a person who owns uptime when something breaks at two in the morning.
We can carry all of that because operations is our craft, which is exactly why we are comfortable recommending against doing it yourself. For a company without an in-house infrastructure team, "just self-host it" is bad advice dressed up as empowerment. The point was never that the cost disappeared when we left HubSpot. The point is who pays it, and whether they know what they are signing up for. That is true of a website, and it is far more true of the serious operational software that actually runs a business, which is the work we are really here to do.
04 · The rocket we could finally build
Years ago, when Gysho was new, we sketched a design idea we loved and could not execute: a small rocket that travels with you as you move through the site, a companion along the journey. On the tools we had then, it remained a sketch. On our own stack, we finally built it. There is now a small rocket that follows you across the site, and yes, it is a deliberate nod to the version of us that drew it years ago and had to let it go for lack of control over the ground we were building on.
It is a tiny thing, and it is also the entire argument in miniature. When you stop renting the ground you build on, you stop trimming your ideas to fit someone else's platform constraints.
The rocket exists because the site is finally ours.
05 · The question every company should ask
The principle scales up and down. Whether you are evaluating the AI models you build on, the infrastructure your data lives in, or the website at the front of your business, the questions are the same. Could you export all your content and customer data in a single day? If your platform doubled its prices tomorrow, could you leave within a quarter? Are there features you need that your platform refuses to build because they do not serve its average user? And the one most companies skip past: if you did leave, do you have the people to keep the thing running afterwards?
Most companies have at least one critical system running on a platform they could not walk away from without months of pain, and even the ones who could leave often have nowhere to land. If that is you, it is worth a conversation.
06 · What we actually offer
Let us head off the easy misreading, because it matters. We are not in the business of hosting your website, and this is not a pitch to move your marketing site onto our servers. The website was the demonstration, not the product. It was the cheapest honest way to show that we hold ourselves to the same standard we ask of our clients.
What we actually build is bespoke enterprise AI applications, on your IP and your data, running on a platform we maintain. That is a far deeper kind of trust than a marketing site, which is exactly why everything above this paragraph matters. When you build the software your business runs on with us, the question is not whether the pages load. It is whether your IP is genuinely yours, whether you could ever leave, and whether the thing we built will still be standing in three years without you having to become an infrastructure company to keep it that way.
Our answer is the one we just acted out on our own front door. The IP and the data are yours. What we build sits on standard, inspectable patterns rather than a proprietary cage, so it is the kind of system you could pick up and move. We run it so that you never carry the operational tax of patching, monitoring, redundancy, and security. And we build it so that you are never trapped, because a partner you cannot leave is not really a partner. Most of our clients stay for years. None of them stay because they have no way out.
We have walked this path ourselves, starting with our own website, so we know where the hidden costs are and who ends up paying them. If you visit the site while you think it over, the rocket will be there with you. And if you are ready to talk about building something of your own, on ground you control, here is how to reach us.