Search docs.molo17.com

    Install with the Gluesync kit

    Start at Get Gluesync and follow the setup wizard. The resulting kit installer is the supported default for a self-managed deployment: it validates the host, prepares the container runtime where supported, downloads the licensed services, and starts the Control Plane.

    How-to guide

    For a step-by-step walkthrough tested on a running Gluesync, see the how-to guide Install Gluesync on Linux and size the host.

    Installer versions and what changed in each tool are on the Installers changelog.

    Included Prometheus and Grafana

    The default Gluesync installation kit already includes Prometheus and Grafana. For this kit, you do not install or configure a second Prometheus or Grafana.

    In the Control Plane, Metrics and insights (gauge icon, left menu) is that included Grafana. The default Grafana login is admin / password.

    On Windows, Gluesync itself is under C:\Program Files\Gluesync. A path such as C:\Program Files\GrafanaLabs is a separate Grafana Labs installation, not the Gluesync kit.

    See Monitoring for the included stack. A Prometheus or Grafana you run yourself is optional, and only that path uses the import and scrape steps on Prometheus and Grafana dashboards.

    You do not need to install Docker or write a Compose file before starting the wizard. The manual Docker guides are only for system administrators whose infrastructure policies require a DIY deployment.

    Before you run it

    1. Check system requirements.

    2. Request the Gluesync kit for the required source and target.

    3. Keep the kit ID from the download email available.

    4. If you need a fresh copy of an installer or lifecycle tool, validate your licence under Installation kits & tools.

    5. Make sure the host can reach the endpoints in System requirements.

    6. Make sure ports 80 and 443 are free on the host. The installer checks them, and checks that the kit ID has a kit on the download server.

    The installer checks the host before it installs anything and reports each problem with a GS-PRE code and a fix. See Installer error codes and troubleshooting.

    The installer changes container-runtime and logging configuration. Use a dedicated host for production, take a backup of existing runtime configuration, and run the installer with the administrative privileges requested for the platform.

    Linux

    Run this command on the server, from an account that can use sudo:

    curl -fsSL https://molo17.com/gs-content/utils/docker-installer.sh | sudo bash

    The command is the same as in earlier releases. From installer 2.0 (Gluesync Control 1.4.5), docker-installer.sh is only the way in: it downloads Gluesync Control for Linux for the CPU of the server (amd64 or arm64), checks its size and SHA-256 against the MOLO17 update catalog, and runs gluesync install. A file that does not match is refused and nothing runs. Gluesync Control does the installation itself, so the server needs only curl or wget, and sha256sum, shasum or openssl.

    In a terminal, gluesync install opens a guided screen:

    1. Welcome: what is going to happen, and the server it found (distribution, CPU cores and memory).

    2. License agreement: the MOLO17 Gluesync End User License Agreement and, when the kit includes it (kits packaged from October 21, 2026), its copy (eula.pdf, installed as /opt/gluesync/eula.pdf). Tick I accept the license terms to continue; the acceptance is written to /var/log/gluesync/install.log. The Gluesync platform is licensed under the MOLO17 Commercial License; a few components, such as Chronos and Conductor, are open source under the GNU GPL v3. From Gluesync Control 1.4.9.

    3. How do you want Gluesync to be installed?

      • Online: quicker and automated. It pulls from the MOLO17 repository and installs all dependencies, Docker included. You enter the kit ID from the download email.

      • Offline: meant for air-gapped environments. You give the platform package and the kit file. Docker must already be installed. See Offline installation and updates.

    4. Checks: the prerequisite checks, each with its GS-PRE code, a message and a fix. A soft block (a code that can be accepted) offers Accept and continue after a confirmation that names what you accept. A hard block only offers Quit. See Installer error codes and troubleshooting.

    5. Docker: online, what is installed and from where. Offline, the Docker that was found, which is left as it is.

    6. Ready to install: whether to start Gluesync when the installation is done (on by default) and whether Gluesync Control updates itself every day (on by default).

    7. Installing Gluesync: the steps, a progress bar and the output. Press Ctrl+C to stop.

    8. Done: the address of the Control Plane, the admin / admin sign-in (change the password after the first sign-in), the install folder and the services. Open Gluesync Control continues into the Gluesync Control screen. A failed install shows the code, the message, what to try and the log file.

    Without a terminal (cloud-init, CI, ssh without a tty), gluesync install asks nothing and takes every answer from GLUESYNC_* variables or options. It prints, and logs, that installing Gluesync means accepting the End User License Agreement. Pass them to sudo explicitly:

    curl -fsSL https://molo17.com/gs-content/utils/docker-installer.sh | sudo GLUESYNC_KIT_ID=a1b2c3d4e5f6 GLUESYNC_START=y bash

    GLUESYNC_ACCEPT=GS-PRE-040 (or --accept) accepts a soft block, GLUESYNC_NONINTERACTIVE=1 never asks, even in a terminal, and --kit, --offline, --package and --kit-file are the options of sudo gluesync install. The full list is in Install Gluesync.

    When Gluesync is already installed in /opt/gluesync, the installer does not install over it: it offers an update, online or from a package file (gluesync update).

    Gluesync is installed under /opt/gluesync. The installer puts Gluesync Control for Linux on the PATH: run sudo gluesync for a terminal screen, or sudo gluesync status, start, stop, restart, update and collect-logs as commands. If you chose not to start Gluesync at the end of the installation, start it with:

    sudo gluesync start

    Supported distributions and current runtime requirements are listed in System requirements.

    Windows Server

    Antivirus and EDR software, such as Microsoft Defender or Elastic Defend, can stop the installation or keep the containers restarting. Agree on exclusions with your security team before you run the installer. See Prepare antivirus and EDR software.
    1. Sign in to the server with a local administrator account.

    2. Download and run the Gluesync setup wizard (gluesync-windows-setup-wizard.msi). See Windows setup wizard.

    3. Follow the wizard. If Windows requests a restart, restart the host. Setup continues on its own.

    4. Keep the Gluesync launch window open until it says that Gluesync is ready.

    5. When installation completes, use the generated shortcut or the address shown in the launch window.

    Other options: docker-installer-windows.ps1 for Server Core and scripted installs, and the legacy MSI (gluesync-platform-installer.msi). Both are described in Legacy MSI and PowerShell installers.

    Gluesync is installed under C:\Program Files\Gluesync, together with Gluesync Control (setup wizard 1.4.0 and later). The Gluesync Control desktop shortcut opens its window, and the gluesync command works from an elevated terminal. To start Gluesync manually:

    gluesync run
    Installs made with a setup wizard before 1.4.0 start Gluesync with .\run.ps1 from the installation folder.

    For Windows-specific prerequisites, silent installs and troubleshooting, see Windows setup wizard.

    macOS

    1. Install and start Docker Desktop.

    2. Extract the kit ZIP.

    3. In the extracted directory, run:

      ./run.sh
    4. Open the Control Plane URL printed by the script.

    macOS is appropriate for evaluation and local development, not a production deployment.

    Verify the installation

    1. Open the Control Plane.

    2. Sign in with admin / admin.

    3. Set a new password when prompted.

    4. Confirm that Data pipelines loads without a Core Hub connection error.

    5. Open the notifications menu and resolve any startup error before creating a pipeline.

    Continue with Build your first pipeline.

    Manage the installation

    Use the tools supplied with the kit instead of raw Docker Compose lifecycle commands. If a tool is missing or outdated, download it again from Installation kits & tools after validating your licence.

    Task Linux macOS Windows Server What the tool does

    Start or restart

    gluesync start

    ./run.sh

    gluesync run

    Finds the supplied Compose file, prepares required environment settings, pulls images during initial setup, and starts the stack with orphan handling.

    Stop

    gluesync stop

    ./stop.sh

    gluesync stop

    Finds the supplied Compose file and stops the complete Gluesync stack with orphan handling.

    Update

    gluesync update

    ./update.sh

    gluesync update

    Checks the selected release channel, updates managed image references, and restarts the stack when required.

    Collect logs

    gluesync collect-logs

    ./collect-logs.sh

    gluesync collect-logs

    Collects logs, configuration and diagnostics into a support bundle, and uploads it into your support ticket when you give its voucher (--voucher GSV-XXXX-XXXX-XXXX). A ticket number and an e-mail address still work as a legacy option.

    On Linux, gluesync is the command line of Gluesync Control for Linux (put on the PATH by the installer): run it with sudo from any folder. Installations made with an older kit still have the scripts of that kit (./run.sh, ./stop.sh, ./update.sh, ./collect-logs.sh) in /opt/gluesync, and they keep working. Run the macOS tools from the extracted kit directory. On Windows Server, run gluesync from an elevated terminal: it is the command line of Gluesync Control (setup wizard 1.4.0 and later) and works from any folder. Installs made with a setup wizard before 1.4.0 use .\run.ps1, .\stop.ps1, .\update.ps1 and .\collect-logs.ps1 from the installation folder. All of them preserve the required environment, Compose selection, validation, and lifecycle sequence.

    Do not replace these tools with docker compose up, down, stop, or pull. Raw Compose commands bypass the Gluesync lifecycle checks and can select the wrong files or remove persistent state.

    Remove an installation

    Before uninstalling, take a configuration backup and copy any required data volumes.

    Linux

    Run ./docker-uninstaller.sh. Add --purge-runtime only if the container runtime and all of its data should also be removed.

    Windows Server

    Run .\docker-uninstaller-windows.ps1 from an elevated PowerShell session. It removes the Gluesync platform and keeps the Docker engine. Add -PurgeRuntime to also remove the Docker engine and its data, and the Containers feature when the installer turned it on. Hyper-V is never touched. Use -Force to skip the confirmation (required without a console) and -NoRestart to restart later: the uninstall then finishes by itself at the next startup.

    Uninstalling can remove Gluesync containers and volumes. Purging the runtime can also affect workloads unrelated to Gluesync.

    When the kit installer is not suitable