fDeploy ships as two components and you need both. Everything below is a direct download — no account, no email address, no licence request.
Install on: One machine
The control plane. A Windows service with the web dashboard, the OpenAPI v3 REST API, and a built-in NuGet package repository. It holds your projects, environments, releases, variables, and audit log. Install it once.
fDeploy Server 1.0.2.0 (x64)Install on: Every deployment target
The worker. A Windows service on each machine you deploy to. It receives packages over an authenticated, encrypted channel and performs variable substitution, IIS configuration, and PowerShell execution locally. Install it on as many machines as you like.
fDeploy Agent 1.0.2.0 (x64)Install the Agent on as many machines as you want. fDeploy is licensed per fDeploy Server instance, so deployment targets are unlimited and free on every tier — including Community. Adding a machine never changes your bill.
Install fDeploy Server on the machine that will host the dashboard. It arrives licensed for the Community tier, so it works immediately — there is no trial period and nothing to activate.
Install fDeploy Agent on each Windows machine you intend to deploy to.
Register each Agent with your Server from Infrastructure → Deployment targets in the dashboard.
Create a project, define a deployment process, and ship a release.
Both installers are signed, 64-bit, and register their component as a Windows service. System requirements, prerequisites, database setup, and the full walkthrough are in the installation documentation.
A fresh install is licensed for the Community tier, which is the complete product — unlimited projects, deployment targets and users — and free for organisations under $1M / €900k in annual revenue. See pricing for the paid tiers and the full eligibility rules.