About
Born from a monorepo headache.
ForkDeploy is not a startup. It is one developer's answer to a problem that would not go away, grown into a small platform shared with people I know.
Why it exists
The wall I kept hitting.
I kept running into the same wall. A monorepo where the services would not work together: env files going missing between deploys, one app refusing to start without another, having to upload everything at once and hope it lined up.
The tools I tried were either too heavy for my little server, or a managed cloud that cost more in a month than a student should spend in a year. So I started building the thing I actually wanted: something that understands a repo as one connected whole.
That thing became ForkDeploy.
“Deploying a monorepo shouldn't feel like assembling furniture without the manual.”
What it takes
One person, a real cluster, a lot of evenings.
A deploy platform is not a weekend script. This is what actually goes into it.
The platform itself
A deploy engine that understands dependency graphs, a dashboard, a CLI, build pipelines, and the config format that ties it together. All designed, written, and maintained by one person.
Real infrastructure
ForkDeploy runs on a real Kubernetes cluster on real servers in the EU. Keeping it healthy means patching, monitoring, backups, and the occasional late-night fix when something misbehaves.
Evenings and weekends
This is not a company with a team behind it. It is built in the hours around study and life, because the problem is real and building the fix is genuinely fun.
The vision
Where this is going.
Four principles decide every feature that gets built, and every one that doesn't.
Small on purpose
ForkDeploy is a personal platform shared with friends and family, run with care. Not a giant faceless cloud trying to onboard the world. Staying small keeps it honest and keeps it good.
Developers only
It is built for people who write code and are comfortable with git and a config file. There is no no-code layer, because a wrong click on real infrastructure has real consequences.
The monorepo is the unit
Most platforms deploy one service at a time and leave the wiring to you. Here the repo is the deployable: services, secrets, and order all belong to one connected whole.
Fair by default
Free during the beta, for everyone. If paid plans ever arrive there will be plenty of notice, and a fair free tier stays. Nobody gets surprised by a bill.
The concrete plans for the rest of the beta live on the roadmap page in the docs.
Sound like your kind of platform?
Connect a repo and see the whole thing deploy as one. Free during the beta.