Platform engineering and GitOps
Give development teams self-service environments, golden-path templates and GitOps delivery on Kubernetes, with security and standards built in, so they ship faster without waiting on tickets.
Make the right way the easy way
A Kubernetes platform pays off when development teams can use it without becoming Kubernetes experts. Platform engineering builds that layer: templates for new services, self-service environments, pipelines, and guardrails that keep everything secure and consistent.
We build internal developer platforms on Kubernetes and OpenShift with GitOps at the centre. Every environment and deployment is described in Git, and automation keeps the clusters matching it. Teams move faster, and the platform team stops being a queue.
When it fits
01
Tickets for everything
New environments, namespaces and pipelines wait in a queue for the platform team.
02
Every team does it differently
Each application has its own pipeline, deployment scripts and conventions.
03
Environments drift apart
Test and production differ in ways nobody can explain, so releases break.
04
Audits are painful
Proving who changed what, when and with whose approval takes days of digging.
What we do
Golden-path templates
Ready-made templates for new services, with code layout, pipeline, deployment, monitoring and security already set up.
Self-service environments
Teams create namespaces, databases and preview environments on demand, within quotas and policies.
GitOps delivery
Argo CD or Flux keeps clusters matching what is in Git, with pull-request approvals and a full history.
Developer portal
A portal such as Backstage or Red Hat Developer Hub, with a catalogue of services, owners, documentation and templates.
Policy as code
Kyverno or OPA Gatekeeper rules that enforce standards automatically and explain what to fix.
Multi-tenancy
Teams separated by namespaces, quotas, network policies and role-based access, sharing clusters safely.
GitOps
Git holds the desired state, and the platform keeps to it
Teams change the platform by changing Git. An agent applies each approved change to every cluster and puts back anything changed by hand, so environments stay consistent and every change has a record.
- Golden-path templates
- Teams start new services and environments from approved templates.
- Git, the desired state
- Every change is a reviewed, approved commit with a full history.
- GitOps agent
- Argo CD or Flux applies the changes to each cluster automatically.
- Clusters
- Development, test and production stay in step.
- Drift put right
- Changes made by hand are detected and reverted to match Git.
How we build a developer platform
01
Understand
Map how teams build, test and release today, and where they wait or repeat work.
02
Design
Agree the golden paths, tenancy model, policies and GitOps structure with your teams.
03
Build
Set up GitOps, templates, the portal and policies, and onboard a pilot team.
04
Roll out
Onboard the other teams in waves, measure lead time and adoption, and keep improving the paths.
What you get
- GitOps repositories, with Argo CD or Flux configured
- Golden-path templates for your main application types
- A developer portal with a service catalogue
- Security and standards policies, as code
- A tenancy model with quotas and access by team
- Measures of lead time, deployment frequency and adoption
Platforms and tools
- Argo CD
- Flux
- Backstage
- Red Hat Developer Hub
- OpenShift GitOps
- OpenShift Pipelines
- Tekton
- GitLab CI
- GitHub Actions
- Helm
- Kustomize
- Crossplane
- Kyverno
- OPA Gatekeeper
- External Secrets Operator
- HashiCorp Vault
Questions about platform engineering
Is platform engineering different from DevOps?
It builds on it. DevOps is how teams work; platform engineering gives them a shared, self-service platform, so each team doesn't have to build its own pipelines and tooling.
DevOps and automated deliveryDo we need a developer portal?
Not at first. Templates and GitOps deliver most of the value. A portal helps once many teams and services need a catalogue, owners and documentation in one place.
Argo CD or Flux?
Both are mature CNCF projects. Argo CD has a strong web interface and is included in OpenShift GitOps; Flux is lighter and suits teams that prefer the command line. We choose with you.
How do we keep secrets out of Git?
Secrets stay in a vault, such as HashiCorp Vault or your cloud's secrets manager, and are delivered to the cluster at run time. Git only holds references to them.
Give your developers a platform they want to use
Tell us how your teams build and release today. We'll show where self-service and GitOps will save the most time.