Your data stays yours. Kaphera only coordinates.
Kaphera sets up company identities, agreements and connections between companies. The data itself moves directly between you and your partners, on terms each side sets.
Built onEclipse Dataspace ComponentsDataspace ProtocolDecentralized Claims ProtocolIDSA Rulebook
Kaphera holds the setup, not the data
To connect companies, Kaphera needs to know who they are and what they agreed. It doesn't need what they share.
Last reviewed 24 Oct 2026
Kaphera keeps what it takes to coordinate: your company identity, partners, agreements, tasks and AI-use terms. It does not keep the data those agreements cover.
Orders, delivery dates, certificates and footprints go from your partner's connector to yours. Kaphera doesn't run a data plane for you.
A task gives your AI tool a link (MCP) from your own secure space. Each partner chooses which AI tools may see its data: any, EU-hosted only, or none.
It helps you find things and prepares actions for you to confirm. It receives company, partner and task names, never data contents, and keeps no conversation history.
How data spaces protect you
Kaphera is built on the rules and protocols that European data spaces use. These are the protections you get from them.
Last reviewed 24 Oct 2026
Before any transfer, both connectors negotiate a contract. In EDC, the agreement itself works as the access token for that one dataset.
Offers carry machine-readable terms (ODRL), and connectors check them before a contract is agreed and data is sent.
Companies prove who they are with verifiable credentials. Each party signs its own tokens, and partners check them against its published identity (did:web). No single identity provider sits in the middle.
Kaphera packages Eclipse Dataspace Components (Apache 2.0, governed by the Eclipse Foundation). The protocols it speaks are on track to become ISO/IEC standards.
Standards we build on
These are the standards Kaphera is built on. They are not certifications of Kaphera. We hold no certifications yet; our roadmap is in the Trust Center.
Last reviewed 24 Oct 2026
Open-source connector framework, Apache 2.0, in the Eclipse Dataspace Working Group
Open sourceRead moreHow connectors publish catalogues, negotiate contracts and start transfers
ISO/IEC FDIS 26450 · final text registered 13 Oct 2026Read moreHow companies present verifiable credentials without a central identity provider
ISO/IEC DIS 26451 · approved for final draft 20 Oct 2026Read moreShared concepts and characteristics of data spaces (JTC 1/SC 38)
Under publication since 21 Oct 2026Read moreHow a data space is governed and joined: roles, policies, an 8-step participation flow
Published guidanceRead moreIndependent certification of connectors and operating environments, Assurance Levels 1–3
Kaphera: not yet certifiedRead moreISO/IEC numbers refer to documents still in the ISO process; they are not published standards yet. Status checked 24 Oct 2026 on iso.org.
Common security questions
Last reviewed 24 Oct 2026
Still have questions? Contact us