5 min read

White-label Partner Playbook

How to sell Kaphera Cloud into the white-label partner archetype: systems integrators and platform companies that want a managed connector offering under their own brand. The Think-it origin story is the proof point; the margin calculation and the steward-ownership / source-availability durability story are what close.

Jobs to be done

  1. When I see a market opportunity in managed connectors, help me launch an offering under my brand within a quarter, so I capture the window before competitors establish reference customers.
  2. When I need to offer my clients managed connector infrastructure, help me do it with margin I control, so this is a product, not a referral channel.
  3. When my clients ask what manages their connector, help me give them an honest answer backed by source code they can inspect, so I sell on transparency, not trust.
  4. When the platform provider’s terms or ownership change, help me retain the ability to operate independently, so my client relationships are not hostage to a dependency I cannot exit.

White-label stack

What partners license under their own brand: the platform layer plus the open-source EDC operators below.

flowchart TB
  subgraph BRAND["Partner brand"]
    CON["Cloud Console (source-available)"]
    SRV["Cloud Server (source-available)"]
    CO["Cloud Operator (source-available)"]
  end
  subgraph OSS["Open-source foundation"]
    EO["EDC Operator (Apache 2.0)"]
    EE["EDC Enablement Operator (Apache 2.0)"]
    DSP["DSP Data Plane (GPL)"]
  end
  CON --> SRV
  SRV --> CO
  CO --> EE
  EO --> EE
  EO --> DSP

Signal → Product map

When you hear the signal, sell the product. The justification tells you why that product and not another.

What you hearWhat to sellWhy this product, not another
”We want to offer managed connectors to our clients”kaphera-cloud-operator • kaphera-cloud-server • kaphera-cloud-console (white-label licence)The full stack under their brand. Cloud Operator for multi-tenant isolation, Server for API, Console for client-facing UI. They set the pricing. Not the managed platform, that’s Kaphera’s brand, not theirs.
”We don’t want to build a connector platform from scratch”White-label licence (full stack)6-12 months of specialised Rust + K8s engineering vs. weeks to launch on Kaphera. The build-vs-buy math is decisive. Not the open-source operators alone, those don’t include the organisational model or the console.
”We need to manage multiple client environments”kaphera-cloud-operatorThe Organisation CRD gives per-client namespace isolation. Each client = an isolated organisational context with its own networking, TLS, and identity. Not manual namespace management, declarative, operator-managed.
”Our clients care about what’s underneath”kaphera-edc-operator (Apache 2.0) + kaphera-cloud-server (source-available)The open-source EDC operator proves transparency. The source-available server and console mean their clients can audit the full stack. No other white-label option offers this, every competitor is proprietary.
”We want to operate on our own infrastructure”All 3 operators + kaphera-cloud-server • kaphera-cloud-console (on-prem licence)They run everything. Kaphera provides the software licence and engineering support. Full control. Not managed hosting, they want the product, not the service.
”Which dataspace profiles can we offer?”Connector profiles (MDS, Tractus-X)Pre-validated profiles mean the partner’s team doesn’t need to solve dataspace-specific trust anchor and credential work. Each profile they offer expands their addressable market without engineering investment.

Upgrade signals

  • Client count growing past 10 → operational support engagement. They’ll want Kaphera’s help managing the fleet.
  • Asking about additional dataspace profiles → each new profile expands their addressable market. Revenue expansion per client.
  • Wanting custom connector profiles for niche dataspaces → enterprise licence + engineering engagement.
  • Their clients need digital twin infrastructure → add kaphera-digital-twin-registry to the offering.
  • They want to offer the CLI or Terraform under their brand → [[kaphera-cli|kaphera CLI]] and kaphera-cloud-terraform-provider are Apache 2.0, they can ship them as-is or wrap them.

Objections & responses

ObjectionResponse
”What if you raise prices?""The licence terms are contractual and predictable. You set your client pricing independently. And the source-available licensing means you retain the ability to operate the stack yourself if terms become unacceptable."
"Our clients will just go to Kaphera directly""Your clients come to you because of your industry relationships, your integration expertise, and your local presence. Kaphera provides infrastructure; you provide the service. We don’t compete for your clients."
"We’ve been burned by platform dependencies before""That’s exactly why the stack is source-available, not proprietary. You can read every line. Steward-ownership means Kaphera cannot be acquired. If the relationship changes, you have the knowledge and the licence to continue operating.”

What closes the deal

The margin calculation. Show them: licence cost vs. what they charge per client × projected client count. If the numbers work, the conversation shifts from “should we” to “how fast can we launch”.

For marco-ferretti: the source-available licensing removes the risk objection. The steward-ownership removes the acquisition objection. What’s left is the commercial math, and the commercial math works because licensing is a fraction of building.

The Think-it reference is the proof point: Think-it is the prototype white-label partner. They ran managed connectors before Kaphera was a product. The operator is the productised version of what they built for themselves. That’s not a case study, it’s the origin story.

Graph View

Backlinks