Build on BTP/BAIP

Build on BTP/BAIP

Before you build, check what is there. If you find something close, think about contributing to it. If you find nothing, start building.

Guidance, not rules. Each project's own contributing guide wins. Links read 2026-09-29

01Check what is there

Search by the use case, not by a package name: the same need often sits under a capability you would not guess. The capability map and Browse hold everything in BTP/BAIP.

02Found something? Contribute

Where an artifact does most of what you need, a fix, a test or a page of documentation reaches everyone who already uses it. Read where it stops and its open and closed issues first: someone may have asked already. Then contribute to a project. These are the places where evidence or a second hand counts most.

Not known yet

One artifact stands

03Nothing there? Build

Use cases no recorded artifact covers, and capabilities with no artifact in BTP/BAIP. Unmapped means the atlas holds nothing, not that nothing exists: search once more, then build a reusable deployment.

Use cases nothing covers

Every assessed use case in BTP/BAIP has an artifact that covers it.

Capabilities with no artifact

No capability is unmapped in BTP/BAIP.

04Read in the atlas

CI/CD pipelines4
  • DevOps with SAP BTP2025-06-06
  • SAP BTP Showcase – SAP Continuous Integration and Delivery (SAP CI&D) for SAP HANA Cloud2021-01-27
  • Explore version control and automation with GitHub in Cloud Integration
  • Get Started with an SAP Cloud Application Programming Model Project in SAP Continuous Integration and Delivery
NextContribute to a project