---
# System prepended metadata

title: CNCF - Sandbox - Application

---


## Title

[Sandbox] Shipwright

## Application contact emails

> Provide the email address(es) of individuals who should be contacted regarding this application. If more than one email is provided, please comma separate them.

encalada@de.ibm.com
schwarzs@de.ibm.com
adam.kaplan@redhat.com

## Project Summary

> Provide a very brief, single line summary of the project.

An extensible framework for building container images on Kubernetes.

## Project Description

> Provide a brief, 100-300 word description of the project that explains what it does and why it's needed.

Shipwright is designed to make it easy to build container images securely and reliably. The community is rooted in the fundamental principles of simplicity, flexibility, and security. Shipwright is currently an incubating project under the Continuous Delivery Foundation (a subsidiary of the Linux Foundation).

 
This project introduces a layer of standardisation across many of today's build tools (_such as Kaniko, ko or Buildpacks_). By abstracting the complexity of today's build processes, Shipwright establishes a common layer within Kubernetes, that can work across multiple tools and runtimes.

In essence, Shipwright empowers developers and organisations to easily build container images, leveraging their preferred build tools with the confidence of adhering to security best practices. Shipwright extensible and pluggable nature, makes it an invaluable asset for integration into existing Kubernetes components or CI/CD systems.

## Org repo URL

> provide if all repos under the org are in scope of the application

https://github.com/shipwright-io

## Project repo URL in scope of application

> Provide the URL of the primary source code for the project. If there is no single repo but all repos under the org are in scope of the application, provide "N/A". If multiple repos (in addition to the primary repo) exist under an org, but not all are in scope, please enumerate in scope repos in the next question.

N/A

## Additional repos in scope of the application

> Provide the URLs of any additional repos for this project's application if appropriate.

N/A

## Website URL

> Provide the URL of the project's website. If the project has no website, please provide the primary repo URL again.

https://shipwright.io

## Roadmap

> Provide the URL of the project's roadmap.

https://github.com/shipwright-io/build/blob/main/ROADMAP.md

## Roadmap context

> You may optionally provide any details of the roadmap you feel are required for clarity.

_No response_

## Contributing Guide

> Provide the URL of the project's contribution guide. If the guide is embedded in another file, please deep link to the correct header.

https://github.com/shipwright-io/.github/blob/main/CONTRIBUTING.md

## Code of Conduct (CoC)

> Provide the URL of the project's code of conduct.

https://github.com/shipwright-io/.github/blob/main/CODE_OF_CONDUCT.md

## Adopters

> Provide the URL of the project's Adopters file. If no file exists, move on to the next question.

https://github.com/shipwright-io/build/blob/main/ADOPTERS.md

## Contributing or Sponsoring Org

>Provide the URL of the project's contributing or sponsoring company/organization. If no such company/organization exists move on to the next question.


https://www.ibm.com/
https://www.redhat.com/

Contributors are primarily employees from IBM and RedHat. Project Shipwright is already a vendor-neutral Linux Foundation Project, incubating inside the Continuous Delivery Foundation.

## Maintainers file

> Provide the URL of the project's maintainers file.

https://github.com/shipwright-io/build/blob/main/OWNERS

## Why CNCF?

> Why do you want to contribute the project to the CNCF? What value does being part of the CNCF provide the project? Provide detail on why you chose the CNCF that allows the TOC to consider alignment of expectations between the project and the ecosystem.

Shipwright is currently an incubating project within the Continuous Delivery Foundation (CDF). After further evaluation, we believe the project is more closely aligned with the CNCF. We are confident the CNCF will help us increase community contributions and adoption, and foster closer collaboration with our mutual project dependencies.

The goals of our project align with the CNCF Sandbox goals and with CNCF's mission by addressing key challenges in the Cloud Native space related to application delivery. Shipwright empowers organisations to build and run scalable applications in today's diverse cloud environments.

## Benefit to the Landscape

> How will adding this project benefit the CNCF landscape? What is the differentiator or enhancement this project provides to existing project, capabilities, or challenges within the landscape?

In the evolving landscape of today's Cloud Native ecosystem, developers encounter a multitude of build tools for creating container images. Project Shipwright addresses this variety by introducing standardisation across multiple CNCF build tools, promoting their adoption through an extensible declarative API accessible to both developers and organisations.

This standardisation can be consumed by other projects that aim to provide a unique experience when building and deploying applications, using Shipwright as a fundamental building block.

In addition, Project Shipwright aims to provide throughout the same declarative API, today's Supply Chain Security Best Practices.

## Cloud Native 'Fit'


> Please explain where you see the project "fitting" in the Cloud Native landscape. This should detail how the project is cloud native, which elements of cloud native the project embodies or exemplifies.

Shipwright is build with and for Cloud Native technologies, fitting into the Application Definition & Image Build category.

## Cloud Native 'Integration'

> What CNCF projects does this project complement or depend on, and how?


We complement the following projects:

- OpenFunction
    - How? 
        - Uses Shipwright as a Building Block
- Tekton
    - How?
        - Can integrate Shipwright inside a Tekton Pipeline, as the building block.

We depend on the following projects:

- ko
    - How?
        - Shipwright can use `ko` to delegate the mechanism of building a container image.
- Buildpacks
    - How?
        - Shipwright can use Buildpacks to delegate the mechanism of building a container image.
- Kaniko
    - How?
        - Shipwright can use Kaniko to delegate the mechanism of building a container image.
- Tekton
    - How?
        - Shipwright uses Tekton to achieve the sequential execution of containers inside a Kubernetes Pod, plus other Tekton features.

## Cloud Native Overlap

> What CNCF projects does this project overlap with, and how?

None.

## Similar Projects

> Please list similar projects in the CNCF or elsewhere. If none exist, provide "N/A".

N/A

## Landscape

> Are you already listed on the CNCF Landscape?

Yes.

## Business Product or Service to Project separation

> If this project is identical (name, features, etc.) or closely related to one or more products or services of the sponsoring company/organization(s), how do you plan to separate this project from any products in terms of organization and development? If it is not related to a product or service, just provide "N/A".

N/A

## Project champions

> Please list any people who are part of CNCF leadership (TOC, TAGS, etc.) who can endorse or answer questions about your project.


- Karena Angell
- Derek Carr

## Additional information

> Any additional information you would like the TOC to consider when evaluating this project?

Our decision to contribute the project to CDF was primarily driven by its integration with Tekton, Shipwright is built on Tekton, a CDF project since its inception. However, we anticipate that this association will become less influential over time, especially in light of Tekton's departure from CDF and the growing number of CNCF projects used by or that rely on Shipwright.
