Skip to main content


Latest Post

Posted on 3 years ago by Elle KElle K

Chef, the infrastructure automation platform, provides users with the ability to manage their server fleet no matter what the size. Offered both as an open source tool and as an enterprise edition, Chef's primary Chef server -- the master server from which users can work to create cookbooks -- is available both as a hosted offering and as a tool available for download and configuration on your own servers. It is the Chef server itself that can be privately- or Chef-hosted. Nodes will always be maintained on the user or company's own infrastructure -- whatever that infrastructure may be. The Chef server is what hosts cookbooks, roles, and node definitions. But what are the overall differences between the two ways to manage the Chef server?