Cinc Auditor vs Test Kitchen
Cinc Auditor
cinc.shTest Kitchen
kitchen.ciSide by side
| Figure | Cinc Auditor | Test Kitchen |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Infrastructure Testing Tools | 7.9 (#11) | 8.2 (#7) |
| License | Cinc says its binaries are licensed under Apache 2.0 and have no further EULAs or licensing. | The project is released under the Apache License 2.0. |
| Purpose | Cinc Auditor is a free distribution of Chef InSpec for compliance and audit workflows. | Test Kitchen is a test harness for executing infrastructure code on one or more platforms in isolation. |
Plans
In their own words
Cinc Auditor
Cinc Auditor is a free distribution of Chef InSpec for compliance and audit workflows on Linux, macOS, and Windows. Its profiles are fully compatible with upstream counterparts, and its tools work with InSpec; an InSpec wrapper redirects to Cinc Auditor so existing automation can keep working. Installation options include scripts, Bundler, RubyGems, and plain packages. Cinc also publishes a Docker Hub image as a drop-in replacement for chef/inspec. It can run InSpec-compatible profiles in CI or against containers, with GitLab CI and GitHub Actions named as examples. Auditor is included in Cinc Workstation. Cinc says its binaries use the Apache 2.0 license without additional EULAs or licensing. The project does not provide formal warranties or support, and it does not currently offer repositories for standard package managers such as yum or apt. The free plan costs nothing. Cinc recommends contacting Progress for warranty or support needs.
Test Kitchen
Test Kitchen is a free test harness for running infrastructure code in isolation on one or more platforms. Its workflow uses create, converge, setup, verify, and destroy commands to provision environments and test infrastructure code. Documented drivers cover Amazon EC2, Apache CloudStack, DigitalOcean, Docker through Dokken, Google Cloud Platform, Hetzner Cloud, Vagrant, Azure, Hyper-V, OpenStack, and VMware products. Which drivers are available depends on the driver gems installed in the Ruby environment. Provisioning options include Chef Infra, Cinc Client, Habitat, PowerShell DSC, and shell scripts; listed verification integrations include Cinc Auditor, Chef InSpec, and Serverspec. Community plugins add Ansible, Puppet, and Salt provisioners. Installation is available through RubyGems, system packages, or Cinc Workstation, but Test Kitchen itself does not bundle Cinc or Chef tooling. Requirements include a 64-bit operating system and enabled CPU virtualization. The project uses Apache License 2.0 and points users to Chef Community Slack for community assistance. The documentation notes known issues and no current maintainer for kitchen-docker, recommending kitchen-dokken instead.