Seven years in. 1.0 shipped.
fDeploy is a self-hosted deployment platform for Windows. One founder, one inbox, no investors, and the same tool we use to ship fdeploy.com and docs.fdeploy.com. This is the page that explains why a product like this exists in 2026.
7 yrs
since the first commit, March 5, 2019
1
founder · Stockholm
0
outside capital · 0 cloud bills
Windows shops. Teams that live in IIS, PowerShell, and on-prem datacenters and do not want to be told that the only modern way to deploy is to rent a runner from someone else's cloud.
Today most of these teams have two choices: pay enterprise prices for the entrenched commercial tool, or stitch together PowerShell scripts on top of a general-purpose CI runner and hope nothing rots. fDeploy is the third option — purpose-built, self-hosted, priced like software for humans.
Before fDeploy I spent a decade shipping .NET applications to Windows servers — four years at Skandia, one of Sweden's largest financial groups, and earlier engagements with Swiss Federal Railways, UBS, Migros, Schindler, and University Hospital Zürich. The pattern was consistent: teams either paid enterprise prices for a heavyweight commercial deployment tool, or lost weekends keeping brittle PowerShell pipelines alive. Neither felt like the right answer. So in March 2019 I started writing the tool I actually wanted to use.
Seven years later it deploys itself, deploys this website, and is finally good enough for other teams. There is no investor calendar driving the roadmap, no growth target dictating which features ship. That is the whole point.
Self-hosted by default
Your boxes, your control plane, your data. No telemetry phoning home, no SaaS fallback you cannot opt out of, no cloud account required to run the product.
Priced so it stops growing
One licence per server instance, whatever you deploy to. Charging per deployment target means punishing customers for succeeding, and we would rather have a bill you can predict three years out than a number that climbs every time you add a machine.
Slow software
Ready beats on-time. Seven years in the making is not a delay — it is the difference between software you ship and software you stake your releases on.
Questions, feedback, or a use case you want to talk through? Email [email protected]. One inbox, read by the founder.