The bmannconsulting.com website
bmann.ca
1---
2link: https://buildpacks.io/
3title: Cloud Native Buildpacks
4---
5A standard under the [[CNCF|Cloud Native Computing Foundation]]
6
7## What We Do
8
9Cloud Native Buildpacks (CNBs) transform your application source code into container images that can run on any cloud. With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles. This makes it easier to know what is inside application images, enforce security and compliance requirements, and perform upgrades with minimal effort and intervention.
10
11## Our Origin Story
12
13**Buildpacks** were first conceived by [[Heroku]] in 2011. Since then, they have been adopted by Cloud Foundry and other PaaS such as Google App Engine, Gitlab, Knative, Deis, Dokku, and Drie.
14
15(image of Heroku v1, Pivotal and Heroku v2, and then Pivotal + Heroku agreeing on current Cloud Native Buildpacks)
16
17The **Cloud Native Buildpacks** project was initiated by Pivotal and Heroku in January 2018 and joined the [Cloud Native Computing Foundation](https://www.cncf.io/) in October 2018. The project aims to unify the buildpack ecosystems with a [platform-to-buildpack contract](https://github.com/buildpacks/spec/blob/main/buildpack.md) that is well-defined and that incorporates learnings from maintaining production-grade buildpacks for years at both Pivotal and Heroku.
18
19Cloud Native Buildpacks embrace modern container standards, such as the OCI image format. They take advantage of the latest capabilities of these standards, such as cross-repository blob mounting and image layer "rebasing" on Docker API v2 registries.