Windows Deployment Tool

What it does

fDeploy is a self-hosted deployment automation tool designed for Windows teams deploying .NET applications to IIS. It runs as a Windows service on the user's own hardware with no cloud component. The system consists of a Server (which hosts the control plane, dashboard, OpenAPI v3 REST API, and a built-in NuGet package repository) and Agents (Windows services on each deployment target that execute packages locally). The tool handles projects, environments, target roles, deployment processes, and releases while storing frozen snapshots of configuration and variables.

Who it is for

The tool targets Windows-based development teams shipping .NET applications to IIS servers. It is built for organizations that want deployment automation without relying on cloud-hosted solutions or multi-tenant platforms. Teams using Active Directory can sync group memberships for access control. The licensing model supports free use for companies with up to 1 million USD annual recurring revenue, making it accessible to smaller organizations and enterprises with cost concerns.

Pricing

Licensed per Server instance, not per deployment target. The site does not display pricing tiers or costs for organizations exceeding the 1M USD ARR threshold.

How it stands out

fDeploy is fully self-hosted with no cloud dependencies or outbound license checks required. The tool bundles the NuGet package repository directly into the Server rather than requiring separate components. Release snapshots preserve the exact deployment process and variables at creation time, so redeploying older releases uses their original configuration snapshot instead of current project state. The system supports role-scoped deployment steps that map targets by role and environment within a single process, and includes progression phases that enforce ordered deployment across environments. Built-in IIS configuration management, certificate library with thumbprint-based binding, and XDT transforms for environment-specific configuration are included without additional tools.

What a founder should check

A potential competitor should examine how entrenched the existing deployment platforms are in Windows/.NET shops and what switching costs exist for teams already using Azure Pipelines, Octopus Deploy, or similar tools. Second, verify whether the single-Server-instance architecture (no clustering or high availability) is a real limitation preventing adoption by enterprises, or whether smaller organizations and on-premises shops genuinely prefer this constraint. Third, test whether the free tier for companies under 1M USD ARR meaningfully captures market share or simply shifts revenue expectations, since many deployment tools already offer free tiers or compete on other dimensions like ease of use or managed hosting.