// platform engineering · malmö, sweden
The golden path your developers will actually want to use
We build internal developer platforms that shorten lead time instead of adding process: Backstage, ArgoCD, Crossplane and Terraform, wired into the way your teams already work.
▸ ci pre-wired
▸ dashboards included
→ main
tag v1.7.0
reconcile loop
drift corrected
// what we do
From scattered scripts to a supported path to production
Hands-on engineering inside your team. We ship real services onto the platform while we build it, so adoption is proven rather than assumed.
Golden paths
A paved road from repository template to running production service: scaffolding, CI, deployment, observability and on-call wiring included by default.
Developer portal
Backstage set up as a real catalogue: ownership, dependencies, scorecards and self-service templates instead of a wiki nobody updates.
GitOps delivery
ArgoCD or Flux with environment promotion, progressive delivery and rollbacks that are boring on purpose.
Infrastructure as a product
Terraform and Crossplane modules with sane defaults, so teams can request a database or queue without filing a ticket.
Platform operations
SLOs for the platform itself, cost visibility, upgrade cadence and a support model that keeps the platform team from drowning.
// architecture
How the pieces fit together
// engagement
How an engagement runs
- 01→DiscoverInterviews, lead-time mapping and a candid look at today's toil.
- 02→DesignTarget architecture, golden path definition and a thin-slice roadmap.
- 03→BuildWe implement inside your team, real services on the path, not a demo.
- 04→AdoptDocs, workshops and migration support until teams choose the path.
- 05Hand overOwnership, runbooks and a backlog your platform team can run alone.
// maturity
Where are you on the platform ladder?
Most teams we meet sit somewhere between level 2 and level 3. Knowing the next step matters more than jumping to the end.
Ad hoc
Every team wires its own pipeline. Deployments are tribal knowledge and lead time is measured in weeks.
Shared tooling
Common CI templates and Helm charts exist, but there is no ownership model and drift creeps in.
Golden path
A documented, supported route to production covers the majority of services. New services start on it by default.
Self-service
Teams provision infrastructure and environments themselves, within guardrails, without waiting on ops.
Platform as a product
The platform has users, SLOs, a roadmap and measurable impact on delivery performance.
// stack
Tooling we work with daily
// faq
Common questions
Do we need a platform team before we start?
No. Plenty of engagements start with one or two engineers who own delivery on the side. We help shape the team and the operating model alongside the technology.
Is Backstage always the answer?
No. Backstage is excellent when you have enough services to make a catalogue worth maintaining. Below that, a good template repository and clear docs often beat a portal.
How do you avoid building a platform nobody uses?
By migrating real services onto it while we build, and by measuring lead time and adoption from day one. If a team routes around the path, that is a design bug we fix.
// how we work
// contact
Tell us what you are working on and we will get back to you shortly.
A single review or a longer engagement inside your team. Both work for us.
office: Malmö, Sweden · uppdrag across Europe