If you are hosting your Octopus Server yourself, these are the minimum requirements.
The Octopus Server is hosted on a Microsoft Windows operating system, however, once your Octopus Server is up and running, you can deploy to Windows servers, Linux servers, Microsoft Azure, AWS, Cloud Regions, or even an offline package drop.
Octopus Server can be hosted on any modern Windows Server. We automatically test the Octopus Server on the following versions of Windows Server:
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
Octopus Server will run on the newer versions of Windows Server without GUIs, however, the easiest installation path is to use "Windows Server with a GUI" and run our installation wizard. If you want to use one of the new GUI-less servers, you will need to add some missing Windows Features and configure the Octopus Server yourself.
Learn about automating installation.
Octopus Server will run on client/desktop versions of Windows, such as Windows 7 and Windows 10. This can be an easy way to trial Octopus Server; however, we do not support Octopus Server for production workloads unless it is hosted on a server operating system.
SQL Server Database
Octopus works with a wide range of versions and editions of SQL Server, from a local SQL Server Express instance, all the way to an Enterprise Edition SQL Server Failover Cluster or SQL Server AlwaysOn Availability Group, or even one of the hosted database-as-a-service offerings.
The following versions of SQL Server Database are supported and automatically tested against every release of Octopus Server:
|Octopus Server||Minimum SQL Server version||Azure SQL|
|2020.1.x ➜ latest||SQL Server 2016+||Supported|
|3.0 ➜ 2019.13||SQL Server 2008+||Supported|
The following versions of Octopus have a requirement for SQL Server 2017+. This requirement has been relaxed to SQL Server 2016+ with any patch version later than specified in this note.
2020.2.1 ➜ 2020.2.18 2020.3.1 ➜ 2020.3.5
- Express (free)
- Microsoft Azure SQL Database
- AWS RDS SQL Database
Warning: Octopus does not support database mirroring or SQL Server replication. Having these features turned on may cause errors during configuration. More information.
We try to keep the .NET Framework requirements for Octopus Server as stable as possible:
- Octopus 3.4 to Octopus 2018.4 requires .NET Framework 4.5.1 or newer.
- Octopus 2018.5 and later requires .NET Framework 4.5.2 or newer and WMF/PowerShell 5.0 or newer.
- Octopus 2019.7 and later requires .NET Framework 4.7.2 or newer.
- Octopus 2020.1 and later is a fully self-contained distribution bundling the .NET Core 3.1 runtime - no .NET Framework is required.
- Windows PowerShell 2.0. This is automatically installed on 2008 R2.
- Windows PowerShell 3.0 or 4.0 are recommended, both of which are compatible with PowerShell 2.0, but execute against .NET 4.0+.
- Windows PowerShell 5.1 is required to run Azure steps.
The Octopus Server includes the Octopus Web Portal user interface and we try to keep this as stable as possible:
- Octopus 3.0 to Octopus 3.17 supports all modern browsers and Internet Explorer 9+.
- Octopus 4.0 and later supports all modern browsers, and Internet Explorer 11+ (available on Windows 7 and newer, and Windows Server 2008R2 SP1 and newer).
- Octopus 2020.1 and later only supports modern browsers - Internet Explorer 11 is no longer supported.
There is no one size fits all approach for Octopus Server. The best approach is to start with a working Octopus Server, start deploying your applications, monitor your server statistics, and scale from there.
- Absolute minimum to make it run: 512MB RAM, 1GHz CPU, 2GB free disk space.
- Recommended starting point for smaller deployments (less than 30 deployment targets for example): 2GB RAM, dual-core CPU, 10GB free disk space.
- Recommended starting point for larger deployments: 4GB RAM, dual-core, 20GB free disk space.
Need support? We're here to help.