Simplifying Platform Engineering with DevOps-OS
A process-first talk on building improved developer experience workflows with open source building blocks.
Chennai FOSS 2026 · Apr 18
cloudenginelabs.io
DevOps-OS open source project
20 minute flow
What we will cover
01 · Mindset
Why DevOps starts with process, not tooling.
02 · DevOps-OS
Why this project exists and what problem it simplifies.
03 · Templates
How repeatable tech stack automation becomes reusable building blocks.
04 · Platform view
How templates evolve into platform engineering and IDP adoption.
Short talk · lightweight slides · practical framing
Ends with a live demo cue
Process-first understanding
DevOps is a workflow system before it is a toolchain
- Start with how code moves from idea to production. SDLC Process - Plan, Analyse, Develop, Build, Test, Deploy and Observe.
- Then define approvals, quality gates, deployment flow, and feedback loops.
- Only after that should tools and YAML enter the conversation.
When process is clear, automation becomes practical, repeatable, and easier to adopt.
Design the path first
Then automate the path
Why DevOps-OS
Process > tools
What teams usually do
Pick CI/CD, Kubernetes, GitOps, and SRE tools first — then struggle to connect them into one usable workflow.
What DevOps-OS encourages
Define the delivery process first — then scaffold the right starting configuration around it.
The project is not just about generating files. It is about making the first layer of platform workflow design simpler.
Less blank-page setup
More workflow clarity
Concept evolution
How DevOps automation evolves
Automation maturity: what starts as CI/CD scaffolding grows into a shared platform capability and then becomes a self-service developer experience.
Automation maturity
CI/CD template
Automates stack setup with repeatable pipelines, checks, and deployment defaults.
→
Shared capability
Platform Engineering
Turns repeatable setup into an internal capability that standardises delivery without slowing teams down.
→
Self-service layer
IDP
Exposes that capability through a usable interface so developers can consume it as a self-service experience.
DevOps automation starts as templates, matures into platform capabilities, and is consumed through an IDP.
Templates → capabilities → self-service
Map process with tools
Connect each stage to the right building block
1
Plan
Delivery intent, ownership, release expectations.
2
Build & test
GitHub Actions, GitLab CI, Jenkins scaffolds.
3
Ship
Kubernetes, deployment config, GitOps handoff.
4
Operate
Prometheus, Grafana, SLO, alerting foundations.
5
Improve
Template updates, reuse, onboarding, standardisation.
Process gives context
Tools implement the context
Templatisation
Turn stack-specific automation into reusable templates
Opinionated defaults
Encode a practical starting point for Python, Go, JavaScript, Java, or mixed stacks.
Consistency at scale
Teams stop rebuilding the same CI, GitOps, and SRE setup from scratch.
Faster onboarding
Developers consume a known pattern instead of reinventing delivery setup.
Templates are not shortcuts. They are packaged implementation experience.
Repeatable
Adaptable
Platform engineering
What is platform engineering?
- Creating shared internal capabilities that reduce delivery friction for product teams.
- Providing paved paths instead of one-off docs, tribal knowledge, or ticket-driven setup.
- Balancing standardisation, self-service, governance, and developer experience.
Not just infrastructure
Usable internal platforms
IDP
What is an Internal Developer Platform?
Experience layer
An IDP is how developers discover, request, and consume platform capabilities through a usable interface.
DevOps-OS angle
Templates become the portable building blocks behind that experience layer — ready to plug into self-service workflows.
Platform engineering builds the capability. IDP makes the capability consumable.
Capability + interface
Self-service with guardrails
Demo framing
Live demo: from template creation to platform consumption
Show creation
Create templates for CI/CD, deployment, or stack automation using DevOps-OS.
Show consumption
Explain how the same templates can power platform engineering workflows and future IDP experiences.
- Keep focus on the workflow story, not every command.
- Use the demo to show reuse, consistency, and developer experience.
Presenter cue slide
No deep walkthrough on screen
Wrap-up
Key takeaways
1
Process-first thinking makes DevOps automation more useful.
2
Templates help teams standardise without slowing developers down.
3
Platform engineering is about delivering reusable internal capabilities.
4
DevOps-OS can act as an open source building block behind that journey.
Thank you — Chennai FOSS 2026.
github.com/cloudengine-labs/devops_os
Use ← →, space, or click buttons
Slide 1 / 10