Core Hub

Core Hub is the control and processing service at the center of a Gluesync deployment. Users normally work through the Control Plane; agents and optional services connect to Core Hub behind that interface.

For the complete data path and deployment boundaries, see Gluesync architecture.

What Core Hub owns

Configuration: Pipelines, connector assignments, entities, mappings, filters, transformations, alerts, users, and global settings.
Orchestration: Pipeline lifecycle, entity operations, snapshots, maintenance mode, and coordination with connected services.
Data processing: Mapping, filtering, transformation, and routing between source and target agents.
Control Plane: The web application used to configure and operate Gluesync.
APIs: REST, WebSocket, and MCP surfaces used by the Control Plane and external automation.
Observability: Pipeline, agent, and entity metrics exposed to the Control Plane and Prometheus.

Core Hub does not replace the source or target database and is not a vendor-owned staging store.

What runs elsewhere

Agents: Capture changes from sources or write records to targets. They run close to the systems they connect.
Durable source queue: Buffers captured changes on the source-agent side so an interruption between the agent and Core Hub does not require the source database to retain the event in memory.
Control Plane apps: Schedules, Query Studio, Query Forge, Metrics & Insights, Modules Manager, and Automator may depend on additional connected services.

See Components, apps, and tools for the distinction between a user-facing app and the service behind it.

Use Core Hub

Goal	Documentation
Use the web application	Control Plane tour
Build and run pipelines	Pipelines
Automate platform operations	Core Hub REST API
Connect an AI client	Core Hub MCP server
Monitor the service and data flows	Monitoring
Back up configuration	Backup and restore

Goal

Documentation

Use the web application

Control Plane tour

Build and run pipelines

Pipelines

Automate platform operations

Core Hub REST API

Connect an AI client

Core Hub MCP server

Monitor the service and data flows

Monitoring

Back up configuration

Backup and restore

Security boundary

Users authenticate to Core Hub through local accounts or OIDC. Roles govern Control Plane and API operations. Node-to-node encryption and TLS protect communication where configured.

Start with Users and roles, OIDC, and node-to-node encryption.