Query Forge

Capabilities

Federated SQL on the infrastructure you already run

Built on Query Studio infrastructure, Query Forge exposes each SQL-capable agent as a schema and plans joins centrally with intelligent pushdown.

Federated architecture

How Query Forge works

Plan centrally, push filters down, join in memory

Instead of new data movement pipelines, Core Hub receives the SQL statement, pushes projections and filters to remote agents, then evaluates joins with Apache Calcite.

• Central query planning across relevant agents
• Pushdown for projections and filters (=, <>, <, >, LIKE, IS NULL, AND/OR/NOT)
• Only filtered rows travel the wire for central join evaluation
• Bridges relational engines and NoSQL stores behind agents

View Query Forge docs ↗

● ● ● Query Forge

Multi-source querying without data movement

Query across relational, legacy, and NoSQL environments from a single developer or BI connection. Gluesync resolves schemas and returns results transparently.

Standard connectivity

Dedicated JDBC driver

Connect DBeaver, DataGrip, Tableau, and custom scripts

A branded JDBC endpoint (jdbc:gluesync://host:port) makes Core Hub feel like a single SQL system to external clients.

• Personal API Token authentication (gsp_…) or local account credentials
• No shared service credentials
• Predictable schema naming for single- and multi-agent pipelines
• Works with standard BI and SQL tooling

View Query Forge docs ↗

Unified JDBC gateway

One connection string. Many agents. Warehouse-style querying flexibility without storage overhead or continuous extraction latency.