OphioliteSolutions
For data managers
The same well has four names, the authoritative version of a file is whichever was copied last, and changes in the wells database go unnoticed.
Why Ophiolite
Ophiolite gives wells and wellbores declared identities, keeps originals with every version, runs reviews through one set of stages, and tells you when a connected source changed — without refreshing anything behind your back.
What you can use
Everything the browser does is scriptable
The Workspace is an ordinary client of the public API, so sharing, access and publication can be done from code.
AvailableShare work with the right people
Contributors, policy-checked sharing and one set of stages; everyone reads the same exact version.
AvailableAI use you can permit and audit
Per-reader permission by purpose, whole-or-nothing corpus export and in-boundary search that never calls out.
- No model training or hosting
Portable exit
A versioned export bundle with an independent offline reader: reuse your data with no server and no account.
- Streaming past 32 MiB per representation is not yet qualified
One record of data, context and interpretation
A single metadata and permission core, so a version fixes the data, its context and its interpretation together.
AvailableWells and wellbores as real things
Typed wells and wellbores with evidenced associations, navigable in the browser and the SDK.
PartialWell logs, tops, trajectories, surfaces and point sets
Typed profiles for logs, tops, trajectories, gridded and triangulated surfaces and point sets.
- Shapefile import, explicit coordinate transformation and true-vertical-depth tracks are not yet available
Connectors with fidelity reports
Each connector declares what it reads and writes and reports what a conversion loses; a packaged QGIS plugin for scalar maps.
- QGIS host acceptance on macOS is not yet complete
Configurable scientific ingestion
Source packages with companions, versioned import recipes, Petrel points-with-attributes and OpendTect horizon readers.
A day in the work
- A connected wells table changed overnight; the Workspace says so.
- Review the change and refresh explicitly; completed work keeps the version it used.
- Associate a new log with its wellbore, stating the evidence.
- Approve a result for use; later versions need their own approval.
See for yourself
The data model page shows how identity, versions and lineage fit together; the capability matrix states every limit.