Questions
The ones we actually get
AWS and Kubernetes wherever it runs — EKS, GKE, Hetzner, self-managed. Not Azure. Everything below is answered here and linked to the page that states it in full.
Working with us
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.
How fast do you reply?
A reply from an engineer, usually within one working day. If a call helps it is a conversation, not a discovery questionnaire.
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.
What if we leave?
Either side can end it with 30 days' written notice. What you already hold stays: the repository, runbooks and decisions. What we hand over on the last day is the access list to revoke and the last monthly summary. Nothing we set up needs us to keep running.
Access and security
Do you need administrator access?
No, and we will not ask for it. A read-only role in the billing account, and optionally a metrics agent in the cluster with read-only Kubernetes RBAC and no privileged containers. Anything that changes a resource happens as something you review and approve.
What can a read-only role see?
Configuration, metadata and billing: what exists, how it is set up and what it costs. It cannot read the rows in your databases, the objects in your buckets or your source code, and it cannot change anything.
Is this a security audit?
No. We keep a security baseline on the platforms we operate, and we report posture findings the inventory passes over. That is not a pentest, not certification preparation and not an audit trail.
Formats, time and price
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.
How long does each format take?
Free diagnostic — No cost · about three weeks, of which fourteen days of measurement. Fixed-scope audit — Fixed price, quoted before start · fourteen days of measurement inside it. Consulting hours — By the day · a window agreed with the question. Ongoing operation — Month by month · a written summary each month · Either side can end it with 30 days' written notice.
Is the diagnostic really free?
Yes, and the document is yours whether you hire us or not. It is one estate — one payer account and the clusters attached to it. Anything larger stops being a diagnostic and becomes a quoted engagement, which we say before starting rather than after.
What if the defensible saving turns out to be small?
Then the report says it is small. We would rather lose the follow-on engagement than hand over a figure that falls apart in your first internal review — on the last estate we reviewed, reconciling overlaps removed roughly three quarters of the headline number.
Will optimisation hurt performance?
We measure fourteen days of requests against use at the percentiles before proposing a change, and the plan says raises as well as cuts. A change that would move a p95 is written down as such, and you decide.
Scope
Which clouds and clusters?
AWS and Kubernetes wherever it runs — EKS, GKE, Hetzner, self-managed. Not Azure.
What do you not do?
Application development and integrations, certification preparation and pentesting, and Azure. Each one is listed with the nearest thing we do instead.
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.
Something not answered here?
A reply from an engineer, usually within one working day.