Push your monorepo. Every service ships.
ForkDeploy deploys multi-service repos as one: shared secrets, the right order, zero downtime. You push, it handles the careful parts.
# 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 }}Node.js · PHP · Go · C# · static sites · Docker, all from one repo.
What it does
Everything a small team actually needs.
The boring-but-important plumbing, handled. You just push code.
Monorepo-aware
Your repo is one deployable whole, not a pile of services you wire up by hand.
Shared secrets
Set a secret once and share it across services. No more copying .env files around.
Dependency-aware deploys
Database before API, API before web. ForkDeploy resolves the order for you.
Service discovery
Every service gets a stable internal URL. Reference it with a single variable.
Zero-downtime updates
New versions roll out gradually. Your site never goes dark mid-update.
Honest pricing
Free during beta, for everyone. If paid plans ever come, you hear about it first.
Want the details behind each one? They live in the docs.
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.
- 2
Describe your services
One small config lists your services and what depends on what.
- 3
ForkDeploy deploys them
Secrets are shared, services get internal URLs, everything comes up in order.
- 4
Push again, stay online
Every later push rolls out gradually with zero downtime.
Curious how this compares to raw Docker or Kubernetes? See the side-by-side.
What you can host
Bring your stack. All of it.
Node.js, PHP, Go, and C#, with framework detection for the big ones. Anything that runs in a container runs on ForkDeploy.
Node.js
APIs, SSR, workers
PHP
Symfony, Craft CMS, Laravel
Go
Fast single binaries
C#
.NET services
Static
Astro, Vite, Angular, plain HTML
Docker
Anything else you need
The story
Built by one developer who got tired of fighting his own monorepo.
ForkDeploy started as a personal fix for a real headache and grew into a small platform run with care. Read why it exists and where it is going.
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 and 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. 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 (Next, Nuxt, Angular, Vite and friends), PHP (Symfony, Craft CMS, Laravel), Go, C#, static sites, and anything you can put in a Docker image. ForkDeploy detects the common frameworks and builds them for you. 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. Read the security page in the docs for the full picture.
Want to deploy something?
Open the dashboard and connect your first repo. It is free while we are in beta. No card, no catch.