Operators, service companies, and regulators all touch the same
subsurface data from different angles. We meet each one where it
already lives — federating, hosting, or exposing the layer
— without asking anyone to rebuild their stack.
partner-ecosystem · placeholder · round-4 capture
§02 · INTEGRATION PATTERNS
Four ways to plug in.
Operators with existing OSDU
You already run OSDU. We federate against it. Your platform stays
the system of record; we add the discovery surface, the MCP layer,
and the regulator-facing audit endpoint on top. No data leaves
your tenant unless you say so.
We host the OSDU stack for you — schemas, storage, search,
legal tags, the lot. You focus on loading the data and asking the
questions. Standards-clean from day one, so the day you outgrow us
you walk out with an OSDU-compliant export, not a lock-in.
We expose the data layer through MCP and REST APIs your existing
tools can call. Drop your interpretation, modeling, or analytics
product on top of a clean OSDU surface instead of building your
own ingest. Your customers get audit and lineage for free.
A read-only audit endpoint with signed records and immutable
lineage. See what was reported, when, and by whom — without
standing up infrastructure or chasing operators for spreadsheets.