Platform and infrastructure
Kubernetes
The reason the platform exists at all.
Why we chose it
We always intended to move off cPanel and Plesk. A control panel decides the shape of everything above it, and that shape had stopped fitting the applications customers actually wanted to run. So rather than resell somebody else's panel for another decade, we built the platform we wanted to operate. Every hosting product we sell is provisioned on it.
What it does here
Every customer workload runs as an isolated tenant: backend, worker, storefront, database, cache, storage, environments, backups and rollback.
The rest of the stack
- MedusaJSThe commerce engine, and the one we run our own business on.
- Proxmox VEOur own virtualisation, rather than a hyperscaler's abstraction.
- PostgreSQLThe database we trust with orders.
- RedisCache, event bus, workflow engine and locks.
- Next.js and ReactStorefronts that render on the server, because commerce is public.
- TypeScript and Node.jsOne language across the storefront, the backend and the plugins.
- S3-compatible object storageMedia and backups that outlive the container holding them.
- Our own DNSAuthoritative nameservers we operate ourselves.
- GitLabSelf-hosted source, CI and registry.
- StripePayments, without holding card data ourselves.
Running something like this already?
Tell us what you operate today and what hurts about it. We will tell you what we would change.