anchor.diff:  ---
   # <a name="using-builder" id="using-builder" data-magellan-target="using-builder"> Chef Habitat Builder</a>
   
  -Chef Habitat Builder acts as the core of Chef’s Application Delivery Enterprise hub. Chef Habitat Builder was first launched as a cloud service and as the repository of all available plan templates built by Chef and the supporting community. Due to the fact that the application source code is stored alongside the build package, many users expressed a preference for storing packages and running the Builder on-premises. As a result, Chef Habitat Builder can be consumed either as a cloud based or on-premises solution. Plan files are stored in the Chef Habitat Builder SaaS, where they can be viewed and accessed by the Chef Habitat community and then shared with the on-premises version of the builder where they can then be copied and maintained locally.
  +Chef Habitat Builder acts as the core of Chef’s Application Delivery Enterprise hub. Chef Habitat Builder was first launched as a cloud service and as the repository of all available plan templates built by Chef and the supporting community. Due to the fact that the application source code is stored alongside the build package, many users expressed a preference for storing packages and running Chef Habitat Builder on-prem. As a result, Chef Habitat Builder can be consumed either as a cloud based or on-premises solution. Plan files are stored in the Chef Habitat Builder SaaS, where they can be viewed and accessed by the Chef Habitat community and then shared with the on-premises version of the builder where they can then be copied and maintained locally.
   
   ## Chef Habitat Builder Enterprise Components Include:
   
  
positive.code: 
  * When you build an artifact in your local environment, Chef Habitat signs the artifact with a public key
  * When you upload an artifact to Chef Habitat Builder or Builder on-prem, Chef Habitat verifies that the artifact was signed with its public key
  * When you install an artifact on a Supervisor, Chef Habitat uses the public origin key to authorize the artifact's installation; Chef Habitat only installs artifacts for which it has the public origin key
  * When you download an artifact to your local environment, Chef Habitat uses the public origin key to verify the artifact's integrity before it starts the installation
  
  Chef Habitat Builder origin key names follow the format:
  
negative.code: 
  ## <a name="builder-start" id="builder-start" data-magellan-target="builder-start">Get Started</a>
  
  Whether you are looking to leverage the SaaS or on-prem version of Chef Habitat Builder, you will need to create an account on the SaaS version of Chef Habitat Builder. After you have then downloaded the version, you will then sync the two accounts.
  
  This documentation covers everything from creating an account to setting up automated builds and exporting packages to a variety of container registries.
  
  
  ---
  ## <a name="builder-account" id="builder-account" data-magellan-target="builder-account">Get an Account</a>
  
  ### Prerequisites
  
  