The API Layer for the Data Warehouse

Turn trusted warehouse SQL into secure, read-only APIs. Democratize data usage across apps, internal tools, and AI agents—without driving up your warehouse compute bills or exposing database credentials.

How it works

Serves a cached snapshot to your apps

Warehouse SQL
Trusted models
Approved queries
Sync
API Layer
Qry
Read
Downstream
Apps
Internal Tools
AI Agents

Why now

The warehouse is no longer just for dashboards.

Internal tools, customer surfaces, partner workflows, scripts, and AI agents increasingly need precise slices of trusted warehouse data. Direct warehouse access is too broad, custom backend work is slow, and reverse ETL is not an API contract.

Qry creates a narrow governed boundary: the data team chooses the SQL, the allowed inputs, the freshness policy, and the consumers that can call it.

select
  account_id,
  account_name,
  health_score,
  current_mrr,
  renewal_date
from marts.customer_health
where true
  and account_id = {{ account_id }}
  and health_score <= {{ max_score }} -- @optional
limit {{ page_size }}

Use cases

Focused API surfaces for data teams and the software around them.

Qry is not BI, reverse ETL, an app builder, or a backend-as-a-service. It is the narrow API layer around warehouse data that should be consumed programmatically.

AI agents and Slack bots

Give LLMs and autonomous agents structured warehouse context via secure, cached APIs.

Read use case

Customer-facing usage widgets

Serve refreshed billing and platform metrics directly inside your product dashboard.

Read use case

Internal tools and Retool portals

Connect warehouse data to internal ops tools and custom admin panels without slowing down your app or driving up query costs.

Read use case

Cloud MVP

Managed reliability around the warehouse-serving boundary.

Qry Cloud is being built first around hosted teams, durable refresh workflows, immutable snapshots, and operational visibility for API usage.

Cost InsulatedAPI traffic reads from local serving snapshots. Downstream reads never trigger live warehouse queries, eliminating expensive compute spikes.
DemocratizedProvide secure, read-only programmatic access to modeled data without distributing database credentials.
ObservableTrack background refresh workflows, request logs, performance, and API metrics in a centralized dashboard.
Stable ContractsGenerate OpenAPI documentation and typed query parameters, making each endpoint a versioned contract.