Status quo · late 2026
What has changed — and why it matters now
How we approach it
Our method for Data Mesh, Fabric & API Access
01ReadinessDomain maturity, platform capability, governance appetite — mesh, fabric or centralised first.
02Product definitionData product canvas: owner, consumers, contract, SLOs, quality, access.
03PlatformSelf-serve capabilities, templates, catalogue, policy automation.
04Access layerREST/GraphQL data APIs, sharing protocols, MCP servers for agents, gateways.
05EnableFederated governance forums and advanced AI & data training for domain teams.
In depth
Building blocks
Data products
Discoverable, addressable, trustworthy, interoperable, secure — with contracts.
Fabric layer
Active metadata, virtualisation, integration across clouds and SaaS.
Sharing
Delta Sharing, Iceberg REST catalogues, OneLake shortcuts, clean rooms.
APIs for people and agents
Governed data APIs, MCP servers, rate limits, auditing.
Training
Data engineering, GenAI, agentic and multi-agent courses for your teams.
What you get
Deliverables
Data mesh & data fabric designAPI access for automationAdvanced AI & data training
Technology-agnostic
Platforms we work across
We design for the outcome first and choose the platform second — across Microsoft, AWS and Google Cloud, and every major AI provider.
Microsoft Fabric & PurviewDatabricks (Delta Sharing, Unity Catalog)SnowflakeGoogle Dataplex & Analytics HubAWS DataZoneStarburst / TrinoAnthropic MCP
Related