Host your whole monorepo as one.
ForkDeploy deploys multi-service repos the way they actually run together — shared secrets, the right deploy order, and services that can find each other. No tangled CI, no $200-a-month cloud bill.
Node.js · Go · C# · static sites · Docker — all from one repo.
# one repo, three services, wired together
project: shop
services:
database:
image: postgres:16
api:
build: ./apps/api
depends_on: [database]
env:
DATABASE_URL: {{ database.url }}
web:
build: ./apps/web
depends_on: [api]
env:
API_URL: {{ api.url }}Why ForkDeploy exists
Born from a monorepo headache.
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 does
Everything a small team actually needs.
The boring-but-important plumbing, handled — so you can just push code.
Monorepo-aware
ForkDeploy treats your repo as one deployable whole — not a pile of disconnected services you have to wire up by hand.
Shared secrets & env
Set a secret once and share it across services. No more copying .env files around or losing them between deploys.
Dependency-aware deploys
Tell ForkDeploy what depends on what. It brings your database up before the API, and the API before the web app — automatically.
Service discovery
Services get stable internal URLs and find each other out of the box. Reference one service from another with a single variable.
Zero-downtime updates
Push again and ForkDeploy rolls the change out gradually. Your site stays up while the new version takes over piece by piece.
Honest pricing
Free during the beta, for everyone. If it ever grows into paid plans, they will be fair — and you will hear about it first.
How it works
From git push to live, in four steps.
No dashboards full of knobs. Push your code and ForkDeploy does the careful parts.
- 1
Connect your repo
Point ForkDeploy at your monorepo and push, the same way you already do. No new tools to learn.
- 2
Describe your services
A small config lists your services and what depends on what. Most of it ForkDeploy can detect for you.
- 3
ForkDeploy deploys them, in order
Secrets are shared, services get internal URLs, and everything comes up in the right sequence.
- 4
Push again, stay online
Every later push rolls out gradually with zero downtime. Your site never goes dark mid-update.
What you can host
Bring your stack. All of it.
Start with web, Go, and C#. Anything that runs in a container runs on ForkDeploy.
Node.js
APIs, SSR, workers
Go
Fast single binaries
C#
.NET services
Static
Astro, Vite, plain HTML
Docker
Anything else you need
Who it's for
Made for developers — kept small on purpose.
ForkDeploy is built for people who write code and are comfortable with git and a config file. It is honest about that: there is no no-code layer, because a wrong click on real infrastructure has real consequences.
It is also intentionally small — a personal platform shared with friends and family, run with care, not a giant faceless cloud trying to onboard the world.
Good to know
Questions, answered honestly.
Is it really free?
Yes. Everything is free during the beta while I gather feedback. There is no card, no trial timer. If paid plans ever arrive, there will be plenty of notice and a fair free tier will stay.
Who is this for?
Developers — and right now, mostly friends, family, and people I know. It is a small, personal platform on purpose. If you are comfortable with git and a config file, you will feel at home.
Which languages and frameworks work?
Node.js, Go, C#, static sites, and anything you can put in a Docker image. The first focus is web apps, with Go and C# right alongside. More language support comes as the platform grows.
Do I need to know Kubernetes?
No. ForkDeploy runs on Kubernetes under the hood for reliable, zero-downtime deploys, but you never touch it. You describe services in a simple config and push — ForkDeploy handles the rest.
Can I self-host it?
Yes, that is on the roadmap. A self-hosted setup will be simpler and have fewer features than the hosted version, but it will let you run everything on your own machine.
Where does my code run, and is it safe?
It runs on a small EU-based cluster. Secrets are encrypted at rest and only shared with the services you choose. This is a personal project run with care — not a faceless cloud.
Want to deploy something?
Open the dashboard and connect your first repo. It is free while we are in beta — no card, no catch.