Commerce
Stripe
Payments, without holding card data ourselves.
Why we chose it
The one place we deliberately do not own the stack. Card data is a liability, not an asset, and there is no version of running it ourselves that serves a customer better.
What it does here
Checkout, subscriptions and invoicing for hosting plans and services.
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.
- GitLabSelf-hosted source, CI and registry.
Running something like this already?
Tell us what you operate today and what hurts about it. We will tell you what we would change.