Softwr

Cloud & Infrastructure · head to head

Chef vs GitHub

Chef logo

Chef

Cloud & Infrastructure

Infrastructure automation and management

From
Free
Rated
-
Full reviewWebsite
GitHub logo

GitHub

Technology

Where the world builds software

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Chef priced per node per year, at $59 on Business and $189 on Enterprise, so cost scales with fleet size rather than with team size; GitHub acquired by Microsoft in 2018, reducing pure independence despite operational autonomy
  • They diverge on capability: Chef covers Recipes, GitHub covers Git repositories.

Where they differ

Only the attributes on which Chef and GitHub actually diverge.

Attributes where Chef and GitHub differ
AttributeChefGitHub
Pricing modelopen-sourcesubscription
PlatformsLinux, Windows, Mac, ApiWeb, Desktop, Mobile
CategoryCloud & InfrastructureTechnology
Founded20092008

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Chef

  • Recipes
  • Cookbooks
  • Roles
  • Data bags
  • Attributes
  • Chef Server
  • Chef Infra
  • Chef Compliance

Only in GitHub

  • Git repositories
  • Pull requests
  • Code review
  • Issues & projects
  • GitHub Actions CI/CD
  • GitHub Pages
  • Security scanning
  • Dependency management

Both cover

  • AWS
  • Azure
  • Docker

What people use each for

The jobs each tool is most often brought in to do.

Chef

  • Configuration management and infrastructure automation across server fleetsnot GitHub
  • Enforcing compliance and audit policy on managed nodesnot GitHub

GitHub

  • Version controlnot Chef
  • Code collaborationnot Chef
  • CI/CD pipelinesnot Chef
  • Project managementnot Chef
  • Documentation hostingnot Chef

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Chef

  • Priced per node per year, at $59 on Business and $189 on Enterprise, so cost scales with fleet size rather than with team size
  • Tripling the price between the two published tiers puts compliance and audit features well above basic automation
  • Enterprise Plus and every self managed deployment are custom quoted with no published price

GitHub

  • Acquired by Microsoft in 2018, reducing pure independence despite operational autonomy
  • Primary focus on source control differs from purpose-built project management tools like Jira
  • Pricing for enterprise features and private repositories adds up compared to some self-hosted alternatives

Pricing, plan by plan

Chef

Free
  • Open SourceFree
    • Chef Infra
    • Community support
    • Full functionality
  • Chef Automate$4000/year
    • Chef Infra
    • Compliance automation
    • Insights

GitHub

Free
  • FreeFree
    • Unlimited public/private repos
    • 2,000 CI/CD minutes/month
    • 500MB package storage
  • Team$4/month
    • Everything in Free
    • 3,000 CI/CD minutes/month
    • 2GB package storage
  • Enterprise$21/month
    • Everything in Team
    • 50,000 CI/CD minutes/month
    • 50GB package storage

Which should you pick?

Choose Chef if

  • You need recipes.
  • You want to start without paying.
  • You work on Linux, Windows, Mac, Api.
  • You also want cookbooks.
Chef review

Choose GitHub if

  • You need git repositories.
  • You want to start without paying.
  • You work on Web, Desktop, Mobile.
  • You also want pull requests.
GitHub review

Questions people ask

Is Chef or GitHub better?
Neither clearly leads. Chef starts at Free and GitHub at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Chef or GitHub?
Chef starts at Free and GitHub at Free.
Does Chef or GitHub run on more platforms?
Chef runs on Linux, Windows, Mac, Api. GitHub runs on Web, Desktop, Mobile.
Can I use Chef for free?
Both have a free tier, so you can try either at no cost before committing.
What is Chef best used for?
Chef is most often used for configuration management and infrastructure automation across server fleets, enforcing compliance and audit policy on managed nodes. Of those, configuration management and infrastructure automation across server fleets and enforcing compliance and audit policy on managed nodes are not what GitHub is typically brought in for.
What can Chef do that GitHub cannot?
Chef covers Recipes, Cookbooks, Roles, Data bags. GitHub covers Git repositories, Pull requests, Code review, Issues & projects. Both handle AWS, Azure, Docker.

Answered from the vendors’ own pages

GitHub: What is a Git repository and how does GitHub use it?

A repository is the centralized database that stores the complete collection of files and folders for a codebase, along with the revision history. GitHub uses Git to provide distributed version control access to repositories with version tracking, branching, and collaboration features.

Source
GitHub: How does GitHub authentication work?

When you connect to a GitHub repository from Git, you need to authenticate with GitHub using either HTTPS or SSH. GitHub supports multiple authentication methods including passwords, personal access tokens, SSH keys, and GitHub Apps.

Source
GitHub: How long has GitHub been operating?

GitHub was founded in 2008 and launched publicly on April 10, 2008, making it the dominant git hosting platform for nearly two decades.

Source
GitHub: Who owns GitHub and when did the acquisition occur?

Microsoft acquired GitHub for $7.5 billion USD, with the deal announced June 4, 2018 and completed October 26, 2018. GitHub operates as an independent subsidiary within Microsoft.

Source
ShareXLinkedInRedditWhatsAppEmail

Related pages

More on Chef

More on GitHub

Keep looking

Other head to heads