01 / Context switching
External clients everywhere
Engineers jump between the Control Plane and separate database tools to inspect schemas, run SQL, and troubleshoot sync issues — slowing every validation loop.
Gluesync Module · SQL workbench
Query Studio
An embedded SQL workbench inside the Control Plane. Inspect schemas, run queries, and validate live datasets without leaving Gluesync.
Why Query Studio
Validate data where pipelines are managed
02 / Credential sprawl
Scattered connections
Each external client means another credential, another VPN hop, and another place where production access is hard to govern.
03 / The platform outcome
One operational workspace
Query Studio uses existing Gluesync connections so pipeline monitoring and data exploration share a single, governed environment.
Capabilities
Built for data operations inside Core Hub
Query Studio turns Gluesync from a replication monitor into an interactive workspace for inspecting and validating synchronized data.
Embedded workbench
Control Plane workspace
Schema browser, SQL editor, and results in one place
Fully embedded in the Gluesync Control Plane and powered by Core Hub. Work against configured agents without managing a separate database client.
- Schema browser for databases, schemas, tables, and columns
- Multi-tab SQL editor for composing and managing queries
- Results console with outputs, execution logs, and analysis
- S3, WebDAV and NFS lake agents in the connection picker, with one table per dataset
Developer productivity
Query capabilities
Dialect-aware tooling for ad-hoc and repeatable validation
Productivity features help teams move from one-off troubleshooting to reusable validation workflows across heterogeneous engines.
- Dialect-aware autocomplete for supported engines
- Explain plan visualization for query strategy analysis
- Query parameters, saved queries, and CSV / JSON / SQL INSERT export
- 20+ database engines supported out of the box
Multi-source querying from one workspace
Interact with relational, analytical and data-lake sources through a consistent interface inside Gluesync — then extend to federated JOINs with Query Forge.
Enterprise governance
Security and access control
Read-only by default, audited, and role-aware
Query Studio is designed for production environments where data access must stay carefully managed.
- Role-based access control for user permissions
- Read-only mode by default to protect production systems
- Optional write mode for roles authorized through RBAC
- Query auditing with 90-day retention for compliance
Settings · Query data access
Query data access
Connection mode
Schema and table rules
public
*
erp
customers
PII unmask grants
Viewers can never unmask, even with a grant.
Query Studio AI · Available in Gluesync 2.3
Move from intent to inspectable SQL.
Ask for the data you need in plain language or press Tab while you write. Query Studio AI uses the schema context already visible in your workspace to propose the next query.
- Grounded in your workspaceDatabase, schema, and editor context shape the draft.
- Review before runGenerated SQL enters the editor. It never executes itself.
- Existing controlsQuery Studio permissions and read-only defaults stay in force.
Tool calls
list_sql_capable_agents()execute_sql(…) Tool calls
get_pipeline_status(…)get_agent_metrics(…) Tool calls
list_connections()get_connection_usages(…) Explore the platform
Continue exploring Gluesync
Query Studio is part of Gluesync Knowledge. Pair it with Query Forge for federated SQL, or return to the full platform.
Lake queries
Query Parquet, CSV and JSON files in your data lake from this workbench, in place.
Explore Lake queries →
Validator
Compare a replicated entity with its target and optionally reconcile the differences.
Explore Validator →Core Hub MCP server
Expose Query Studio database tools and Core Hub operations to MCP clients under Control Plane RBAC.
Explore Core Hub MCP server →
Query Forge
Federated SQL across isolated agents — JOINs without ETL or raw data movement.
Explore Query Forge →
Courier
Publish REST endpoints over your tables, served through the Query Studio execution path.
Explore Courier →
Schedules and events
Chronos schedules, chained workflows, webhooks, and Core Hub event triggers.
Explore Schedules and events →Resources
Guides, roadmap and support
Documentation
Technical guides, API reference, deployment tutorials.
Read documentation ↗
Public Roadmap
What we're building next. Submit feature requests.
View roadmap ↗
Support
Access technical support and operational assistance.
Get support →
Service Status
Real-time platform availability and incident history.
Check status ↗Inspect live data without leaving Gluesync
Start a free trial or talk with the MOLO17 team about embedding Query Studio in your data operations workflow.