Pre-release. Ophiolite runs today for design partners; public source and server image publication are in preparation.

Ophiolite

Trust

Architecture

Every part runs inside your boundary. People's own tools connect through the same API as the browser.

Everything runs inside your boundaryInside the owner's boundary: the Workspace in the browser, the gateway with one typed API, the metadata and permission core, your object storage, and sandboxed runners. Outside: people's own tools (Python, OpendTect, QGIS) connecting through the API with their own sign-in. Nothing is sent to Ophiolite.Your boundaryWorkspaceGateway · one typed APIMetadata and permissionsYour object storageSandboxed runnersYour sign-in providerPython, agents,OpendTect, QGISyour computers
Owner-hosted: the server, storage and sign-in are yours. People's own tools connect through the same API as the browser, each with its own sign-in.
  • Available

    Workspace

    The browser application; an ordinary client of the public API.

  • Available

    Gateway

    One typed API for every operation, with the same permission checks for every kind of caller.

  • Available

    Metadata and permission core

    Versions, context, interpretation, grants and audit in one store, so one read answers consistently.

  • Partial

    Object storage

    Local disk or S3-compatible storage with verified range reads.

    Streaming past 32 MiB per representation is not yet qualified; Multi-node storage is not qualified

  • Available

    Runners

    Containers for jobs and agents, without network.

    No GPU or distributed scheduling

  • Partial

    Server image

    All of it in one image with backup, restore and upgrade.

    Clean-host qualification on the consolidated composition is still open; Available to design partners; there is no public download