Platform Engineering

Home /
Categories /
Platform Engineering

Your IDP is the face of your organisation, not a scaffolding tool

Internal Developer Platforms — Backstage being the obvious one — usually get sold on bootstrapping: click a template, scaffold a new service, get a repo with CI already wired up. That’s a nice party trick. It’s also the least interesting thing an IDP does, because you scaffold a service maybe a handful of times a year.

From commit to production: how Kargo completes the GitOps flow

Most teams that adopt GitOps end up with two-thirds of a delivery pipeline. CI builds and pushes an image. Argo CD reconciles the cluster to whatever is declared in Git. Both halves are solid. But the bit in the middle — moving a change through dev, staging and production, with checks at each step — is almost always a pile of bespoke scripts, manual pull requests, and “just bump the tag in the prod values file.” That’s where Kargo comes in.

GitOps your cloud infrastructure with Crossplane and Argo CD

Most teams already deploy their applications with GitOps: the desired state lives in Git, and a controller like Argo CD reconciles the cluster to match. So why is the infrastructure underneath those apps still provisioned by someone running Terraform from a laptop — or worse, clicking around a cloud console at 2am?