Who's behind this
I'm Andy McBrearty. I've been building software for over thirty years, most of it at startups and scaleups, much of it as the lead engineer or the engineering manager — which usually meant I was also the person who owned production, whether or not that was in the job description.
Deployably came out of doing that job too many times.
Nobody whose actual job was the platform.
The pattern was always the same. A small team, a good product, and nobody whose actual job was the platform. So the registry, the scanning, the deploy pipeline, the observability, the autoscaling and the cost of all of it landed on whoever had the most Kubernetes scar tissue. Usually me.
None of the individual pieces are hard. They're all open source, all well documented, all free. The hard part is that there are a dozen of them, they have to agree with each other, and something has to keep them agreeing for as long as you run production. That work never ends and it never ships anything a customer can see.
Deployably is that stack, assembled and maintained, so a team of five can run production like a team of fifty without hiring a platform engineer.
You never have to think about Kubernetes. That doesn't mean there's nothing underneath.
The homepage promise is the point of the product, not a claim that the stack is imaginary.
If you'd pick differently on any of those, I'd genuinely like to hear about it.
The honest picture.
The platform is live and running on managed Kubernetes. Deployments are metric-gated with automatic rollback, so a bad release backs itself out at three in the morning without either of us being awake for it. The Concept tier is free and open to early adopters. The paid tiers are in build, and early adopter pricing stays with you.
It's built by me and Tracie, my wife, from the Isle of Man, in the evenings and at weekends while we both still consult. That's the honest picture. The platform doesn't need us watching it; the company doesn't have a support rota yet. Worth knowing which of those matters to you.
Half an hour. No pitch.
I'm currently spending more time talking to founders and CTOs running multi-tenant products on Kubernetes than I am writing code — trying to work out where the real pain is rather than where I assume it is.
If that's you, I'd like half an hour. No pitch, and I'm not going to try to sign you up to anything. I mostly want to know what you built, what it cost you, and what broke.
If you'd rather try it than talk about it, that door's open too. The Concept tier is free for early adopters, early adopter pricing stays with you, and you get a say in what gets built next.
Either way it reaches me.