Platform Overview
Architecture
Foundational
BP Portal Ecosystems #
BuildPiper is organised into three distinct portals, each tailored to specific organisational roles and operational stages — from infrastructure setup and software delivery to executive-level governance and analytics.
Overview #
BuildPiper’s portal architecture is purpose-built to match the way real organisations operate. Rather than forcing every stakeholder into a single interface, it separates concerns cleanly — each portal is scoped to the responsibilities, workflows, and decision-making authority of the people who use it. This ensures the right teams have access to the right capabilities at the right stage of the software delivery lifecycle.
⚙️
Admin Portal
Day 0 operations, infrastructure onboarding, and global platform configuration.
DevOps & Platform Teams
🚀
User Portal
BAU operations, CI/CD pipelines, deployments, and microservice lifecycle management.
App & Delivery Teams
📊
Insights Portal
Governance, compliance, DORA metrics, and organisation-wide engineering analytics.
Executive Leadership
1
Admin Portal
Day 0 Operations · Infrastructure · Platform Configuration
👥
Target Audience
DevOps Engineers, Platform Teams, CISO & Support Teams.
🎯
Primary Function
Focuses on Day 0 Operations — the foundational setup work that must happen before any application team can begin building or deploying. This includes infrastructure onboarding, artifactory repository configurations, container repository configuration, and network and domain whitelisting within BuildPiper.
Key Activities #
▸
Infra Onboarding
Provisioning and managing Kubernetes clusters and compute resources.
▸
Third-Party Integrations
Connecting essential tools like Registry, Jira, Slack, and security scanners.
▸
Platform Configuration
Defining global guardrails, environment settings, and access policies.
2
User Portal
BAU Operations · CI/CD · Deployments · Service Lifecycle
👥
Target Audience
Application Teams, QA Teams, Release Managers, and Technical Leadership (CTO / CISO).
🎯
Primary Function
Manages BAU (Business-As-Usual) Operations. This is the primary workspace for the software delivery lifecycle — from writing code and triggering builds to managing complex deployment strategies and monitoring live services.
Key Activities #
▸
CI/CD Management
Orchestrating builds and managing complex, multi-stage deployment strategies.
▸
Continuous Delivery
Handling production rollouts and environment-specific controlled releases.
▸
Service Lifecycle
Monitoring the health, performance, and availability of active microservices.
3
Insights Portal
Governance · Analytics · DORA Metrics · Compliance
👥
Target Audience
Executive Leadership — CEO, CISO, VP of Engineering, and senior management.
🎯
Primary Function
Provides high-level Governance and Analytics. It serves as a central hub for organisation-wide visibility, enabling leadership to track engineering maturity, enforce compliance, and make data-backed decisions without needing to navigate operational tooling.
Key Activities #
▸
Compliance & Security
Identifying which teams are meeting security protocols and regulatory standards.
▸
Maturity Metrics
Tracking the evolution of DORA metrics, code quality, and engineering practices across business units.
▸
Developer Productivity
Analysing DORA metrics and team efficiency to drive data-backed decision-making.
Stakeholder–Portal Matrix #
The table below maps each stakeholder group to their primary portal and the core activities they perform within it.
Stakeholder Group
Primary Portal
Key Activities
⚙️
Platform Engineering
Admin Portal
Cluster / VM onboarding, global integrations, system health monitoring.
🚀
Application Delivery
User Portal
CI builds, CD deployments, step catalog, application monitoring.
📊
Executive Management
Insights Portal
Velocity tracking, compliance audits, maturity metrics, DORA analytics.
📘 BuildPiper Documentation · Portal Ecosystem
Last updated: March 2026
