Audience: platform engineers, internal-platform and DevEx teams, and SREs who stand up and operate IntegraCI on behalf of the developers who self-serve on top of it. You are the people who define the paved road, not just walk it.Outcomes — after this course you can:Author and modify golden paths so teams start from a known-good template with CI, security steps, and ownership wired in.Wire your organisation's CI, scanners, registries, and clouds in through the connector marketplace, and scope what each tenant can use.Write policy as code and set the guardrails that gate onboarding and deploys, versioned and tested like any other code.Explain and verify how database-enforced (RLS) tenant isolation keeps tenants apart, and what platform engineers own around it.Set up deploy targets, read GitOps drift against the live cluster, configure gated promotion of signed and scanned builds, and generate progressive delivery configurations.Run the platform after you ship it: DORA dashboards, SLOs, incidents, runbooks, observability, and cost.Time: about 8 to 10 hours of self-paced study, plus the hands-on labs.Prereq: ICA recommended. You should already understand the four pillars, the SDLC, the connector model, governed AI, and tenant isolation in concept. ICPE takes you from understanding them to operating them. IntegraCI · tags professional, icpe, platform-engineering.A note on what the platform does: IntegraCI is a control plane. It generates manifests, CI steps, and configurations, delegates execution to your connectors, CI runners, and Kubernetes controllers, and records and gates on the results. As a platform engineer you are wiring and governing that control plane, not turning it into a build farm. Keep that distinction in mind through every module.
Know More