OphioliteSolutions
For team leads and IT
The team shares work through a file share, a workspace product would lock the data in, and nobody can show where the data lives or who can read it.
Why Ophiolite
Ophiolite runs inside your boundary with your storage and your sign-in provider, keeps an exact record of who published and shared what, and gives you a portable exit that reads without us.
What you can use
Sign in once, stay signed in
Sign in through your organisation's sign-in provider or with an access key; one session policy applies to the browser, the SDK and applications.
One typed API
Every scientific read and write goes through one versioned API with a published schema and generated Python and TypeScript types.
AvailableScreens in plain language
Scientists see names, units and versions; engineering identifiers stay behind one Technical details disclosure.
AvailableAgents that act within your rules
A remote MCP endpoint and scoped agent keys with budgets; every change an agent makes needs a plan you approved.
- Assistant sign-in against your own sign-in provider and automatic assistant approvals are not yet available
Share work with the right people
Contributors, policy-checked sharing and one set of stages; everyone reads the same exact version.
AvailableRun code inside your boundary
Agents and long jobs run in containers with no network, a read-only file system and resource limits.
- No GPU or distributed scheduling
AI 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.
AvailableAdversarially qualified
An independent adversarial qualification of the whole chain before release; findings fixed and requalified.
PartialOne installable server image
One image with backup, restore, upgrade and member and project moves from one operations command.
- Clean-host qualification on the consolidated composition is still open
- Available to design partners; there is no public download
Explicit result versions
Append a result version against its parent, group results, recommend one and compare parameters.
- Connector-owned inputs are not versioned this way
Your storage, verified reads
Local or S3-compatible object storage with verified range reads.
- Streaming past 32 MiB per representation is not yet qualified
- Multi-node storage is not qualified
Public conformance suites
Offline, server and agent conformance tasks anyone can run, and a nightly run against a deployment.
- A model-driven agent test over MCP is not yet part of the suite
Apache-2.0 foundation
Apache-2.0 for project-owned code, source publication in preparation; a release-only candidate passes every gate privately.
- Source publication in preparation; the source is not yet public
A team journey rehearsed from the public docs
The six-step team journey rehearsed on a clean install from the public documentation, by an agent that did not build it, with no engineer repairs.
- An internal rehearsal, not an external trial
- QGIS and the two-person run on macOS were not part of it
Access keys, service accounts and hand-over
Self-service scoped access keys, project service accounts with named administrators and an offboarding hand-over.
Compared with LAS files, Python and a shared drive
| Question | LAS, lasio and a shared drive | Ophiolite |
|---|---|---|
| Where the data lives | On a shared drive, in copies | On your server and storage, one version of each |
| Which version a result used | Written in a note, if at all | Recorded with the result |
| Who can read it | Whoever has the drive | People it is shared with; everyone else refused |
| Units, nulls and depth | Re-read by every script (lasio) | Stored with the version; read the same way everywhere |
| Agents and automation | A script with a shared password | Scoped keys, budgets and approved plans |
| Leaving | Copy the files | A bundle and a reader that work without us |
A day in the work
- Run Ophiolite beside your storage (design partners receive the server image); connect your sign-in provider.
- Add people and projects; a sign-in ends after seven days without use and after thirty days at most.
- Back up and restore with one operations command.
- Leave, if you choose, with a bundle that reads offline.
See for yourself
The security page lists sessions, keys, sandboxing and the qualification record; the architecture page shows the owner boundary.