Working with Cyclid

Cyclid was built to make testing easier – so it’s no surprise that we’re equally easy to work with.

It’s designed to be flexible, so you can add the functionality you need, and leave out what you don’t. What’s more, the same determination to understand and solve your CI problems also powers our support.

Cyclid grew from our belief that CI could be done better – and be more user-friendly. As developers, we’ve designed the kind of system that we’d want to use ourselves.

Here’s five reasons why:

  • Flexible With no pre-defined job structure, Cyclid gives you complete flexibility to build Continuous Integration jobs however you like. You define the Steps & Stages that your job requires, and you define how to run them.
  • Extensible From running a command during your CI job, to creating a cloud instance to run them in, Cyclid is built around plugins. Plugins are lightweight and easy to write, making it easy for you to add the functionality you need.
  • Agnostic From Containers to Clouds, Ubuntu to Fedora: it’s your choice. Cyclid is not tied to a single platform or operating system, and neither are you.
  • Open Source With the majority of the source code licensed under the Apache2 license, you’re free to use, review, extend and modify Cyclid yourself.
  • Operable Built by people with operations experience Cyclid is designed to be easy to install, easy to manage and easy to monitor.

We are here to help you do things better.

That’s why we built Cyclid.


Cyclid Jobs are free-form. You define Stages, Steps and Actions and you define how they are run with the Sequence.

Cyclid jobs are written in either YAML or JSON. They are composable so you can share common Stages between your jobs.

Every job is run in it’s own Build host, and every Build host is ephemeral. Cyclid is agentless so there’s no need for any dedicated, long running instances. Build hosts are only created when you run a job, saving your resources and money.


Almost everything is a plugin:

  • Actions that are run in your Job.
  • Sources that download your source code.
  • Builders that create Build hosts.
  • Provisioners that configure Build hosts.
  • API extensions that add functionality to Cyclid.

Plugins are lightweight and easy to write in Ruby.


Cyclid doesn’t tie you to any single platform or operating system. You can run your builds on anywhere there’s a Builder plugin for, and on any Operating System or distribution a Provisioner plugin exists.

Platforms include…




Red Hat
Enterprise Linux



Cyclid has been designed to be easy to install and manage. With a simple configuration file and sensible defaults it’s easy to manage your Cyclid server with Configuration Management. Alternatively we’ve made Docker images available, allowing you to create a fully functional Cyclid system in seconds.

Cyclid is designed to be a horizontally scalable with a share nothing design. All it needs is a database.

Open Source

The majority of the Cyclid source code is licensed under the Apache2 license, giving you the full freedom to use & modify Cyclid as you see fit, with no “gotchas” or complications.

Cyclid - CI the way you want it

Give Cyclid a try