Open-source · self-hosted PaaS
Deploying an app shouldn't need a whole team.
Patr is an open-source, self-hosted platform that runs your apps on your own servers — a VM, a k8s cluster, or the Raspberry Pi in your drawer. You build. It deals with the rest.
Closed beta Not open to the public yet — I'm running it in real production right now, hitting the bugs myself so they're dead before they ever reach you. The code's on GitHub if you want a look under the hood.
Why this exists
Shipping shouldn't be open heart surgery.
You built the thing. Getting it in front of users should be the easy part. Instead it's an entire profession: pipelines, YAML, dashboards, a small army babysitting infrastructure so that something that's already built can go live. I've watched teams treat shipping an app like open heart surgery my whole career, and it never sat right with me.
Patr's whole job is making sure you never think about any of it. An entire PaaS, running on your own setup.
What you're not signing up for
No Kubernetes PhD
Point Patr at a VM, a cluster, or the machine under your desk. It doesn't care what's underneath, and you don't have to either.
No crippled free tier
Self-hosted is the full product, not a demo with the good buttons greyed out. Everything the paid plan has, minus the stuff only large orgs care about.
No cloud provider required
Your hardware is enough. A cloud account is optional, not a prerequisite. Your servers, your data, your call.
No separate observability stack
Logs and metrics are built in. Nobody should lose a weekend wiring up OTEL and Grafana just to see why their app crashed.
What's in the box
A whole PaaS, not a deploy button.
Deploy anything
A container image or a repo, onto a VM, a k8s cluster, or bare metal. One workflow, whatever the target.
Container registry
Push your images straight to Patr. No third-party registry to wire up first.
Domains + HTTPS
A free HTTPS URL out of the box, or bring your own domain. SSL is handled for you.
Logs & metrics
Built in. See what your app is doing without standing up OTEL and Grafana yourself.
Secrets & config
Managed secrets, injected into your deployments — not pasted into a YAML file somewhere.
CLI + API
Drive it all from the terminal, or hit the typed API directly. Scriptable top to bottom.
What you'd use it for
- Simplifying your AWS setup so your team ships faster instead of fighting the console.
- Letting developers deploy their own apps without a DevOps team getting involved.
- Getting logs and metrics without running a second infrastructure project to see the first one.
- Running on hardware you already own instead of renting someone else's.
How does it work?
You run it. You point it at your servers. You deploy.
# 1. set Patr up on a server you own
$ patr runner setup
✓ Patr is up at https://patr.your-domain.com
# 2. create a runner to deploy your apps onto
$ patr runner create
✓ runner created
# 3. push a deployment. that's the whole workflow
$ patr deployment push
✓ built
✓ deployed
→ https://myapp.your-domain.comEverything after that — logs, metrics, restarts, domains — is in the dashboard. Screenshots coming as the beta opens up.
Battle-tested — on me first
I'm hitting the bugs in prod so you don't have to.
Patr isn't a side project I'm hoping works someday. It's running real production workloads right now — mine. Every rough edge, every 3am page, every ugly edge case gets found by me, in prod, before it ever reaches you.
That's the whole point of the closed beta. I'd rather be the one who gets burned. By the time the doors open, the scary bugs are already dead — killed in a real production environment, not a test suite pretending to be one.
How is this different from…
| Patr | Heroku / Render | Coolify | DIY Kubernetes | |
|---|---|---|---|---|
| Open source | ||||
| Runs on your hardware | ||||
| Full product, free | free software, your time isn't | |||
| Logs & metrics built in | paid add-ons | basic | assemble it yourself | |
| VMs, clusters & bare metal | their cloud only | Docker hosts | ||
| Battle-tested | in prod now — mine |
Questions you're probably asking
Is it actually free?
The self-hosted version is the whole product — every feature, nothing greyed out. The only paid tier adds the governance stuff big companies need: SSO, billing, org-level controls. Solo devs and small teams never hit that wall.
Do I really not need Kubernetes?
Right. Point Patr at a VM, a cluster, or a spare box and deploy. If you happen to run k8s it'll use it; if you don't, you'll never know it was an option.
Where does my data live?
On your hardware. Patr is something you run, not a service you rent — nothing phones home, and there's no account you can get locked out of.
What happens when I outgrow one server?
Add more runners and spread deployments across them. Same workflow, more machines under it.
Can I use it in production today?
I do — that's the whole battle-tested-on-me thing above. For everyone else it's closed beta while I knock the edges off. Want in early? The code's on GitHub.
Latest from the blog
- Where were we all these years? June 1, 2026
I shut down a company I loved. Patr survived, went open source, and I'm not done. Here's the whole story, and an invitation.
- Eliminating Tests with Types March 19, 2026
How I used Rust's type system to make an entire class of API tests unnecessary: if it compiles, it's correct.
Come build it with me
Patr needs Rust people for the core, frontend people for the dashboard, and people who write docs, answer questions, and make a community worth hanging out in. I can't pay you today — but the moment there's real income, the people who built it with me get paid. The full, honest version of that story is here.
Sounds good?
It's early, and I'm not going to pretend otherwise. But "early" here means I'm the one in prod hitting the sharp edges, not you. Come watch it harden — or grab a file and help me sand it down faster.