BP SSO and Login

Documentation Introduction

BuildPiper Introduction

BuildPiper is a full-scale app delivery platform — an enterprise-grade application delivery orchestrator designed to standardise the end-to-end SDLC.

Unified control plane for VM delivery, Kubernetes workloads, mobile apps, and database ops with built-in CI/CD and security automation.

BP Portal Ecosystems

From core infrastructure to executive-level analytics.

Read More >
BP Stakeholders

Powering a high-velocity, governed delivery lifecycle.

Read More >

Buildpiper (BP) supports multiple Single Sign-On (SSO) providers to provide secure and seamless authentication across the platform. It integrates with popular identity providers including Google OAuth2.0, Active Directory (AD) Authentication, GitHub OAuth2.0, GitLab OAuth2.0, Bitbucket OAuth2.0, and Microsoft OAuth2.0. These options allow organizations to use their existing identity systems, reducing the need to manage separate credentials and improving security. By leveraging OAuth2 and enterprise directory services, BP simplifies user access, strengthens authentication controls, and streamlines onboarding. Administrators can configure SSO from System Settings, ensuring compliance with organizational policies while delivering a consistent and convenient login experience for users

App level Job Templates

Last Updated: March 31, 2026

Application Pipelines

Last Updated: March 31, 2026

Artifactory

Last Updated: March 23, 2026

AskOlly

Last Updated: January 28, 2026

AskOlly – Proactive Failure Analyser. Immediate, actionable diagnostics the moment a failure happens. What is AskOlly? AI-powered failure analyser in BuildPiper—monitors CI/CD events/logs in real-time, detects anomalies, identifies root causes, recommends fixes from historical intelligence. Goes beyond alerts: explains failures and guides resolutions for faster MTTR. Why AskOlly? Solves: hours on logs, unclear causes, experience-dependent fixes,...

Asynchronous Design

Last Updated: April 1, 2026

BuildPiper (BP) is asynchronous by design, meaning job execution happens in the background through dedicated workers instead of blocking the main application flow.