Deployment automation for Windows. Licensed per Server instance, not per target.
Projects, environments, target roles, deployment processes, and releases carrying frozen process and variable snapshots. fDeploy Server runs as a Windows service on your own hardware. Deployment targets, projects and users are unlimited on every tier.
Download fDeploy 1.0.2.0
fdeploy.com and docs.fdeploy.com are deployed with fDeploy. Built in Stockholm; first commit 5 March 2019.
Two components.
fDeploy Server on one machine, fDeploy Agent on every deployment target. No cloud component; the NuGet feed is part of the Server.
Projects, environments and processes in the Server dashboard.
Capabilities and limits.
No multi-tenancy. One Server instance per installation; no clustered high availability.
Self-hosted
Server, package repository and Agents all run on your own hardware. No cloud component and no outbound licence check.
Role-scoped deployment steps
Targets carry roles such as web-server or app-server, and can belong to more than one environment. Steps select targets by role and environment, so one process covers all environments.
Progressions
An ordered phase pipeline assigned to a project. A release cannot deploy to a phase until every environment in the preceding phase has deployed successfully for that release.
Release snapshots
Creating a release snapshots the deployment process, variable values and package references, including values from linked library variable sets. Deploying an older release uses its snapshot, not current project state.
Configuration transforms
.NET XDT transforms run during deployment, with variable substitution applied on top. Environment-specific configuration stays out of the build.
Built-in NuGet repository
fDeploy Server hosts a NuGet feed. Packages are pushed to it from the build, and every pushed version is retained.
Certificate library
Certificates are stored centrally and bound to IIS sites as part of the deployment process. The Agent installs by thumbprint and skips one already present, so redeployment is idempotent.
Agent communication
Server and Agent authenticate each other over an encrypted channel. Packages, resolved variables and scripts travel across it. Sensitive variables are encrypted at rest and masked in logs.
Team-based access control
Permissions are assigned to teams rather than individual users, with roles scoped to projects, environments, or system-wide. Teams can map to Active Directory groups for membership sync.
OpenAPI v3 REST API
The instance serves its own OpenAPI v3 document. The dashboard is a client of the same REST API, so pipeline clients can be generated from the spec.
Licensed per fDeploy Server instance.
One licence per Server instance. Deployment targets, projects and users are unlimited on every tier, including Community.
Community is the same build as Professional. The difference is eligibility and support, not capability.
Perpetual licences do not expire. There is no licence server to contact and no kill switch, so an installation keeps running regardless of maintenance status or of what happens to the vendor. Maintenance is optional and covers new versions only.
Community
under $1M / €900k annual revenue
The complete product, free for commercial use by smaller organisations
Unlimited projects
Unlimited deployment targets
Unlimited users
Community support
Single server instance
Who it's for
Free for commercial use, in production, by any organisation with annual revenue under $1M / €900k - counted with any affiliates. Personal, educational, non-production and non-commercial open-source use is free at any size.
Professional
per year, per fDeploy Server instance
or $7,250 / €6,750 once - perpetual licence
Perpetual maintenance $1,450 / €1,350 per year - optional
For teams shipping Windows software in production
Unlimited projects
Unlimited deployment targets
Unlimited users
8/5 support, Mon–Fri 09:00–17:00 CET
Single server instance
Who it's for
Required once your organisation's annual revenue reaches $1M / €900k.
Academic
per year, per fDeploy Server instance
or $3,625 / €3,375 once - perpetual licence
Perpetual maintenance $725 / €675 per year - optional
For accredited institutions and registered non-profits
Unlimited projects
Unlimited deployment targets
Unlimited users
Async email support
Single server instance
Who it's for
Accredited academic institutions and registered non-profits whose annual budget is above the Community threshold.
Enterprise
Multiple fDeploy Server instances, a contractual SLA, and source code escrow.
Prices exclude VAT. EU business customers outside Sweden are invoiced under the reverse charge procedure. Payment by invoice and bank transfer.
Frequently asked questions
Which features are not supported?
No multi-tenancy, no runbooks, and no release channels. There are no worker pools: a step runs either on the deployment targets matching its roles, or once on the fDeploy Server itself. The deployment process is edited in the dashboard rather than defined in source control. fDeploy runs as a single Server instance, so there is no clustered high availability.
What step types are there?
Deploy to IIS, covering websites, web applications and virtual directories; Execute a script, for PowerShell; HTTP request; Manual intervention; and Send an email. Steps are scoped by target role and environment, accept variable bindings in their fields, and have run conditions.
How do rollbacks work?
There is no rollback action. You redeploy the earlier release. Because every release carries its own frozen process and variable snapshot, redeploying one cut six months ago uses the configuration that was current when it was cut, not what the project says today.
Can a step roll out gradually rather than hitting every target at once?
Yes. IIS, script and HTTP request steps running on deployment targets take a target batch size. Zero deploys to all matching targets in parallel, which is the default. One is sequential, so you can keep part of the infrastructure serving traffic. N deploys to N targets at a time.
Do you plan to ship a specific feature I need?
Send it to [email protected]. Requests are tracked and prioritised by how often they come up. We do not commit to timelines.