Managed Medusa Hosting
previewControlled Preview for Medusa v2 workloads covering the backend, worker, PostgreSQL, Redis, and TLS. Resources and operating terms are confirmed by quote while the remaining production gates are validated.
Hosting
Managed hosting, run by the people who built it
Quote-first workloads on the UHL Kubernetes platform, with resources and operating coverage agreed before contract.
Select a Plan
Choose the right hosting tier for your workload.
Choose the operating model
Two managed runtimes, one accountable path
Start with the workload and maturity level. The commercial and operating boundary is agreed before anything is provisioned.
Controlled product maturity
Managed Medusa is in Preview. Managed WordPress and WooCommerce are in limited Beta. Both use selected, quote-first onboarding.
Scoped before contract
Resources, environments, backup policy, and operating coverage are written for the workload before onboarding.
Operated by UHL
Lifecycle operations are modelled and recorded, with destructive actions kept behind an engineer-reviewed path.
Included
What managed means here
A provisioned stack, not a control panel
Your service is provisioned as a defined workload on our Kubernetes platform rather than a slice of a shared box, so it can be resized and rebuilt without a migration.
Lifecycle operations, not support tickets
Provision, suspend, resume, resize, restore and terminate are modelled operations with real states and idempotency, run by our engineers rather than improvised at a shell prompt.
Domains attached by you, from your account
Attaching and detaching a domain is yours to do once control of the name is verified, alongside renewal when the window is open. The rest of the lifecycle stays with us on purpose.
Credentials held by reference
Database, SFTP, admin and API credentials are stored as references in a secret manager rather than inline in our database, and are never written to logs.
An audit trail per service
Every operation on your service is recorded with who asked for it and what happened. When you ask what changed last Tuesday, there is an answer.
Annual, customer-initiated renewal
Recurring plans are annual and prepaid, and renewal is something you initiate. Nothing renews itself while you are not looking.
Not included
What we do not claim
The second half of this list is the half that prevents an unhappy customer six months in, so it is on the page rather than in the small print.
No published SLA or uptime figure
Operating coverage is agreed in the quote for your workload. We would rather commit in writing to something specific than print a number on a marketing page.
No resource numbers before scoping
CPU, memory and storage are confirmed by quote against what you actually run. A plan table full of numbers that do not match your workload helps nobody.
Not self-service signup
Hosting is quote-first. You talk to an engineer, get a scoped quote, and then it is provisioned — which is slower than a checkout button and produces fewer bad fits.
How it runs
From conversation to operated service
Tell us what you run
Traffic profile, data size, integrations, and what the failure modes would cost you.
We scope it
Resources, environments, backup policy and operating coverage, written down before any money changes hands.
Provisioned
The stack is created as a managed workload with credentials issued into a secret manager, not emailed.
Operated
Domain attachment and renewal are yours from your account; the rest of the lifecycle is ours, and every operation is recorded.
Managed WordPress Hosting
betaLimited beta onboarding exercises the provisioner-backed runtime with selected workloads. Plans remain quote-first while security, backup, restore, lifecycle, and support gates are completed.
You will need a domain in front of it
Explore the supported extensions and lifecycle rules now. Registration and attachment remain separate from managed-hosting onboarding.
Frequently asked questions
Can I sign up for hosting online right now?
No, and that is deliberate. Hosting is quoted first: you tell us the workload, we scope resources and operating coverage, and you get a written quote before anything is provisioned. Domains are self-service; hosting is a considered purchase and we treat it as one.
What uptime do you guarantee?
We do not publish an uptime figure, because a number on a marketing page is not a commitment to anybody. Operating coverage is agreed in your quote for your workload, in writing.
How much CPU and memory do I get?
Confirmed by quote against what you actually run. We would rather size a service to your traffic and data than sell you a tier and hope it fits.
Can I attach a domain I registered with you?
Yes. Once control of the name is verified, a domain registered with us can be attached to — or detached from — a hosting service from your account, provided the service is running. A domain registered elsewhere can be pointed at the service in the usual way.
What can I do myself, and what needs an engineer?
From your account you can attach and detach domains and renew a service when the renewal window is open. Resizing, suspending, restoring and terminating are operator actions — they are the operations that can lose data or cost money unexpectedly, so they go through us, and every one of them is recorded against your service.
What happens to my data if I leave?
You leave with it. We build on open platforms — Medusa, WordPress, PostgreSQL, MySQL, Kubernetes — specifically so that leaving is a migration rather than a rewrite, and we do not obstruct a domain transfer out.
Do you host anything other than Medusa?
Managed Medusa is in Preview and managed WordPress and WooCommerce hosting is in limited Beta. Both use controlled onboarding while their remaining production gates are tested. If you run something else, tell us what it is — we will separate supported testing from capabilities we cannot yet offer.
Unusual workload?
Tell us what you run - we'll say honestly whether we're a fit.