Delivery
GitLab
Self-hosted source, CI and registry.
Why we chose it
The same argument as the rest of this page: a delivery pipeline that depends on somebody else's availability is not a pipeline we can promise anything about. Ours runs on our own infrastructure.
What it does here
Source control, CI, container registry and the deployment path into the platform.
The rest of the stack
- MedusaJSThe commerce engine, and the one we run our own business on.
- KubernetesThe reason the platform exists at all.
- 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.
- 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.