Skip to content

Kubernetes · Cloud infrastructure · FinOps

We work on the platformyou already run.

Kubernetes, CI/CD and cloud infrastructure — operated, tuned and documented by engineers who measure the result. There is no platform to adopt, no rewrite, and we never ask for administrator credentials.

  • read-only by default
  • scoped and priced before start
  • senior engineers do the work
  • we build MetrixForge
AWSAmazon EKSGKEHetznerKubernetesKarpenterCluster AutoscalerHelmCiliumTerraformOpenTofuArgo CDFluxGitHub ActionsGitLab CIPrometheusGrafanaOpenTelemetryVictoriaMetricsVelero

Services

What we do

Nine things, each one something we have done end to end. Engagements are scoped and priced before they start.

All services

Proof

What we can show instead of a logo wall

Read-only

by default

An agent in the cluster and a read-only cloud role. Nothing is changed without an explicit, reviewable action — and platform vendors that provision for you need administrator rights to do their job.

−73%

on a claimed saving, after review

One recent audit: detectors summed to a headline figure, and reconciling overlaps cut it to a defensible range roughly a quarter of the size. We narrow the number before you see it, because a figure your engineer can break in one meeting is worth less than no figure.

25min

total downtime, 18 → 5 RDS instances

A payment-adjacent platform allowed two maintenance windows of fifteen to twenty minutes on separate days. Everything else happened under live traffic.

Read how it was done

How it runs

How an engagement runs

The same four steps whether it ends in a document or in an ongoing arrangement.

  1. A 30-minute call

    What you run, what hurts, and whether a diagnostic would tell you anything you do not already know. If it would not, we say so on the call and that is the end of it.

    You get: the list of read-only accesses a diagnostic needs

  2. Read-only inventory

    A read-only role and, where it helps, a metrics agent. Two weeks of measurement before any change, so the plan starts from what runs, not from what the diagram says.

    You get: a read-only inventory and fourteen days of measured data

  3. A plan with a price

    What we would change, in what order, what it costs and what we will not touch. Fixed scope, priced before it starts.

    You get: a plan with a price and the order of work

  4. Operate, or hand it over

    A standing arrangement with a monthly written summary — or infrastructure as code, runbooks and decisions left in your repository so your team carries on without us.

    You get: the monthly summary while we operate; at hand-over, infrastructure as code, runbooks and decisions in your repository

Fit

Who this is for

Three things make an engagement work. If one of them is missing we would rather say so on the first call.

  • Production Kubernetes — EKS, GKE, Hetzner or self-managed — without a dedicated platform person
  • For cost work, a cloud bill from roughly $5k a month — below that an audit returns less than it costs in attention, and we say so
  • A team able to grant read-only access and about an hour of an engineer's time

Not for: application development and integrations, a round-the-clock operations desk, certification projects.

Not sure? Sixteen intake questions, most of them one click

Engagements

Ways to work with us

Four shapes, from a free fortnight of measurement to running the platform. Each one ends in something you keep.

Day-2 running of the clusters you already have: upgrades, capacity, autoscaling and the reliability work nobody schedules.

  • Upgrades planned against the provider's support window and rehearsed first.
  • A monthly written summary of what changed and what it cost.
  • Changes arrive as a pull request you review, not as a controller acting at 3am.

What you get

A platform that keeps working, and a record of why it looks the way it does.

Time and price: Month by month · a written summary each month · Either side can end it with 30 days' written notice.

Kubernetes management

Why Kernforce

Four ways to buy this work

We are one of them, and not always the right one. Here is the honest shape of the alternatives.

Access required

Kernforce
Read-only, plus a metrics agent you can remove
Platform vendor
Administrator rights, to provision on your behalf
Staff augmentation
Whatever your own engineers hold
Large consultancy
Varies by engagement

What you keep afterwards

Kernforce
A document, IaC in your repo, runbooks
Platform vendor
A subscription and a dashboard login
Staff augmentation
Whatever was written down at the time
Large consultancy
A deck and a report

Pricing model

Kernforce
Scoped and priced before the work starts
Platform vendor
Per cluster or a share of the savings claimed
Staff augmentation
Per person, per day
Large consultancy
Per phase, scoped after discovery

Who does the work

Kernforce
Senior engineers on our team
Platform vendor
A controller in your cluster
Staff augmentation
Whoever is available
Large consultancy
Usually not the person who sold it

Lock-in

Kernforce
None — there is nothing of ours to adopt
Platform vendor
The platform becomes part of your control plane
Staff augmentation
None
Large consultancy
None, beyond the contract

The number you are given

Kernforce
Reconciled first, and usually smaller than the tool's
Platform vendor
Summed across detectors
Staff augmentation
Not applicable
Large consultancy
Modelled, then presented

Our tooling

MetrixForge, the instrument we measure our work with

We develop MetrixForge, a platform for measuring Kubernetes cost, efficiency and risk: agents that collect metrics and scan images, an analytics layer over the result, and recommendations that can be applied as a reviewed pull request against your own repository.

metrixforge.io

By the numbers

Commitments, not marketing figures

Each of these restates something written in full elsewhere on the site. If one changes there, it changes here.

14days

of measurement before a number

0

administrator credentials requested

1

written summary of changes, every month

30days

notice to end ongoing operation, either side

Questions

The ones we actually get

Who actually does the work?

A small team of senior engineers. The first call may be with a technical specialist, and the engineers on an engagement can change — someone is ill, someone leaves. That is why the work is written down as it happens, in your repository: the changes you reviewed, the runbooks and the decisions. Whoever picks it up starts from the record you already hold.

What does ongoing operation include?

Upgrades planned against the provider's support window and rehearsed first, capacity and autoscaling reviews, an on-call path, and a monthly written summary of what changed and what it cost. Changes arrive as a pull request you review, not as a controller acting at 3am.

Do you take on-call?

P1 — production down or degraded for users — is acknowledged within 30 minutes in working hours, 09:00–18:00 CET, Monday to Friday. P2 within 2 hours. Nights and weekends: P1 only, and only under a written on-call arrangement priced separately. Planned absences are announced in advance and written into the agreement.

Do we have to adopt your platform?

No. There is nothing to migrate onto. We build MetrixForge and use it to measure, but the deliverable is a document and changes to your own repository — not a dependency on us. The agent is the one optional piece, and removing it removes nothing you keep.

Do you work with our existing CI and GitOps tooling?

Yes — that is the premise. Pipelines get measured before anything is rewritten, and GitOps delivery is set up so git keeps describing what actually runs. There is no platform of ours to migrate onto.

All questions

Tell us what is running and what is bothering you.

A first call is a conversation, not a discovery questionnaire. If a short engagement is the right answer we will say so; if you do not need us yet, we will say that too.