Chef Server: Chef server stores your recipes as well as other configuration data. The Chef client is installed on each server, virtual machine, container, or networking device you manage—we’ll call these nodes. The client periodically polls Chef server latest policy and state of your network. If anything on the node is out of date, the client brings it up to date.
Chef Development Kit: The Chef Development Kit (Chef DK) contains everything you need to develop and test your infrastructure, built by the awesome Chef community.
Chef Analytics: See what’s happening on your infrastructure in real time. Integrate the data with your favorite external systems, such as Splunk or HipChat. Make changes at speed while ensuring infrastructure is policy compliant.
Management Console: Use the web-based management console to control access via RBAC, edit and delete nodes, and reset private keys. Keep up to date with what’s happening during Chef client runs.
High Availability: High availability protects you if your Chef server fails. Chef supports distributed replicated block devices (DRBD) and Amazon’s elastic block storage (EBS) volumes and the remapping of its elastic IP (EIP) addresses.
Replication: With replication, you can use a single Chef server as a central location for developing policy. Other Chef servers in other geographic areas periodically poll the primary for any changes. They stay current with your latest cookbooks, environments, roles and databags.
Hosted Chef: Let us manage your Chef server for you. Our hosted service is free for up to five nodes and it scales to any size you need.