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 SaaS version where they can be viewed and accessed by the Chef Habitat community and then shared to 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 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 Enterprise Components Include:
   
  -* **Application Manifest** - The Application Manifest provides a single application directory which includes at a minimum the compiled app artifact, dynamic links to all direct & transitive runtime dependencies and instructions to install and run the app.
  +* **Application Manifest** - The Application Manifest provides a single application directory, which includes---at a minimum---the compiled app artifact, dynamic links to all direct and transitive runtime dependencies ,and instructions to install and run the app.
   * **Deployment Channel Management** -  Pre-canned deployment channels that can be used as-is or a user can custom design their own channels. Apps that are deployed through Chef Habitat can subscribe to a channel and be auto-upgraded whenever the app is promoted.
   * **Origin Management** - origin stuff
   * **Content Library** - Hundreds of pre-built [application delivery packages](https://bldr.habitat.sh/#/pkgs/core) and core dependencies, which makes it easy to get started with Chef Habitat.
   * **Custom Data and Reporting APIs** - Rich APIs enable the capability to export to CSV or JSON.
  -* **DevOps Integration APIs** - it provides an API so that clients can find and download the necessary packages to run their applications. Additional APIs also enable easy integration with other popular DevOps tools including Jenkins, Terraform, Artifactory, Hashi Vault and many others.
  +* **DevOps Integration APIs** - it provides an API so that clients can find and download the necessary packages to run their applications. Additional APIs also enable easy integration with other popular DevOps tools, including Jenkins, Terraform, Artifactory, Hashi Vault, and many others.
   * **Role Based User Access** -
   * **Container Registry Support** -
   
   The Chef Habitat SaaS builder offers additional functionality including Automated Builds,
   
  -For more information on how the SaaS and On-Prem versions of Chef Habitat Builder work together read the blog - [Builder On-Prem Enhancements that Extend Support to Airgap Environments and Simplify Set-Up](https://blog.chef.io/chef-habitat-product-announcement-builder-on-prem-enhancements-that-extend-support-to-airgap-environments-and-simplify-set-up/)
  +For more information on how the SaaS and On-Prem versions of Chef Habitat Builder work together, read the blog - [Builder On-Prem Enhancements that Extend Support to Airgap Environments and Simplify Set-Up](https://blog.chef.io/chef-habitat-product-announcement-builder-on-prem-enhancements-that-extend-support-to-airgap-environments-and-simplify-set-up/)
   
   ## Compare Chef Habitat Builder and Builder on-prem
   
  
positive.code: 
  Creating an origin with the `hab origin create` command registers the origin on Chef Habitat Builder without creating an origin key pair. The `hab origin key generate` command creates the key pair and saves them in your local environment, but it does not upload either origin key to Chef Habitat Builder.
  
  * You can only upload new keys to origins in which your are an "administrator" or "owner".
  * Builder requires the public origin key to upload artifacts for that origin, so you'll need to upload it.
  * Builder requires the private origin key to enable new artifact builds from packages with plans linked to that origin.
  
  
negative.code: 
  Replacing <token> with the contents of your generated personal access token.
  
  You can also save your personal access token as a permanent environment variable using the Windows user interface. In your Windows help bar, enter `environment` and select **Edit the system environment variables** from the list of suggestions.
  
  This opens the `System Properties` window on the `Advanced` tab. Select the `Environment Variables` button.
  
  