Cloud Native Buildpacks
Cloud Native Buildpacks (CNBs) transform application source code into OCI-compliant container images that can run on any cloud, without requiring Dockerfiles. Initiated by Pivotal and Heroku in January 2018, CNB joined the CNCF as a Sandbox project in October 2018 and GRADUATED on 11 August 2026, the foundation's highest maturity tier. It is licensed Apache-2.0. CNB is primarily a specification project: three independently versioned contracts — Buildpack API 0.12, Platform API 0.15 and Distribution API 0.3 — plus reference implementations (the pack CLI and the lifecycle). It centralizes container expertise through composable buildpacks, enables layer rebasing for efficient OS updates, and generates Software Bills of Materials in CycloneDX, SPDX and Syft formats. The pack CLI, the kpack Kubernetes operator and the public Buildpack Registry API are the primary integration points.
Cloud Native Buildpacks publishes 7 APIs on the APIs.io network, including Kpack API, and 6 more. Tagged areas include Cloud Native Buildpacks, Build Tools, CI/CD, Cloud-Native, and CNCF.
Cloud Native Buildpacks’ developer surface includes documentation, engineering blog, CLI, authentication, changelog, API reference, getting-started guide, and 41 more developer resources.
Kin Score
APIs 7
Individual APIs this provider publishes, each with its own machine-readable definition.
Buildpack API Specification
The Buildpack API is the contract between a buildpack and the lifecycle. It defines the detect and build executables, layers, build-plan provisions and requirements, and image e...
Platform API Specification
The Platform API is the contract between the CNB lifecycle and a platform such as pack, kpack, or a CI runner. It defines how builders, stacks, run images, and inputs are passed...
Distribution API Specification
The Distribution API specifies how buildpacks and builders are packaged as OCI artifacts, signed, and distributed through OCI registries. It also covers how meta-buildpacks comp...
pack CLI
pack is the reference command-line interface for Cloud Native Buildpacks. It implements the Platform API to build OCI images from source on a developer's workstation, manages bu...
CNB Lifecycle
The CNB Lifecycle is the reference implementation of the Buildpack and Platform APIs. It runs the detect, analyze, restore, build, export, and rebase phases used by all CNB plat...
Buildpack Registry
The Cloud Native Buildpacks registry indexes published buildpacks for discovery and reuse. It mirrors metadata for buildpack packages stored in OCI registries and exposes a brow...
Cloud Native Buildpacks Kpack API
The kpack API from Cloud Native Buildpacks — 25 operation(s) for kpack.
Scroll for all 7
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Buildpacks Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Buildpacks Finops
FINOPSFeatures 5
Notable capabilities this provider offers.
pack build
pack builder
pack rebase
pack sbom download
Buildpack Registry
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 4
What developers build with this provider.
App Developer Image Building
Platform Operator Integration
Buildpack Authoring
OS-Level Security Patching
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 8
Status, limits, changes, and where to get help
Scroll for all 8
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.