# When a client project turns into Kubernetes, do you staff it, sub it out, or pass on it?

> We run that work as your subcontractor, under your contract and your name. Same engineers every time, everything in your repositories and your client's cloud accounts.

**In short.** Dixence runs Kubernetes builds and upgrades, Terraform, CI pipelines, cloud migrations and monthly platform maintenance as a white-label subcontractor for IT services firms and managed service providers. Your contract, your name, your invoice. Two or three named engineers every time, a fixed quote within two working days, everything in your client's repositories and cloud accounts.

Campaign page · For IT services firms and managed service providers · Language: English
HTML page: https://dixence.dev/en/partners/
Publisher: Dixence, a brand of Idempotent Ltd (Switzerland) · contact@dixence.dev

---

We run the Kubernetes work as your subcontractor. Your contract, your name, your invoice. Our engineers, seven hours ahead of your client.

- **2 to 3** named engineers on your account, every time
- **2** working days to a fixed quote on a live scope
- **15** engineering teams on stacks we maintain
- **~2x** what most firms resell our work at

## How it works

### Same people
Two or three named engineers on your account, every time.
### Your name
Your contract, your repos, your client's cloud accounts, your changelog.
### Your invoice
We invoice you, never your client. Most firms resell at roughly double.
### Your night
Our maintenance window is your client's night. They read the changelog in the morning, sent by you.

## What we cover

Kubernetes builds and upgrades, Terraform, CI pipelines, cloud migrations, and the monthly platform maintenance under your brand: patched stacks, CVE tracking across the upstream charts, the upgrade order, the written runbook.

## From your client's side, nothing changes

| What your client sees | What happens behind |
|---|---|
| Your logo on the statement of work | Our scope, written into your template |
| Your engineer on the call | Two or three named engineers behind your desk |
| Your name on the monthly changelog | Our maintenance window, seven hours ahead, before their day starts |
| Your invoice | Ours goes to you, never to them |

> The next proposal with a Kubernetes line in it: who on your bench prices it?

## How an engagement starts

1. **The white-label kit.** A sample monthly changelog you could send to a client tomorrow, and a statement of work template with our scope written in.
2. **One live scope, one fixed quote.** Send us a project you're deciding on right now. Fixed price in two working days, so you quote your client with a margin you know.

The facts a careful buyer checks are on one page: [what we can show you before you reply](/en/proof/).

## Two ways to start, lightest first
The kit by email, or one live scope for a fixed quote in two working days.

[Ask for the kit](mailto:contact@dixence.dev?subject=White-label%20kit)

## Questions we get asked

### Who does our client see?
You. Your logo on the statement of work, your engineer on the call, your name on the monthly changelog. We invoice you, never your client.
### How fast do you quote?
A fixed price in two working days on a live scope, so you quote your client with a margin you know.
### What work do you cover under our brand?
Kubernetes builds and upgrades, Terraform, CI pipelines, cloud migrations, and the monthly platform maintenance: patched stacks, CVE tracking across the upstream charts, the upgrade order, the written runbook.
### Where do the repositories and cloud accounts live?
With your client. Our maintenance window is your client's night; they read the changelog in the morning, sent by you.

## Who we are

A small Swiss team, engineers only. Fifteen engineering teams run on stacks we maintain, several of them through IT firms like yours. Dixence is a brand of Idempotent Ltd.