Product / All capabilities
All capabilities
What exists today, what exists with limits, and what is coming — checked against the program's status table every time this site is built.
| Capability | Status | Who can get it | Limits |
|---|---|---|---|
| Sign in once, stay signed inSign in through your organisation's sign-in provider or with an access key; one session policy applies to the browser, the SDK and applications. | Available | Design partners | — |
| One typed APIEvery scientific read and write goes through one versioned API with a published schema and generated Python and TypeScript types. | Available | Design partners | — |
| Screens in plain languageScientists see names, units and versions; engineering identifiers stay behind one Technical details disclosure. | Available | Design partners | — |
| Everything the browser does is scriptableThe Workspace is an ordinary client of the public API, so sharing, access and publication can be done from code. | Available | Design partners | — |
| Python SDK, command line and templatesThe ophiolite package reads exact versions into DataFrames and publishes results; templates cover notebooks, scripts, applications and agents. | Available | Design partners |
|
| Agents that act within your rulesA remote MCP endpoint and scoped agent keys with budgets; every change an agent makes needs a plan you approved. | Available | Design partners |
|
| Inspect well logs in the browserView a curve, compare the original with a result and see what changed, without leaving the Workspace. | Available | Design partners | — |
| Share work with the right peopleContributors, policy-checked sharing and one set of stages; everyone reads the same exact version. | Available | Design partners | — |
| Run code inside your boundaryAgents and long jobs run in containers with no network, a read-only file system and resource limits. | Available | Design partners |
|
| AI use you can permit and auditPer-reader permission by purpose, whole-or-nothing corpus export and in-boundary search that never calls out. | Available | Design partners |
|
| Portable exitA versioned export bundle with an independent offline reader: reuse your data with no server and no account. | Available | Design partners |
|
| One record of data, context and interpretationA single metadata and permission core, so a version fixes the data, its context and its interpretation together. | Available | Design partners | — |
| Wells and wellbores as real thingsTyped wells and wellbores with evidenced associations, navigable in the browser and the SDK. | Available | Design partners | — |
| Adversarially qualifiedAn independent adversarial qualification of the whole chain before release; findings fixed and requalified. | Available | Design partners | — |
| A team journey rehearsed from the public docsThe 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. | Available | Design partners |
|
| One installable server imageOne image with backup, restore, upgrade and member and project moves from one operations command. | Partial | Design partners |
|
| Explicit result versionsAppend a result version against its parent, group results, recommend one and compare parameters. | Partial | Design partners |
|
| Your storage, verified readsLocal or S3-compatible object storage with verified range reads. | Partial | Design partners |
|
| Well logs, tops, trajectories, surfaces and point setsTyped profiles for logs, tops, trajectories, gridded and triangulated surfaces and point sets. | Partial | Design partners |
|
| Connectors with fidelity reportsEach connector declares what it reads and writes and reports what a conversion loses; a packaged QGIS plugin for scalar maps. | Partial | Design partners |
|
| Public conformance suitesOffline, server and agent conformance tasks anyone can run, and a nightly run against a deployment. | Partial | Design partners |
|
| Faults and seismic sectionsFault sticks, a SEG-Y reader that records every header decision, verified chunks and seismic sections in the Workspace. | Partial | Design partners |
|
| Apache-2.0 foundationApache-2.0 for project-owned code, source publication in preparation; a release-only candidate passes every gate privately. | Partial | Design partners |
|
| Configurable scientific ingestionSource packages with companions, versioned import recipes, Petrel points-with-attributes and OpendTect horizon readers. | Coming | Not yet | — |
| Access keys, service accounts and hand-overSelf-service scoped access keys, project service accounts with named administrators and an offboarding hand-over. | Coming | Not yet | — |
Not planned
These were removed from the plan rather than promised later:
- Suite-wide Petrel or Techlog replacement
- A general application builder or marketplace
- Universal format conversion