Why UHL
Boutique scale, engineering depth
UHL Hosting is a small Swiss team that builds commerce and infrastructure - and then runs it. That second part changes how we do the first.
Swiss company
Openprovider reseller
Medusa and Kubernetes specialists
Direct contact with engineers
Our approach
Designed for the work after launch
We make architecture and delivery decisions with ongoing operation, recovery, and handover in view.
One accountable delivery path
Architecture, implementation, and operations are planned together, so operational constraints are addressed before launch.
Commitments tied to scope
Resource sizing, operating coverage, and service commitments are written for the specific workload instead of presented as generic badges.
Portable by design
Medusa, WordPress, PostgreSQL, MySQL, and Kubernetes keep the architecture understandable and transferable.
Fit comes before the sale
If a simpler stack or another operating model is the better fit, that recommendation is part of the engagement.
Values
What working with us is like
Direct access to engineers
The people who scope and deliver the work stay involved after launch.
Ownership end to end
Consulting, implementation, and operations are handled by one accountable team.
Open-source alignment
We use portable platforms and document the path to another operator.
Swiss base
A Swiss company serving Swiss and EU customers with evidence-led commitments.
Stack
Technologies we work with
- MedusaJS
- Kubernetes
- Next.js
- PostgreSQL
- WordPress
- WooCommerce
- Openprovider
Frequently asked questions
How big is the team?
Small, and deliberately so. That is the trade you are making: you get the engineer who built the thing rather than a support tier, and in exchange we take on fewer clients than a larger agency would. If you need a supplier with a 24-hour follow-the-sun rota today, we are not it, and we would rather say that now.
Why do so few numbers appear on this site?
Because we publish claims only once we can evidence them. Uptime figures, SLA percentages and resource limits are commitments, and a commitment made on a marketing page to nobody in particular is not one we intend to be held to. The specifics go in your quote, in writing, for your workload.
What if you recommend against working with you?
It happens, and it should. A badly fitted customer costs us more in support and reputation than the contract earns. If a simpler stack, a different provider or no change at all serves you better, that is the advice you will get.
Can I leave?
Yes, and the stack is chosen so that leaving is a migration rather than a rewrite. Medusa, WordPress, PostgreSQL, MySQL and Kubernetes are all open platforms with other operators. We do not obstruct a domain transfer out, and your data is yours.
Where are you based, and where does the platform run?
We are a Swiss company serving Swiss and EU customers, and the managed platform is our own Kubernetes infrastructure rather than a reseller arrangement on top of someone else's panel.
See if we fit.
One conversation with an engineer tells you more than any pitch.