# Build an internal platform your developers will use

Kitecorp builds internal developer platforms that teams adopt without being told to: a golden path from repository to production, self-service environments, and a platform team small enough to keep it that way. The measure is adoption, not features.

Canonical: https://kitecorp.org/services/platform-engineering

## What does a platform engagement deliver?

A golden path: the one well-lit route from a new repository to a running service in production, with the pipeline, the environment, the observability and the on-call wiring included, so a team ships its first service in a day rather than a quarter. Self-service for the things teams wait on today: environments, databases, secrets, DNS. A thin platform layer on Kubernetes or managed containers that hides the parts of the cloud nobody needs to see. And the operating model for the platform team: what it owns, what it refuses to own, and how it measures itself.

## What is a golden path, and why does adoption matter more than features?

A golden path is the default way to do the common thing. Not the only way, and not a mandate: a template, a pipeline and a set of modules that make the right choice the easy one. Teams take it because it is faster, and they stay on it because every upgrade (a new base image, a security patch, a cost fix) arrives for free.

Adoption is the only measure that matters because a platform nobody uses is a cost with no return, however elegant. We instrument adoption from the first week: which teams use the path, which parts they bypass, and why. The bypasses are the backlog.

## How does the platform stay small?

By refusing work. A platform team that owns every team's deployment ends up as the bottleneck it was created to remove. The team we help you set up owns the paved road and its tooling, publishes the contracts, and leaves the services on it to the teams that build them. New requests go through one question: does this make the common path faster for most teams, or is it one team's special case? The special cases get documented escape hatches, not platform features.

## Which tools do we work with?

Kubernetes (EKS, GKE, AKS) or the cloud's managed container services for the runtime. Argo CD or Flux for delivery, GitHub Actions or GitLab CI for pipelines, with self-hosted runners where cost or network access requires them. Terraform, Ansible and Kite for infrastructure as code. Backstage or a simpler catalogue where a portal earns its keep. The stack follows what your teams already know; the platform's job is to make it boring.

## How does an engagement run?

A discovery call to understand the teams, what they ship and what they wait on. An assessment of the current paths and a design for the golden one, with the first two or three teams who will walk it. The build, with your platform engineers, measured by adoption from the first week. A handover with the operating model, the backlog of bypasses and the runbooks. Pricing follows the discovery call, once we know the scope.

## Frequently asked questions

### Is a platform team worth it for a company our size?

Once more than a handful of teams ship to the same infrastructure, yes: the duplicated pipelines and one-off environments cost more than two platform engineers. Below that, a well-documented golden path without a dedicated team is usually enough, and we say so.

### Do we need Kubernetes for a developer platform?

No. The platform is the paved road, not the container scheduler. We have built golden paths onto managed containers and plain virtual machines when that was what the team could run.

### What makes developers adopt a platform?

It is faster than what they did before, on the first day, for the thing they do most. Everything else is secondary.

### Do you work with our existing team?

Yes. Every engagement is delivered with your engineers and ends with a handover, runbooks and alerts they own.

### How do we start?

Send a message through the contact page. We schedule a discovery call, agree the scope, and pricing follows what we find.

## How to start

Send a message at https://kitecorp.org/contact or email admin@kitelang.cloud. Pricing follows a discovery call.