Gluesync Module · Ships with Gluesync 2.3.1

Visualize

Turn an entity you already replicate into a chart by describing it to Spark, arrange charts on a canvas, keep them current by hand, on a Chronos schedule or whenever the data changes, and publish a chart or a whole canvas at a stable public URL.

Visualize
Visualize / Q3 sales review

Q3 sales review

Canvas · 2 charts · Team
Revenue by categoryLast quarter · sales.orders
HardwareSoftwareServicesSupportTraining
FreshSUM(amount) · refresh on entity change
Monthly revenueLast 12 months · sales.orders
FreshSUM(amount) · refresh on entity change
  1. 01 Describe the chart to Spark
  2. 02 Apply the proposal to a canvas
  3. 03 Share one link, protected the way you need

Why Visualize

Charts on the data you replicate, not on another copy of it

01 / The BI detour

Export, copy, re-permission

Answering a simple question about replicated data means exporting it to a BI tool, keeping another copy, and maintaining another set of permissions that drifts from Core Hub's.

02 / Dashboards that drift

Stale or expensive

Dashboards rebuilt on a timer lag the data they show, or rerun heavy queries on a schedule nobody is watching. Public pages make both problems worse.

03 / The platform outcome

Author, refresh, publish in Core Hub

Visualize charts the entities Gluesync already syncs, refreshes snapshots when the data changes, and runs every query as the chart's owner under the same policies as Query Studio.

How it works

From a sentence to a shared canvas

  1. 01

    Describe

    Spark proposes, you apply

    Ask for a chart in plain language. Spark grounds the request on the Enterprise brain's schema and returns a proposal with the chart type, grouping, measure and lineage. Nothing is saved until you apply it.

  2. 02

    Arrange

    Collections are canvases

    Group charts into a collection and lay them out as tiles. Each visualization is personal or shared with the team, and belongs to at most one canvas.

  3. 03

    Publish

    A chart or the whole canvas

    Share a single chart or an entire canvas at a public URL that is open, password-protected or behind SSO. Public reads always serve the stored snapshot and never run the query.

Capabilities

What ships in Visualize

Visualize is part of Gluesync from 2.3.1, not an add-on. It is enabled per Core Hub installation and respects the Control Plane's roles: anyone can view, Super admins, Managers and Monitors author, and Super admins and Managers share.

Prompt-driven authoring

From a sentence to a chart

Spark proposals over a single-table SQL entity, with lineage you can check

Pick a SQL entity on an agent Gluesync replicates, then describe what you want to see. Spark returns a proposal that names the chart type, the dimension, the aggregated measure and the columns it used. Apply it as it is, or keep refining in the same thread.

  • Chart types: bar, stacked bar, line, area, pie, donut, scatter, table, KPI and heatmap
  • Proposals carry a short why-note and lineage tags for the columns and entity behind the chart
  • When a request cannot be grounded on a real column, Core Hub answers UNRESOLVED and saves nothing
  • Row, byte and tool-call budgets cap what the proposal step can read
  • Charts can also be authored from the form or through the REST API

View Visualize docs ↗

Visualize
Visualize / Q3 sales review

Q3 sales review

Canvas · 2 charts · Team
Revenue by categoryLast quarter · sales.orders
HardwareSoftwareServicesSupportTraining
FreshSUM(amount) · refresh on entity change
Monthly revenueLast 12 months · sales.orders
FreshSUM(amount) · refresh on entity change

Keep charts current

Snapshots that refresh themselves

Manual, on a Chronos schedule, or whenever the entity changes

Every chart keeps a snapshot of its last result. A refresh policy decides when that snapshot is considered fresh, how long a stale one is still served while a refresh runs, and what triggers the next run.

  • Refresh on demand, from a Chronos visualize_refresh task, or when the bound entity changes on the source or target side
  • Defaults: fresh for 15 minutes, stale-while-revalidate for an hour, 2 second debounce and a 15 second minimum between runs
  • Refresh runs are recorded with their trigger, duration and row count
  • Public pages always serve the stored snapshot; they never execute the query

View Chronos refresh docs ↗

Visualize
Visualize / Q3 sales review / Monthly revenue

Refresh settings

Monthly revenue · applies only to this chart
Refresh when data changes

Rebuild when a confirmed CDC change lands on sales.orders. Debounce 2 s · never closer than 15 s.

Chronos refresh

Chronos runs the schedule. Create a job that posts visualize.refresh for this chart; this switch records that it should run.

Runs the query as the owner, read-only, with the same data-access policies and masking as Query Studio.

One refresh path for Chronos and CDC

The same policy limits apply whether the refresh comes from a scheduled job, a change event or a click, so a busy table cannot turn into a query storm.

Publish

Share a chart or a whole canvas

Stable public URLs with open, password or SSO access

Create a public link for one chart or for a full canvas. Each link has its own slug and protection, can be rotated so the old URL stops working, and renders with a Made with Gluesync header.

  • Protections: open link, password with a short-lived access token and rate-limited attempts, or sign-in through Core Hub SSO
  • Slugs of 12 to 64 characters; rotating a slug makes the previous URL return 404
  • Public responses include the snapshot and chart spec only, never the SQL, bindings or owner
  • Sharing is limited to Super admins and Managers

View sharing docs ↗

Visualize
Visualize / Q3 sales review / Share

Resources

Visualize documentation and resources

Roadmap

Public Roadmap

What we're building next. Submit feature requests.

View roadmap ↗
Support

Support

Access technical support and operational assistance.

Get support →
Status

Service Status

Real-time platform availability and incident history.

Check status ↗

Chart the data you already replicate.

Request a free trial or talk with the MOLO17 team about using Visualize to publish live views of replicated data without another BI copy.