Skip to main content

The QueryFlux Blog.

Why QueryFlux exists, how it works, and how teams run SQL for tools and AI agents across many engines.

Offload Snowflake queries without changing clients

Amit Gilad

Point Snowflake clients at QueryFlux, keep heavy work on Snowflake, and offload the rest to Trino or StarRocks — no dashboard or notebook rewrites.

Guides

3 articles

One endpoint for Iceberg on Trino and StarRocks

Amit Gilad

Run Trino and StarRocks on the same Iceberg tables behind one QueryFlux SQL endpoint — route BI and notebooks without client rewrites.

Guides

Give agents SQL, not the keys to every engine

Amit Gilad

Put AI agents behind QueryFlux — one MCP or SQL endpoint with routing, guardrails, impersonation, and a record of every query.

Guides

Why QueryFlux: the missing layer above query engines

Amit Gilad

Open table formats made data interoperable. Query engines are still islands. Why QueryFlux exists as a neutral SQL layer above the engines.

Vision