Talk with our engineers by joining the new Onehouse community Slack!
Ecosystem and integrations
Automation and APIs
Four interfaces manage every Onehouse resource from code: lakes, databases, tables, sources, flows, transformations, validations, clusters, jobs, table services, catalogs, service principals, and access policies.
| Interface | Shape |
|---|---|
| SQL command API | DDL-style grammar: CREATE FLOW, ALTER CLUSTER, DESCRIBE TABLE_SERVICE, GRANT PRIVILEGE. Commands return a request ID, and a status endpoint polls long-running operations. See Controlling Onehouse with SQL. |
CLI (oh) |
A Python package wrapping the API. It ships an agent skill you can install into Claude Code, Cursor, and Codex, so an assistant can drive the platform directly. |
| Terraform provider | Clusters, lakes, databases, catalogs, sources, flows, table services, transformations, transformer JARs, and validations, each with a matching data source. |
| Python SDK | Typed helpers over the control-plane API, plus a Lakegres client. |
For orchestration, Onehouse publishes Airflow hooks, operators, and sensors. dbt Core and dbt Cloud connect to SQL clusters.