Get Gluesync

A Gluesync evaluation is a kit: a time-boxed package with a license, an installer, and the charts you need to run the platform. Production customers use the same installers and update path; only the license file changes.

From request to first pipeline Four stages, left to right. One: request a kit at molo17.com/get-gluesync, picking a source and a target. Two: the kit arrives by email with a trial license, an installer, and Helm charts. Three: install it with the guided installer, or by hand with run.sh or helm install. Four: sign in to the Control Plane on port 1717 and build your first pipeline. From request to first pipeline 1 Request Pick a source and a target molo17.com/get-gluesync 2 Kit arrives 30-day license + installer Compose and Helm charts 3 Install Guided installer, or run.sh / helm install 4 Run Control Plane on HTTPS (443) Build your first pipeline

Request a trial kit

Open Get Gluesync and follow the setup wizard. You pick one source and one target connector; the wizard prepares the correct kit and installation path around that pair. If the pair you want is not offered, ask us rather than picking the nearest match.

After the request is reviewed you receive an email with the package. A typical kit includes:

  • A 30-day trial license (.dat) and the license agreement

  • A readme

  • The default installer for Docker Compose on Linux or Windows Server

  • Kubernetes Helm charts covering the components listed in the Kubernetes overview

Default credentials after install are admin / admin. Change them before the instance is reachable beyond your laptop. Sizing and network allowlists are on System requirements.

Licensed users can validate their .dat licence at Installation kits & tools to download the current kit or a fresh copy of an individual setup, start, stop, update, uninstall, or log-collection tool. Use this page instead of direct utility URLs in old instructions.

Install it

Path Start here

Guided installer (recommended)

Use the setup wizard on Get Gluesync, then follow Install with the kit. The standard path provisions the container runtime, applies baseline configuration, and starts the stack.

Docker Compose, DIY administrators only

Manual Docker Compose deployment. Use this only when your operations team must inspect or customize the supplied stack. The setup wizard is sufficient for normal installations.

Kubernetes

Kubernetes — install the bundled Helm chart with your values, including namespace, storage, and ingress.

Already have a license

Same installers. Apply the .dat file from Settings → Licensing. See Licensing.

Keep it current

The preferred in-app path is Platform updates in the Control Plane header (top right, next to notifications). It appears when Conductor is connected. Anyone who can view updates sees the control; applying them requires permission to change configuration.

Updates follow the release channel set under Settings → Global settings:

Channel Image tag Use

Official release (GA)

latest

Production. Tested, supported.

Beta

beta

Preview of upcoming features. Not for production.

Alpha

alpha

Unstable. Engineering and early access only.

Click Platform updates, then View details, then Update all. Services are updated one at a time, and each can be retried on its own if it fails.

Two things to know before you start:

  • Do not close the modal or the tab while it runs. When Core Hub itself updates you are logged out and returned to the login screen — that is expected, not a failure.

  • Agent containers are not in this list. It covers Conductor-managed Core Hub, module, and third-party services only; Conductor handles agents separately. Modules manager no longer applies updates at all — use it for component lifecycle.

Per-service states, the mandatory-update flag, and failure handling: OTA updates.

Outside the UI

  • Docker Compose — from the installation directory, run ./update.sh (Linux and macOS) or .\update.ps1 (Windows Server) and follow its prompts. Use the supplied stop and run tools for lifecycle operations; do not substitute raw Docker Compose commands.

  • Kubernetes — upgrade the release with the chart from your kit (helm upgrade against the chart directory you installed from). A helm rollout restart of a chart repo URL is not a valid update. See Kubernetes.

Related