Interoperability & deployment
A frac twin is only useful if it sits next to the systems you already bought. These are the 14 formats and transports that exist in the product today — 11 readable, 9 writable — plus 5 programmatic surfaces and 4 deployment postures. No migration project is required to run a pilot.
Formats & transports
Eclipse deck (.DATA / INCLUDE)
SLB Eclipse / Petrel
Full deck import with INCLUDE resolution, flavor detection so a CMG or MRST deck is not fed to the Eclipse parser, and INCLUDE export back out.
Eclipse summary (.RSM)
SLB Eclipse
Reads simulator summary vectors for history-match comparison.
GRDECL corner-point grid
Petrel / MRST
Grid + property import via the Python SDK example.
CMG IMEX (.dat)
CMG
IMEX dataset export; CMG/MRST decks are recognized on import and routed to the wizard.
RESQML 2.x
Energistics / OSDU-adjacent
Round-trip through the Python SDK examples for grid and fracture-geometry exchange.
WITSML 2.0
Rig / frac-van data aggregators
Streaming ingest with auto-QC on the way in, plus WITSML export of computed channels. Vendor-neutral: any compliant server.
PRODML
Production data historians
Production volumes and pressures for RTA and forecast calibration.
LAS 3.0
Petrophysics
Log import for the rock-property column; computed curves export back as LAS.
ZMAP+
Surface / horizon gridding
Structural surfaces for the stratigraphic column.
PIPESIM bridge
SLB PIPESIM
Wellbore hydraulics hand-off in both directions.
FracPro CSV bundle
LINQX FracPro
Documented CSV schema with a canonical-units trailer for lossless re-import.
ARIES deck
Halliburton Landmark ARIES
Decline/economics deck export so forecasts land in the corporate reserves workflow.
VTK unstructured (.vtu)
ParaView / ResInsight
Fracture and reservoir fields for third-party 3D post-processing.
Apache Arrow Flight
Vendor telemetry / data platforms
High-throughput columnar streaming transport for live channels.
Programmatic surfaces
Public REST API
Per-team API keys (stored hashed, instantly revocable) against /api/public/sdk/v1 — run submission, status, and result retrieval.
Headless CLI
Workflow JSON in, artifacts out. Meters cleanly per run, which is what makes consumption pricing and CI gating possible.
Python SDK
Import/export examples for every format above plus fleet batch submission.
MATLAB & PowerShell
First-class clients for teams whose tooling is not Python, including a Simulink block and scheduled-task CI examples.
MCP server
Model Context Protocol endpoint so an enterprise assistant (yours or ours) can read batch context and call interpretation tools with structured results.
Where it runs
Managed cloud (default)
Browser-native, nothing to install. Team-scoped row-level security isolates tenant data; edge delivery keeps the UI fast from anywhere.
Dedicated single-region deployment
A deployment pinned to one region for operators with data-residency requirements, with the same application image.
Customer-hosted / private cloud
For operators who will not send operational data to shared infrastructure: the app image plus the headless CLI and MCP endpoint run inside your tenancy, with your identity provider in front. Scoped per engagement — talk to us about the runtime you already operate.
Coexistence, not rip-and-replace
The twin reads from and writes back to the systems of record you already own (Petrel/Eclipse, Landmark/ARIES, CMG, WITSML historians). No migration project is required to start a pilot.