7 min read

White-label Partner

The customer-segment archetype for systems integrators and platform companies that want to launch managed connector services under their own brand without building the underlying platform from scratch. They have client base, brand presence, and commercial relationships; they license the Kaphera platform to skip the multi-month build and avoid the lock-in of reselling a proprietary stack.

Who is the customer?

The White-label Partner is a systems integrator or platform company that has identified managed connector services as a product line they want to offer, but does not want to build the underlying platform from scratch. They have an existing client base, a brand presence in the dataspace ecosystem or adjacent markets, and the commercial and technical relationships needed to sell and deliver managed infrastructure. What they lack is the time, the specialised expertise, and the capital required to build and maintain a production-grade multi-tenant EDC operator independently.

In practice, this is a mid-to-large systems integrator (an organisation like a regional technology consultancy, a cloud services reseller, or a sector-specific IT provider) that sees the growth of European dataspace mandates as a commercial opportunity but has assessed the build-versus-buy decision and concluded that building the platform themselves is not the right use of their engineering capacity. They want to be in this market. They do not want to be in the business of building and operating connector infrastructure at the platform level.

The decision-maker is typically at the partnership or product leadership level: someone accountable for building out a service portfolio and evaluating which capabilities to develop internally versus source externally. The evaluation criteria are commercial as much as technical: margin structure, licence terms, ability to customise the customer-facing experience, and what happens to their clients if the relationship with Kaphera changes.

What is their problem?

The White-label Partner’s problem is timing and investment. The window for establishing a credible position in the managed EDC connector market is open now, driven by EU Data Act enforcement timelines, Catena-X supply chain mandates, and the broader acceleration of European dataspace adoption. Their clients are being asked to connect to these networks, and the Partner wants to be the organisation those clients turn to. But building a production-grade multi-tenant connector platform (the operator, the data plane, the identity stack, the credential management, the multi-dataspace profiles) requires months of specialised Rust and Kubernetes engineering, followed by the ongoing operational burden of running it in production. That investment is hard to justify for a services organisation whose core competency is client delivery, not platform engineering.

The alternative, reselling or referring to an existing managed connector service, creates a dependency on a competitor and erodes the Partner’s margin and brand differentiation. If they are routing clients to another provider’s platform, they are not building a product; they are acting as a referral channel.

There is also a long-term concern about control. If the Partner builds their managed connector offering on a proprietary platform, any change in that platform’s pricing, terms, or ownership creates immediate exposure for their client relationships. The lock-in that makes proprietary platforms uncomfortable for end customers makes them equally uncomfortable for partners building services on top of them.

What is the most important customer benefit?

A production-ready platform they can offer under their own brand, without building it themselves. The Kaphera Cloud operator and platform server are source-available, which means the Partner can inspect every layer of the infrastructure they are licensing, understand how it works, and make an informed assessment of what they are offering their clients. The commercial licence gives them the right to operate the platform as a managed service under their own brand. Their clients see their brand and their commercial relationship; Kaphera provides the infrastructure and operational foundation underneath.

The source-available licensing also resolves the long-term control concern. Because the Partner can read the code, they are not dependent on Kaphera’s continued cooperation to understand what their platform does. If the relationship changes, they retain the knowledge of how the platform works. This is a meaningfully different risk profile from building a white-label service on a fully proprietary stack, and it is a distinction the Partner can honestly communicate to their own clients as part of their sovereignty narrative.

The economic case is straightforward: licensing the Kaphera platform is a fraction of the cost of building and maintaining an equivalent one, the time to market is measured in weeks rather than months, and the margin structure of the managed connector business is theirs to set.

How does the company know what the customer wants or needs?

The White-label Partner channel is the most forward-looking of the four personas in terms of direct validated demand. The operational and product knowledge that informs this channel comes primarily from Think-it’s own experience as the prototype white-label partner. Think-it has been running managed EDC connectors for clients using the predecessor Krypton platform, and the Kaphera operator is the productised version of what Think-it built for itself. That experience directly informs what a systems integrator needs from the platform: the ability to manage multiple client environments cleanly, the organisational model that keeps client contexts separate, the developer toolchain that lets the Partner’s engineers provision and operate connectors without direct cluster access, and the commercial licence terms that make the offering viable as a product rather than a project.

The specific commercial structure (licence agreement with Kaphera, Partner operates under their own brand) is designed to match the business model of the target partners rather than imposing a reseller model that conflicts with how services organisations manage client relationships.

What is the customer journey?

The White-label Partner’s journey begins with a commercial conversation, not a technical evaluation. The Partner has already decided they want to be in this market. The question they are bringing to Kaphera is whether the platform and the commercial terms make it viable. The initial conversation covers margin structure, licensing model, what customisation is possible in the customer-facing experience, and what the operational relationship with Kaphera looks like once the agreement is in place.

If the commercial terms work, the technical evaluation follows. The Partner’s engineering team reviews the operator and platform server source, assesses the deployment model, and confirms that the platform can be operated within their existing infrastructure and processes. Because the code is readable, this evaluation is substantive rather than based on documentation and promises.

Onboarding involves setting up the Partner’s branded instance of the platform, configuring the dataspace profiles they want to offer their clients (MDS, Tractus-X, or additional profiles as they become available), and establishing the operational runbook for managing their clients’ connector lifecycle. Kaphera provides the platform and operational foundation; the Partner owns the client relationship, the pricing they charge their clients, and the support experience they deliver.

Once operational, the Partner’s engagement with Kaphera is primarily at the platform layer: new connector profile releases, upstream EDC version updates, and any operational issues that surface in their managed environment. The partner’s growth (onboarding new clients onto their managed connector offering) drives Kaphera’s growth through the licence agreement. The incentive structures are aligned: Kaphera succeeds when Partners succeed, which means the relationship is structured around the Partner’s commercial outcomes rather than Kaphera’s platform usage metrics.

Commercial topology

flowchart TB
  K["Kaphera<br/>(licence + ops support)"]
  P["Partner<br/>(white-labels stack, sets pricing)"]
  C["Partner's clients<br/>(branded managed connectors)"]
  D["Dataspace<br/>(MDS / Tractus-X / ...)"]
  K -- "licence + roadmap" --> P
  P -- "branded service" --> C
  C -- "participation" --> D
  K -. "ecosystem visibility" .- D

Graph View

Backlinks