With Octopus Deploy the machines and services you deploy your software to are managed on the Infrastructure tab of the Octopus Web Portal:

The infrastructure tab of Octopus Deploy

Deployment Targets

With Octopus Deploy, you can deploy software to Windows servers, Linux servers, Microsoft Azure, AWS, Kubernetes clusters, cloud regions, or an offline package drop. Regardless of where you’re deploying your software, these machines and services are known as your deployment targets.

Deployment targets are defined as:

Target Count Against License
Important Note
Windows Server running a Tentacle1 Target per Tentacle instanceListening Tentacles registered multiple times on the same instance will count as one (1) target.
Linux Server running a Tentacle1 Target per Tentacle instanceListening Tentacles registered multiple times on the same instance will count as one (1) target.
SSH Connection1 Target per SSH Connection
Kubernetes Cluster1 Target per Kubernetes NamespaceA namespace is required when registering the Kubernetes cluster with Octopus Deploy. 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 Cluster1 Target per ECS Cluster
Azure Web App / Function / Cloud Service1 Target per Web App / FunctionThis represents how Octopus Deploy currently counts Azure Web Apps / Functions. However, one (1) Azure Web App / Function is not equal to one (1) Linux server.
Azure Service Fabric Cluster1 Target per Cluster
Offline Package Drops1 Target per Offline Package Drop
Cloud Region0 Target per Cloud RegionCloud 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 will only count Windows Servers, Linux Servers, ECS Clusters, Kubernetes Clusters, etc., that are registered with an Octopus Deploy Instance. If you have 5,000 Linux Servers, and 4,000 of them are registered with Octopus Deploy, then Octopus will only count those 4,000 against your license.

You can manage your deployment targets by navigating to Infrastructure ➜ Deployment Targets in the Octopus Web Portal:

The deployment targets area of Octopus Deploy

Learn more about deployment targets.


Before you can add your deployment targets to Octopus, you need to configure your environments. Environments represent the different stages of your deployment pipeline and ensure that the software that’s deployed is the same as it moves through those stages from, for instance, development, into test, and finally to production.

Typical environments include:

  • Development
  • Test
  • Production

You can add as many or as few environments as you require in your deployment pipeline, and you can add as many deployment targets to each environment as you need.

Learn more about environments.


Workers are machines that are used to execute tasks that don’t need to be performed on the Octopus Server or specific deployment targets. Examples of such tasks include deploying a package to an API or running a script. You can register multiple workers and assign them to worker pools.

Learn more

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Wednesday, October 4, 2023