There is one Chef Server, and it is Open Source

Chef is used by companies of all shapes and sizes, from tiny startups to the largest companies in the world, to create businesses where infrastructure moves as fast as software. One thing that binds all these different companies together, regardless of size, is this critical fact:

The people who build and manage infrastructure are the people who best understand the unique requirements that make their businesses special.

That means that, when it comes to deciding how infrastructure automation should work, in the end, the people who run the business are the experts. I may be great at using Chef to tackle all sorts of interesting problems, but how to apply that knowledge depends entirely on the unique requirements of that business.

It is this reality that is leading most of us to build the future of our businesses on Open Source software. We just aren’t interested in waiting for, or pretending, that a closed source vendor understands our needs better than we do. We know it isn’t true.

In the largest of organizations, there is another reason: they are tired of being locked in to relationships with vendors that are no longer providing real and lasting value. The era where we looked at doing perpetual software license deals, along with enormous consulting engagements so that experts could solve our problems for us, has passed. We know that it rarely works, and, importantly, we know that in the world we find ourselves today, these IT vendors just couldn’t possibly be experts in our problem. They don’t live in our proverbial houses.

Chef Software has evolved significantly in the six years since its founding. First, we had only our open source product; then, we launched our SaaS platform, Hosted Chef; and in response to the needs of our largest customers, we then built Enterprise Chef, an on-premises version of Hosted Chef. We’ve played with various mixes of what features go in to which offering, with how to balance our need to thrive as a commercial business with our core belief that Open Source is the future of infrastructure.

Through all of those permutations, we have learned one fundamental thing:

No matter what the mix of proprietary or open source features, when Chef users build awesome things with Chef, they are much more likely to buy our software.

It is in this environment that I’m proud to announce that, starting with the Chef Server 12 release candidate today:

There is only one completely free, fully Open Source, Chef Server.

This brings a number of benefits, both to Open Source Chef users and Enterprise Chef customers:

  1. Chef Server 12 includes the multi-tenancy and role based access control features of Enterprise Chef. Previously, choosing between Chef Server and Enterprise Chef meant making a decision early on about the value of those two features. If you needed them in the future, you were in for a migration between two similar but fundamentally different systems. On the flip side, as an Enterprise Chef customer, if those features brought you little value, you may feel “locked in” by the lack of easy migration back to a purely open source Chef Server.We want to make it easy and clear. We want you to build amazing things with Chef. We also want to make our commercial offerings so compelling that we earn your business every day. If we don’t, nobody is locked in to that commercial relationship. It’s better for everyone.
  2. As we have built other compelling offerings, such as our Reporting and Analytics platform, we tied them directly to Enterprise Chef. That meant that even if you felt like you might get great value out of those features, deciding to use them required a migration. We want to remove the friction to experimenting, to seeing if the things we build on top of Chef help you become successful. Every premium feature we ship is now available, for free, to people managing less than 25 nodes. They can be installed directly from the Chef Server console. For users who are larger than 25 nodes, you can try any of those features free for 30 days. If you exceed those limits, we’ll present a message to you – and we won’t turn the functionality off. You use Chef to build core infrastructure: we trust that you’ll do the right thing, and we trust that if you need to use more, you have a good reason. If those features stop bringing you value, you can turn them off just as easily as you turned them on.
  3. With Open Source Chef and Enterprise Chef being different products, there was a natural tension between which one would be getting attention at any given moment in time. Do we always ship them at the same time? Which gets priority for security releases? Which features go in where? As of this release, those tensions are gone. Every member of the Chef community, whether they are a customer of Chef Software or not, is equally invested in the same core platform. That will mean more frequent updates and innovation for everyone.
  4. When the beginning of a commercial conversation with Chef Software started with using Enterprise Chef, it became easy to see our business as selling an enhanced version of the Chef Server. In truth, it’s about the entirety of Chef – from the developer experience all the way through to your production infrastructure. In the last year, we’ve brought this to the forefront of our development. The Chef Development Kit is one example, where we build, support, and verify not only that Chef works well, but that all of the best tools from the Chef ecosystem do as well. Making companies successful means caring about everything, from the first moment someone starts typing to the moment they bask in the glory of a job well done. We’re committed to making more and more of our premium features work in the unique ways you employ Chef. As an example, in the future, we would love to see Chef Solo support within our Analytics platform. Just because you decided you didn’t need a server doesn’t mean you don’t want visibility into your infrastructure.

A picture is worth a thousand words

 Untitled

 

Chef Software now publishes and supports:

  • The Chef Development Kit, an open source collection of everything you need to get started writing cookbooks and building test-driven infrastructure.
  • The Chef Server, a fully multi-tenant, open source server that scales to store and distribute cookbooks and policy.
  • The Chef Client, an open source client that contains everything you need to automatically configure your infrastructure, with either local policy (Chef Solo) or from a Chef Server.
  • Chef Push, an open source, scalable push notification mechanism.
  • A premium Management Console that provides a Web Interface to the Chef Server, allowing you to set policy without writing code, and see reports of activity from the Chef Client.
  • A built-in framework for making the Chef Server highly available, on physical infrastructure and in the cloud. This premium feature includes support for DRBD, Amazon Web Services, and a pluggable ‘bring your own block device’ mode. We’ll be adding support for more providers all the time.
  • A premium replication service that makes it easy to publish content to a single Chef Server, and then have that content dynamically distributed to Chef Servers all over the globe.
  • Chef Analytics, a premium service that tracks all the activity in your Chef ecosystem – from resource updates to API calls, and provides visibility, notifications, and compliance. Our first release was in July, and we have big things planned.

All of our Open Source products are available, free of charge, in both source and binary form. Our premium features are free to use for infrastructures with 25 or fewer nodes, come with a 30-day free trial in larger infrastructures, and are available by subscription. In all cases, we know you use Chef for mission-critical infrastructure: if you exceed the usage limits, we will simply provide a gentle reminder, and trust that you’ll do the right thing.

We will continue to produce more Open Source software, and provide more compelling premium features, as well.

We are proud to be an Open Source company.

We believe that the future of infrastructure automation and more broadly, the future of how our businesses will be architected demands it. We know that when you are successful, Chef Software is too. This release fully aligns our business model with those realities: everyone is free to build their business on Chef, and it is our job to earn your business every day. It’s now as friction-free as we can make it to learn whether our premium features, such as the Management Console, Analytics, High Availability, or Replication bring you value.

We can’t wait to see what you build.

Where can I learn more?

* Check the Chef Server 12 Release Candidate blog post for specifics on how to install or upgrade the Chef Server.

* Learn about the new High Availability and Replication features.

* Check out our continuing commitment to making Windows automation delightful.

Author Adam Jacob

Adam Jacob is the CTO and co-founder of Chef.

  • Donald Guy

    Bravo! Humane and delightful move. :D

  • Tensibai Zhaoying

    Wow :) clap clap clap

    Really a pleasure to read this.
    Any insight on the pricing of the features or is it still a work in progress ?

    • Here are some details for you :)

      http://www.getchef.com/chef/#plans-and-pricing

      • Tensibai Zhaoying

        Thanks. I really hope there’ll be a per feature pricing.

        We have our own dashboards for an internal need based on a broken workflow in my point of view (the need is to report the version artifact_deploy has resolved and deployed on the run)
        The point is I can’t include Analysis feature as something adding value because we already spend time on this dashboard

        For now $6 by 12 by 400 nodes is quite expensive for the only need of a web-ui (even with RBAC included, it was already refused by my managers)

        So actually I’m stuck needing to rewrite a web-ui instead of being able to wrok on features or fixes as it sound cheaper in my managers point of view…

        I hope I do not sound rude, just exposing my case.

        • Nothing rude about it. We have a great sales team that can work with you to see what we can do. We have limits – like any company, we can’t just set prices arbitrarily on a per-customer basis (tl;dr, you run afoul of accounting and tax regulations if you do that.) But get in touch and we’ll see what we can do to help.

          • Tensibai Zhaoying

            Well, for now I do not even get the right to ask for a quote for two main reasons:
            Announced price would be around $28 800 per year for our infrastructure (servers only) and as we understood company’s needs we think we can’t have a pricing which could fit (but ok we should ask)

            There’s no clear information about other currency than $ or £… And our financial guys are frightened when it’s not euros…

            So I’ll try again to reopen this subject, but having some kind of extended pricelist in euros would help.

            Again a per feature pricing would be great and won’t be such a big deal to manage IMHO.

            At end, comments are maybe not the best communication media, but I’m pretty sure I’m not the only one sysadmin facing this problems.

            Edit: sent from a french phone, disregard any typo/spelling ;)

      • Joe Rocklin

        This is great news, but I’ll echo Tensibai: per-feature pricing would be a great addition to this. Large organizations likely already have some of the feature set covered, and justifying the full expense is challenging at best.

  • Sytse Sijbrandij

    Cool move, really awesome to open source the role based access.

  • zts

    This is all wonderful news, thankyou so much! In particular, having the RBAC feature everywhere is going to be transformational.

  • Dhruv Sahni

    Brilliant! Exciting times lie ahead

  • syxbit

    Excellent!

  • Brad Geesaman

    This is extremely timely news. I have a project that is small and really could benefit from the RBAC separation capabilities. Many thanks for this!

  • Jarlath Bloom

    Great to hear :) can’t wait to play around with the new version.

  • Michael Carruthers

    Brilliant, this is icing on the cake.

  • kritivagop01 .

    want to know how to do frsesh installation of chef version 12 to my vmware as a open source in standalone

  • Excellent news!

  • Philipp

    Ok I have created an organaistation and associated an user. How can I give the user admin rights to the organsisation using chef-server-ctl?

    • James Casey

      Hi Philipp, you can do this by using the ‘chef-server-ctl org-associate’ command to associate an existing user with an organization. Also, when creating an organization using ‘chef-server-ctl org-create’ you can associate a user at that point using the ‘-a USER’ option.

  • Dmitry Korzhevin

    Hi,

    Can you please comment this blogpost: https://coderanger.net/chef-open-source/

    Thank you

    • Charles Johnson

      In the months since his post, Noah (coderanger) has been working with CHEF to better clarify the governance of the Chef project. In particular, he’s helped us draft an RFC submission process that’s already producing excellent guidance and results.

      You can see all of this work in the open at:

      https://github.com/opscode/chef-rfc