Talk to us

Services

Some organisations need judgement. Others need something that works.

Texobox has two lines. Consulting on digital transformation, data sharing and data spaces, for organisations becoming data driven across their value chains and for the decisions no product can make for you: what to share, with whom, on which terms, and how to keep control once it’s shared. Data spaces are the means we know best, so much of that work is setting one up, deciding how to take part in one, or designing an architecture that has to hold up against regulation, standards and competitors’ interests at once. And products that package the same expertise, for the obligations that repeat, starting with DataSovi.

Line 1 · ConsultingFor digital transformation, data sharing and data spacesFour ways to start, backed by six areas of expertise: data sharing, data spaces, regulation and standards, authorisation, AI on private data, and fractional leadership.Line 2 · ProductsFor the obligations and integrations that repeatDataSovi: Data Act compliance, data sharing and catalogues, and agentic AI integration, as a product to deploy rather than a project to design.

Ways to start

Four engagements

Each has a defined scope, a fee agreed before we start, and a result you can act on. Most clients start with one of these and continue with what it leads to.

For data holders, and the parties receiving the data

Data Act compliance & observability

Giving users access to their data is the easy part. Proving it is not. We help set up the evidence and compliance for data holders, and give data recipients a way to show what they received and how they processed it.

You get

  • Observability that keeps the evidence current, product by product
  • For data holders: evidence that every user and third party got the data they asked for, and compliance with the Data Act
  • For data recipients: a record of what you received, on which terms, and how you used it
3–4 weeksLeads to: Compliance and observability by design or as a service with DataSovi
For data space initiators, consortia and sector associations

Data space governance & business model

A rulebook, co-created by participants, alongside the business model that makes taking part worth it. Built on our proven and extensive experience in data spaces and trust frameworks.

You get

  • Governance, rulebook and accession terms, written with the participants
  • A business model that works for each role
  • Where data sharing creates value, and which business processes it can optimise
PhasedLeads to: A data space architecture, once the rules are agreed
For data spaces, their participants and intermediaries

Data space architecture & conformance

The architecture that delivers your use case, complies with Article 33 and EN 18235, and automates cross-organisation business processes.

You get

  • An architecture designed around your use case and business process
  • Trust framework and protocol choices that automate exchange between organisations
  • Alignment with Article 33 and EN 18235 (trusted data transactions)
PhasedLeads to: Conformity work as the EN 18235 parts are cited
For organisations letting AI agents act across company lines

Agentic data-sharing architecture

An agent is just another system, with its own identity, that can act on someone’s behalf. We architect identity, mandates, usage rules and audit for agents so they comply with Article 33 and stay observable, on open protocols.

You get

  • Agent identity and verifiable mandates
  • Usage rules checked on every call
  • An audit trail and observability for every agent action
6–8 weeksLeads to: A build project, or agent-ready access with DataSovi

Other ways to work with us

Fractional CTO, CIO or CDO

An anchor role for an organisation where being data driven is central to the business: the decisions that are expensive to reverse, and a roadmap your team runs.

In-company workshop

A day on Data Act architecture for your product, IT and legal teams, built around your own products and data.

Capabilities

The expertise behind the offers

Six areas we work in. Most engagements draw on several of them.

01

Data sharing

Sharing data between organisations is rarely held back by technology. What’s missing is the arrangement around it: what you share, with whom, for what purpose, on which terms, and how you would know if those terms were broken. We help you set that up so you can share data and keep control of it once it leaves your hands, bilaterally, through a platform or through a data space.

1Offer itto the right parties2Agree the termscheckable by machines3Share itunder those terms4Prove itevery exchange recorded
Offer, agree, share, prove: data sharing that holds up between organisations.

Typical work

  • A data-sharing strategy: what to share, with whom, on which terms, and what it’s worth
  • Usage terms and purposes that travel with the data
  • Choosing the model: bilateral, through a platform, or through a data space
  • Describing data as products others can find and use
  • Keeping control after sharing: who received what, and on which terms
  • Data sharing
  • Data products
02

Data space strategy & governance

The rulebook is the real product of a data space: who can join and on what terms, what participants promise each other, who is liable for what, how disputes are resolved and how the rules change. If it’s vague, every exchange falls back to bilateral negotiation. If it’s too heavy, nobody signs it. Taking part is a design decision too: installing a connector doesn’t mean your APIs describe your data well enough for others to use it, or that anyone owns the decision of what to share.

One rulebookManufacturersService providersData providersData usersPlatforms & appsGovernance authority
Governance comes first: everyone in the data space signs one rulebook.

Typical work

  • Whether to set up a data space, join one, or both, and in which role
  • Governance framework, rulebook, accession terms and a change process participants trust
  • A business model that makes participation worth it for each role
  • Operating model for onboarding, certification and automated conformance testing
  • Readiness to take part: systems, APIs, and who decides what gets shared
  • Connectors, catalogues and onboarding on the protocols a data space uses, such as the Dataspace Protocol
  • Rulebook
  • Certification
  • ISO/IEC DIS 26450
03

Data Act, regulation & standards

Regulation sets the outcome and leaves the technical how to standards, several of them still being written. For smart devices and services (“connected products and related services” in the Act), Articles 3 to 6 of the Data Act require that data reaches the right party, on request, under the right conditions. For data spaces, Article 33 sets four interoperability requirements, and EN 18235 is being written to meet them: Part 2 for trustworthiness, Part 3 for interoperability, on the shared terms of Part 1. We read the regulation and the standards together and turn them into decisions your teams can build.

Your productgenerates the dataYouthe manufacturer/data holderYour customerA partner they chooseby designright to accessright to shareEU DATA ACT · ART. 3–5
EU Data Act, Articles 3 to 5: your customers have rights to access and share data.

Typical work

  • Data Act readiness: product data inventory, access by design from 12 September 2026, Article 4 and 5 request flows
  • Article 33 readiness: catalogue metadata, data models, access terms, agreements, and trusted data transactions
  • How the Data Act fits with the Data Governance Act, the GDPR and sector rules
  • Building toward EN 18235, ISO/IEC 20151 and the Eclipse Dataspace specifications while they mature
  • What a newly published part changes in your roadmap
  • EU Data Act
  • EN 18235
  • ISO/IEC 20151
04

Decentralised & fine-grained authorisation, API management

Sharing data safely comes down to one question asked on every call: may this party do this, with this data, right now? Between organisations there is no single identity provider to ask, so the answer is assembled from verifiable claims about the organisation, delegations from the user, and the policy attached to the data. We design where that question is asked, where it is answered, and how the two stay in step as policies change.

Who is askingverified, not typed inEvery callYour dataonly what is allowedPolicydecidesmay they?yes, on these terms
The gateway enforces, a separate policy decides. Standard protocols connect them.

Typical work

  • Identification and trust across organisations, with whichever trust framework or protocol applies: iSHARE, the Decentralised Claims Protocol or verifiable credentials, for example
  • Delegation and consent a machine can verify
  • Policy enforcement at the API gateway, decisions in an external policy decision point
  • Standard protocols between enforcement and decision points
  • API management: gateway design, plugins for the gateway you run (Kong, for example), APIs published as data products
  • Trust frameworks
  • Policy decision points
  • API gateways
  • ISO/IEC DIS 26451
05

AI: agentic, on private data

An AI system is only as useful as the data it can reach, and the data worth reaching is usually private, licensed or regulated. Agents raise the stakes: they act across systems, often with no person in the loop. An agent has its own identity, and can also act on a user’s behalf. Then the user gets only what they are entitled to, never what the agent itself may reach. We help you automate the access layer that checks every request against the policies and rules attached to the data, enforces them and logs what happened.

Yougrant scoped accessAI agentacts on your behalfCheckedon every callCustomerLicensedRegulatedOnly what is allowedthe rest stops at the check
Acting for a user, an agent gets only what that user is entitled to and the data’s terms allow, checked and logged on every call.

Typical work

  • Policy-checked data access for retrieval and agents
  • Agent identities of their own, and delegated, scoped and revocable authority to act for a user
  • Usage rights that travel with the data, including licence and text-and-data-mining terms
  • Datasets offered for training and evaluation with clear origin and licence
  • Every request observed, logged and enforced automatically: what was accessed, by which agent, for whom, on which terms
06

Fractional CTO, CIO, CDO & enterprise architecture

Senior technology and data leadership without a full-time hire, for a digital transformation, a data-sharing programme, a data space initiative or an organisation that has to take part in one: the architecture decisions that are expensive to reverse, and a roadmap your team can execute.

Decidewhat is hard to reverseDesignthe target architectureHand overa roadmap your team runs
Fractional leadership: from the hard decisions to a roadmap your team runs.

Typical work

  • Fractional CTO, CIO or CDO roles
  • Enterprise architecture: reviews, target state and roadmap
  • Digital and data strategy, and data governance at board level
  • Governing change across multi-party frameworks

Data Act, Articles 6 and 11

You shared the data. Now how do you enforce the terms?

The Data Act puts obligations on whoever receives data and gives data holders remedies when they’re broken. Using those remedies means knowing four things, for every user and every recipient. At 50,000 users, bilateral contracts stop being realistic.

  1. 01

    Who the recipient is

    Not a name typed into a form, but a verified legal entity that can be held to account.

  2. 02

    That the request is authorised

    Evidence that this user asked for this data to go to this recipient, collected with no more information than necessary.

  3. 03

    What terms apply

    The purpose agreed with the user, confidentiality for trade secrets, and compensation on fair, reasonable and non-discriminatory terms.

  4. 04

    What actually happened

    Which data went where, when, under which authorisation. Without that record, a claim under Article 11 is an argument, not evidence.

We help you find the right solution to meet these obligations.

Before you sign off on an architecture decision

Run the Article 33 self-check

Article 33(1) lists four interoperability requirements. Data only moves on them when four more hold: every party is identified, every request is authorised, usage conditions are attached to the data, and they are enforced. Tick what your architecture already does.

Article 33(1) · Interoperability
Trusted data transactions

Found gaps? For a data space, a data space architecture & conformance engagement closes them. For smart devices and services, start by proving your Data Act compliance.

How DataSovi does this, on datasovi.com

Engagement

How we work

Defined outcomes, agreed before we start. Ongoing roles are scoped in days per week.

  1. 1

    Assess

    Test your architecture against what applies to it: Data Act Articles 3 to 6 and 33, the published EN 18235 parts, your data space’s rulebook. A gap analysis, not a checklist score.

  2. 2

    Design

    Turn the gaps into decisions: data products, API contracts, policy points, agreement structures. Written down, with the reasoning.

  3. 3

    Build

    Implement alongside your team, or hand over a design they can build: connectors, gateway policy, onboarding into a data space.

  4. 4

    Keep pace

    Standards keep moving after go-live. When one you depend on is revised, we tell you what changed and what it means for your architecture.

Line 2 · Products

A ready-to-use solution that allows better data and access management, while keeping compliance without replacing your existing architecture.

Every request for your product data becomes a governed API call, with evidence. DataSovi is the control layer in front of the services you already run: it checks who is asking and on what terms, delivers, and keeps the proof. The Data Act is the trigger, not the whole story.

Visit datasovi.com

What it’s used for

  • EU Data Act compliance for smart devices & services
  • Data products, offered directly or through data spaces
  • Federated catalogues for data space operators
  • Agentic AI integration with controlled data access

Sectors, features and plans are on datasovi.com.

Let’s look at your architecture.

Tell us what you’re facing. Many organisations need both: a product for the obligations that repeat, and judgement for the decisions it can’t make for them.

Get in touch