Skip to main content
Airhouse is a Postgres-compatible, agent-native data warehouse. It speaks the Postgres wire protocol, runs every query on DuckDB, and stores tables in open formats with DuckLake, so any Postgres client, BI tool, or agent can use it without a new driver or query language. It has three parts:
  • The data plane accepts Postgres connections and checks every statement against the caller’s credentials, role, and limits before DuckDB runs it.
  • The control plane creates databases and users, and mints short-lived credentials on demand.
  • Your storage holds each database’s catalog in Postgres and its tables as Parquet files in object storage, isolated from every other database.
Airhouse architecture. SQL clients such as psql, drivers, BI tools, agents, and apps send SQL over the Postgres protocol to the data plane, which authenticates the password, authorizes the role and limits, and executes on DuckDB. Your platform, Oxygen or your own backend, provisions through the control plane's Admin API, which manages databases, users and roles, and credentials, and returns short-lived credentials. The data plane reads metadata from a DuckLake catalog in Postgres and Parquet table data in S3-compatible storage. A highlighted box notes that each database is isolated, with its own catalog, storage prefix, users, and query limits.

Airhouse checks every statement before DuckDB runs it, can hand out short-lived credentials instead of stored passwords, and keeps each database's catalog and files isolated in open formats on infrastructure you control.

​
Why Airhouse

  • Works with every Postgres tool. psql, JDBC, psycopg2, DBeaver, Tableau, and agents connect over the standard wire protocol.
  • Analytical speed. DuckDB runs joins, window functions, and aggregates over large tables quickly, reading only the files and columns a query needs.
  • Open data, your infrastructure. Tables are standard Parquet files in your object storage with a DuckLake catalog in your Postgres, so the data stays readable without Airhouse.
  • Isolation by default. Each database has its own catalog, storage location, users, and query limits.
  • No long-lived keys. Service accounts mint short-lived credentials on demand, so a platform never stores a password per user.

​
Next steps

  • Getting access: how to get Airhouse from Oxygen.
  • Quickstart: run Airhouse locally and run your first queries.
  • Architecture: key concepts, the life of a query, and deployment topologies.
  • Connect: psql, drivers, and BI tools.