- Airway loads: it extracts data from the systems a business already runs and loads it into the warehouse, moving only what changed.
- Airhouse stores: it is the managed, Postgres-compatible warehouse where that data lands, along with the facts custom apps record, with isolated databases and no long-lived keys.
- Airform shapes: it turns raw tables into clean, tested ones with version-controlled SQL models.
- Airconductor runs: it queues each step and runs it in order, so a load, the SQL that shapes what it loaded, and the refresh of the model built on top happen in sequence and finish even if a server restarts partway through.
Data moves left to right, from your systems to the World Model, and every step along the way is a version-controlled file in the same workspace.
One workspace, from source to model
A typical data stack is stitched together from separate products for moving, storing, transforming, and defining data, each with its own configuration, credentials, and release process. The seams between them are where numbers drift and failures hide. In Oxygen, every step lives in one workspace. Pipelines, models, and metric definitions are files reviewed and deployed together through Git, alongside the agents and automations that use them. A change to how data is loaded, shaped, or measured is a single, reviewable change, and every number an agent reports traces back to definitions you can read.Airway
Incremental ELT from the systems you already run.
Airhouse
The managed warehouse where your data lands.
Airform
Version-controlled SQL models that land clean, tested tables.
Airconductor
The task engine that runs every load, step, and schedule to completion.