Pricing

Free today. Honest about tomorrow.

ForkDeploy is free while it's in beta, full stop. This page is here to be upfront about what happens after, and why, rather than staying quiet about it.

Right now

One plan: free.

Beta

€0 / month

No card required. No trial clock running out.

  • Deploy your whole monorepo as one connected unit
  • All supported languages: Node.js, PHP, Go, C#, static, Docker
  • Automatic HTTPS, zero-downtime rollouts, custom domains
  • Secrets, env vars, and deploy logs

Looking ahead

Why a paid plan might show up eventually.

Servers cost money every month whether anyone deploys to them or not, and this is a one-person project without outside funding. A fair paid plan is how it stays around and keeps improving.

Paying for the server, not for you

Any future price is there to cover the cost of the machines ForkDeploy runs on, plus the time spent keeping them healthy. It is not a subscription-for-profit model.

A real free tier, always

Whatever plans eventually exist, a genuinely useful free tier stays. Small personal projects should never need a credit card.

Plenty of notice

If and when paid plans launch, current beta users hear about it well in advance, with time to decide, not a surprise charge.

Funds the roadmap

Revenue goes straight back into the platform: more capacity, faster builds, and the features requested by people actually using it.

Nothing is locked in yet. If you have thoughts on what a fair plan should look like, the feedback form in the dashboard reaches me directly.

In context

How the cost model compares.

Not a price sheet. ForkDeploy has no prices yet, and everyone else's change often. This is how each option charges you, and how that grows.

What you actually pay for

Kubernetes (DIY)

Cloud servers, load balancers, and the hours to keep them healthy.

Vercel / Netlify

A per-seat subscription, plus usage-based add-ons that stack up.

ForkDeploy

One plan per account. Your whole monorepo is inside it.

Adding a database, worker, or second API

Kubernetes (DIY)

More manifests, same cluster bill.

Vercel / Netlify

Each is a separate paid product or external add-on, with its own bill.

ForkDeploy

A few more lines in the same file. No new bill.

Cost as the team grows

Kubernetes (DIY)

Flat. It tracks infrastructure, not headcount.

Vercel / Netlify

Per seat, so it climbs with every collaborator.

ForkDeploy

The aim is to track what you run, not who logs in.

Free tier

Kubernetes (DIY)

None. You pay for infrastructure from day one.

Vercel / Netlify

Yes, and genuinely good for a single frontend.

ForkDeploy

Everything is free during the beta, and a real free tier stays after.

Who runs the servers

Kubernetes (DIY)

You do.

Vercel / Netlify

They do.

ForkDeploy

We do.

When you outgrow the free tier

Kubernetes (DIY)

Infrastructure, plus someone’s time to operate it.

Vercel / Netlify

Per-seat plus usage, so it can jump between invoices.

ForkDeploy

Priced to cover the servers and their upkeep, not to turn a profit.

Competitor details are general on purpose; their plans change often. For a feature-by-feature breakdown, see the comparison in the docs.

Try it while it's free.

Connect a repo and see the whole thing deploy as one. No cost, no catch, during the beta.