Get any data into OSDU. Configured, not coded.
Wells, logs, seismic, production data and more: delivered, kept in sync, and traceable record by record.
OSDU is the open data platform of the energy industry. Every type of data it holds has its own schema, codes and services, so most teams write and maintain a custom loader for each one. OSDU Delivery replaces those loaders with configuration.
Stop building OSDU ingestion pipelines (3:42). Start here. |
Architecture and data flow (6:18). No coding or OSDU knowledge needed. |
- Every OSDU write path. Storage, file and dataset services, manifest and workflow ingestion, and the domain data stores for wellbores, seismic, samples, well delivery, production and reservoir models (coverage plan).
- Safe to rerun. The same row always becomes the same record, and only what changed is sent.
- Checked before sending. Mappings against their schema, legal tags against OSDU, and records before they go out.
- Every record accounted for. Nothing reaches OSDU except through the ledger, which finds any record by key, OSDU id or source file.
- After delivery. Verify against OSDU, explore what it holds, and correct with removals and redeliveries, every action recorded.
- Runs near your data. Workers fetch their work, so they can run inside the network that holds your data.
- One configuration, every environment. The same flows run in dev, test and prod.
- An AI assistant that builds it with you. Ask for a new data type and it reads the schema, drafts the mapping and opens a pull request for a person to review. It works from definitions and delivery metadata, and reads data only when asked, over what an approved AI context opens (MCP guide).
One command takes a laptop from nothing to a running OSDU Delivery that has delivered a sample estate and proved it. You need no OSDU: a stand-in runs on the machine, and everything else is the real product.
# Windows
irm https://raw.githubusercontent.com/TahirRiaz/osdu-delivery/main/bootstrap.ps1 | iex# macOS and Linux
curl -fsSL https://raw.githubusercontent.com/TahirRiaz/osdu-delivery/main/bootstrap.sh | bashFrom a checkout, dev.bat demo or ./dev.sh demo does the same. It needs a SQL Server, or Docker Desktop running to
start one (the local demo).
The videos in parts, in the order to watch them, each with a short description and tagged for data engineers, for extending the framework, or both.
- Your first delivery: build one from scratch
- Run it locally: with your own SQL Server, OSDU and flow repository
- Welldb sample: an empty partition filled, up to well logs and curves
- Reference documentation: every flow, mapping key, command and concept
- Mapping transformations: every function, modifier and lookup
- Deployment: Docker Compose, Kubernetes, Azure Bicep, Terraform and Radix
- Architecture: the components, the databases and how they fit
- Wiki: why it is this way
Verified against a live OSDU (Azure Data Manager for Energy 0.29, September 2026) through the storage, file, manifest ingestion and Wellbore DDMS paths. Every write path is tested against OSDU's own service contracts, pinned in osdu/specs. Recent changes are in the changelog.
The onboarding videos tagged extending are the way in. CONTRIBUTING.md sets up a
development machine and runs the tests, and osdu/README.md maps the module's code. OSDU Delivery is
built on SQLFlow, kept in sqlflow/, which is why its command line
is sqlflow.
Licensed under the GNU General Public License v3.0 (LICENSE).
Questions, bugs and feature requests: tahir@sqlflow.io or an issue on the repository. Security reports go by email or a private security advisory, never a public issue (SECURITY.md).