Octopus Deploy counts deployment targets based on your license type. New customers and renewals will be on a PTM license. Previously, we offered a per-target license:
- PTM license (projects/tenants/machines) – Has a project limit with optional tenant and machine limits in the license key. Sold from Q4 2023 onward.
- Per target license - Only has a target limit, with no project or tenant limits in the license key. Sold between 2017 and 2024. From May 1, 2024, per target licenses are no longer available.
Please note: If you’re unsure of your license type, please refer to your invoice or contact sales@octopus.com.
| Deployment target | Machine Count Against License (PTM) | Target Count Against License (Per-Target) | Important Note |
|---|---|---|---|
| Windows Server running a Tentacle | 1 machine per Tentacle instance | 1 target per Tentacle instance | Listening Tentacles registered multiple times on the same instance will count as one (1) target. |
| Linux Server running a Tentacle | 1 machine per Tentacle instance | 1 target per Tentacle instance | Listening Tentacles registered multiple times on the same instance will count as one (1) target. |
| SSH Connection | 1 machine per SSH Connection | 1 target per SSH Connection | |
| Kubernetes agent | 0 machines per Kubernetes Agent | 1 target per Agent instance | |
| Kubernetes Cluster | 0 machines per Kubernetes Cluster | 1 target per Kubernetes Namespace | A namespace is required when registering the Kubernetes cluster with Octopus. By default, the namespace used in the registration is used in health checks and deployments. The namespace can be overwritten in the deployment process. |
| AWS ECS Cluster | 0 machines per ECS Cluster | 1 target per ECS Cluster | |
| Azure Web App / Function / Cloud Service | 0 machines per Web App / Function | 1 target per Web App / Function | This represents how Octopus currently counts Azure Web Apps / Functions. However, one (1) Azure Web App / Function is not equal to one (1) Linux server. |
| Azure Service Fabric Cluster | 0 machines per cluster | 1 target per cluster | |
| Offline Package Drops | 0 machines per offline package drop | 1 target per offline package drop | |
| Cloud Region | 0 machines per cloud region | 0 target per cloud region | Cloud regions are legacy targets that pre-dated workers as a mechanism to run scripts on cloud providers. They are used today to execute scripts multiple times with variables scoped for each iteration. |
Please note: Octopus only counts Windows servers, Linux servers, ECS clusters, Kubernetes clusters, etc., registered with an Octopus Deploy instance. If you have 5,000 Linux servers, and 4,000 are registered with Octopus, then Octopus only counts those 4,000 against your license.
Adding deployment targets
You add deployment targets in different ways, depending on the type of target and how the target will communicate with the Octopus Server. For instructions, see:
- Listening and Polling Windows Tentacles
- Linux SSH connection
- Linux Tentacle
- Azure Web App
- Azure Cloud Service
- Azure Service Fabric cluster
- AWS
- Kubernetes agent
- Kubernetes API
- Offline package drop
- Cloud regions
Learn more
- Target tags
- Dynamic infrastructure
- Machine policies
- Proxy support
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Thursday, June 27, 2024