Below is a list of organizations and projects that have publicly adopted Paketo Buildpacks:
| Organization/Project | Description |
|---|---|
| Apcoa | Apcoa urban hubs uses paketo buildpacks for cloud native services to support different mobility needs. We are looking to expand our use of buildpacks with different type of functions and services used in our cloud platform. |
| Bloomberg | Bloomberg uses Paketo-based buildpacks for its internal platforms. |
| Doximity | Doximity is extending Paketo stacks and using ruby, go and nodejs buildpacks as the foundation of their internal platform |
| Fly.io | Paketo is one of the buildpacks options that Fly users can select from in flyctl. An example using the Go buildpack is available in the documentation |
| Greenhouse | Greenhouse uses the Paketo Python and NodeJS buildpacks to drive developer builds within our internal Platform as a Service. Switching to Paketo has been pretty seamless and saved us a ton of work. The support is great and we're able to supplement at times with small downstream buildpacks |
| Knative | Paketo buildpacks serve as the default method of converting a Knative function into an OCI container for deployment. The func CLI uses the pack Go library to programatically invoke a build, potentially applying additional buildpacks when doing so. |
| Porter | Porter supports Paketo buildpacks as an option for users to build and deploy their applications on Kubernetes without having to manually containerize them |
| Randoli | Randoli's App Director users can choose Paketo buildpacks to containerize their applications and then deploy them to any Kubernetes cluster straight from the UI |
| VMware | VMware uses Paketo-based buildpacks as the build phase implementation in several modern application platforms, including Tanzu Application Platform. |
There are two ways to do so:
- Add a comment to this Discussion including a brief description of your use case OR
- Open a PR adding yourself to
ADOPTERS.md