Pay as you Grow

Our plans offer simple and predictable pricing
for your teams from startups to scaleups



Technical support

Main Feature Set

Unified inventory

Service catalog

Configuration management

Stack builder

Application deployment

Full-stack monitoring

Pro Feature Set

Usage reporting

Teams / user policies



1 user

10 jobs

Main Feature Set

Best Effort Support



Best effort



per month

1 user

100 jobs

Main Feature Set

Standard Support






per month

5 users

1000 jobs

Main + Pro Feature Set

Priority support





Unlimited users

Unlimited jobs

Main + Pro Feature Set

Priority support





A job is created and executed each time you deploy a setup or register a host to Cycleops. A deployment job is a run to one or more targets. Deployment targets can be any combination of registered hosts or hostgroups. Registration jobs are executed when you connect a server to Cycleops. One deployment creates a number of jobs equal to the number of targets that one setup is applied to.

To start using Cycleops, you must have your own server infrastructure since we do not offer computing infrastructure. If you need access to computing infrastructure, you can consider the AWS Free Tier.

Yes, as a matter of fact, you can connect any self-managed server you want to use as a deployment target in Cycleops, as long as the server provides SSH access.

Bare metal, cloud servers, or VMs are equal citizens to Cycleops deployment automation!

Yes, provided that you can connect one Internet facing server as the jump host. However,  if you don’t have any server that Cycleops can establish an SSH connection to over the Internet, you won’t be able to use Cycleops.

Once you have created the jump host for your Cycleops account, all new host registrations and setup deployments run through that jump host.

Every deployment counts in your jobs’ usage. The number of jobs per deployment is counted as the number of hosts you deploy in a single setup.

Here’s an example of a job usage:

Suppose your application requires 3 setups

  •  – one for the database container,
  •  – one for the application containers group, and
  •  – one for the web server container.

If you deploy 3 setups to one target host, your job usage would be:
 3 setups * 1 host = 3 jobs

If you deploy 3 setups to two target hosts, your job usage would be:
3 setups * 2 hosts = 6 jobs

Keep in mind that registration jobs do not count in the jobs’ usage. Registration jobs are executed each time you connect your servers with Cycleops.