Well-construction reporting, open by default.
OXBO-X is a modern, web-native platform for oil and gas well construction. It is the reporting system of record an operator actually shops for, and it does the engineering the legacy stack defers to four other products — in one application, on an open data model that hands control of the data back to the operator.
The legacy system of record records what happened. It does not compute the engineering.
In the incumbent pattern the operations report lives in one application while the engineering math — anti-collision, torque and drag, well control, casing design, cost estimating — lives in a chain of separately licensed desktop products, glued together by a single closed database. The user juggles a toolchain. The operator's entire well history is locked inside one vendor's schema. OXBO-X collapses the toolchain into one web application and breaks the lock-in.
Three layers, one application.
Daily operations, time and cost, non-productive time, personnel, drilling parameters, hazards, BHA, mud, cement, casing and well-control events — all captured as structured data with full version history.
Anti-collision and clearance, survey and trajectory, drilling mechanics and rig state, well-control kill sheets, per-cutter bit grading and mud-log authoring — real calculations running inside the same application.
An open, documented schema, append-only version history on every record, OSDU schema alignment, multi-format export, and a production integration layer that already connects to the systems in an operator's environment.
We already built the pipes. The reporting product is the new thing.
The hard, trust-deciding part of replacing a system of record is moving an operator's data in and out without lock-in. Through our sibling platforms — already running in production for a major unconventional operator — we ingest live drilling and completions telemetry, the full daily drilling report, AFE and the chart of accounts, and the authoritative well master; we write structured data back into the operator's existing environment with exactly-once delivery; and we hand every record back as JSON, CSV, Excel and Parquet, OSDU-aligned, straight into the analysts' warehouse and BI.
Documented schema, OSDU schema alignment, export to Snowflake, BigQuery and Databricks.
Production integration with the real systems in an operator's environment, including a land-and-expand path that ingests the legacy history first.
Append-only ledger on every record and a compliance event log with actor and before/after state — the lineage regulatory and audit use cases demand.
One application, the whole well.
File the daily report and run the anti-collision check, the kill sheet and the drilling-mechanics analytics in the same place. The legacy pattern files the report and sends you to three more licensed desktop products and three more data round-trips.
A vectorized ISCWSA clearance engine runs inside the product. No separate directional-planning license to check a separation factor.
Not just a record of the kick — a native kill sheet, Driller's and Wait-and-Weight, with real gas-kick expansion behavior.
Mineralogy percentages, lithology patterns and probabilistic petrophysics per layer — deeper than the deterministic single values of the incumbent pattern.
Teale MSE and a twelve-state rig-state detector computed from EDR, not just EDR storage.
React, FastAPI and PostgreSQL in the browser — not a Citrix-delivered desktop client over Oracle with a bolted-on report writer.
Replace the toolchain. Keep your data.
See OXBO-X against your current reporting system of record, with your own well data in the loop.