Search docs.molo17.com

    Components, apps, and tools

    “Module” is a deployment term, not a user task. Some modules add a screen to the Control Plane, some run only as platform services, and some are engineering tools that most users should never operate directly.

    The main documentation navigation therefore groups content by what users do. Use this page only when you need to understand the underlying component boundaries.

    User-facing apps

    App Purpose

    Schedules

    Create scheduled jobs and event-triggered workflows in the Control Plane. Chronos is the service behind this screen.

    Query Studio

    Browse schemas, run SQL, inspect results, and manage saved queries.

    Query Forge

    Expose several connected systems through one federated SQL endpoint for JDBC and BI clients.

    AI Studio

    Use a configured LLM and governed Core Hub tools from an in-product chat.

    Enterprise brain

    Give every agent and every MCP client one shared schema graph, agent memory, skills, and approved company tools.

    Automator

    Back up, restore, duplicate, and bulk-create pipeline configuration through a guided interface.

    Modules Manager

    Inspect Conductor-managed components and start, restart, stop, or remove them.

    These names are the terms users see in the Control Plane and are the terms used in task guides.

    Integration endpoints

    Core Hub REST API

    Automates platform administration and pipeline operations. See Core Hub REST API.

    Core Hub MCP server

    Exposes 149 built-in tools plus optional dynamic database tools to AI clients, including the Validator, the Enterprise brain, and published agents. See Core Hub MCP server.

    SDKs

    Provide language-specific clients for supported integration workflows. See SDK overview.

    Platform services

    Core Hub

    Owns configuration, orchestration, routing, APIs, and the Control Plane.

    Agents

    Connect Core Hub to source and target systems.

    Chronos

    Executes schedules and trigger flows created in the Schedules UI.

    Conductor

    Manages supported deployable components behind Modules Manager.

    Gluesync Kubernetes Operator (GKO)

    Takes Conductor’s place for updates on Kubernetes. See Gluesync Kubernetes Operator (GKO).

    Whisperer

    Provides database access used by data-query capabilities.

    Operators may need these names for deployment or troubleshooting, but end-user procedures should lead with the screen or task rather than the service.

    Engineering and migration tools

    Bootstrapper

    A lower-level scripting toolkit for bulk pipeline and entity configuration. It is not an ordinary end-user feature and is intentionally absent from primary navigation. Use Automator for supported guided workflows.

    Syniti Replicate converter

    Converts metadata.xml into configuration that Automator or Bootstrapper can import. See Migrate Syniti Replicate metadata. For a step-by-step walkthrough, see the how-to guide Move a DBMoto or Syniti Replicate setup to Gluesync.

    The standalone Bootstrapper reference, Conductor reference, and Whisperer reference remain available for engineers who maintain those components.