EN
We don't run Umbraco on shared Windows hosting, but on our own Linux instances in containers. Every site has its own container and its own database, fully isolated from the rest. That's not just tidier — it's the reason we can update without taking the site offline for even a second.
An update doesn't run on the live site, but next to it. We build the new version as a second container, let it start up fully and use a healthcheck to confirm it's healthy. Only then does the traffic switch over. Visitors notice nothing: no maintenance page, no error, no lost form submission.
If something does go wrong after all, we switch the traffic back to the container that's still right there. Rolling back is as fast as rolling out — and that is exactly what makes an update a non-event.
Because updating is no longer a risky operation, we can simply do it. Sites keep pace with the current Long Term Support version of Umbraco, including the security patches that come with it. No deferred maintenance piling up into a migration nobody dares to touch anymore.
The instances are generously sized: enough compute and memory to absorb a traffic spike without the backoffice slowing down. Media storage and bandwidth are scaled to match, so images, video and downloads can simply live on the site without hitting a limit at every upload.
A site that keeps up, updates that can happen on a Tuesday afternoon instead of in the middle of the night, and no growing gap between your version and the version the rest of the Umbraco world is on.
Curious what this means for your site? Let us know via the form below — we're happy to think along.
Adres
Postbus
Curious what this means for your site? Leave your details and briefly describe what you're running into, and we'll get back to you. We usually respond within one business day.
Prefer direct contact? Feel free to call or email us.
Yes. Modern Umbraco runs on .NET, which has been fully at home on Linux for years. We host every site in its own container on our own Linux instances, with its own database — fully isolated from other sites.
The new version is built as a second container next to the live site and started up fully. Only when a healthcheck confirms it's healthy does the traffic switch over. No maintenance page, no error, no lost form submission.
Then the traffic switches back to the container that's still right there. Rolling back is as fast as rolling out — exactly what makes an update stress-free.
No. Every site has its own container and its own database. A busy or misbehaving neighbour can't touch your site, and the instances are generously sized to absorb a spike in visitors.