System Requirements
Before deploying Gluesync, ensure your environment meets these requirements for optimal performance.
Quick reference
Install Gluesync on a dedicated system
Gluesync should be installed on a dedicated third system, separate from both the source database and the target system.
Avoid running Gluesync on machines that already host databases or other resource-intensive or intrusive software (for example, endpoint protection/anti-virus), as this can impact performance and operational stability.
Linux system requirements at a glance
| Aspect | Details |
|---|---|
Supported distributions |
Linux LTS releases (Ubuntu 22.04+, RHEL 9+, Alma/Rocky 9, Debian 12). Choose Kubernetes nodes or Docker/Podman hosts depending on scale. No upfront containers knowledge required if using the Compose kit which comes with the Gluesync auto-installer. |
Hardware baseline |
* Docker/Podman compose (≤8 pipelines): 8 vCPU, 16 GB RAM, 200 GB disk * Kubernetes production (~50k RPS): 3 nodes totaling 16 vCPU, 32 GB RAM, 200 GB disk * Add storage headroom for Prometheus, backups, and caching. |
Container runtime |
Docker Engine + Compose v2, Podman + Podman-compose, or kubelet with CRI‑O/containerd. |
Best suited for |
Production workloads, multi-pipeline deployments, air-gapped or headless installations. |
Windows system requirements at a glance
| Aspect | Details |
|---|---|
Supported editions |
Windows Server 2022/2025 is recommended for production workloads, use Windows 10/11 (Pro or Enterprise) for lab/testing workloads. Gluesync runs on Windows-based docker images, which can be run on any Windows machine (and VMs too). |
Hardware baseline |
* 8 vCPU * 16 GB RAM (8 GB minimum for POC) * 200 GB free disk (SSD recommended) * Optional: extra 100 GB if enabling Prometheus/Grafana if you require high retention periods for metrics (e.g. 1 month) |
Container runtime |
Docker engine is required, which comes bundled with our installation kit (Auto-Installer). Docker Desktop (bundles Docker Engine + Compose) or Podman Desktop are also supported for lab environments. Compose kit installer can run without pre‑installing Docker, but Docker Desktop is recommended for troubleshooting. |
Reboot required |
A system reboot is required after installation to ensure all components and services are correctly initialized. |
Best suited for |
Small to mid-size Production workloads, POC/demo environments, lab setups, or small single-pipeline deployments that need a Windows UI (not required for Gluesync). |
|
If your Windows Server runs Docker behind a corporate proxy or needs to grant non-admin users access to the Docker named pipe, follow the dedicated workflow in the Docker installation guide: Windows Docker Engine: That section explains how to edit |
|
Docker Inc. and several upstream components announced end-of-life plans for Windows Server 2019 container support. As these dependencies sunset, Gluesync will phase out Windows Server 2019 compatibility in an upcoming release. Begin planning migrations to Windows Server 2022 (or Linux) to remain on supported ground. |
Network allowlist essentials
| Purpose | FQDN / pattern |
|---|---|
Docker Hub images |
https://*.docker.io, https://*.docker.com |
Gluesync backoffice APIs |
https://api.backoffice.molo17.com |
Gluesync FTP server for support logs updaload |
https://ftp.molo17.com |
Gluesync telemetry / log shipping (optional) |
https://logstash.molo17.com |
Gluesync documentation & updates |
https://docs.molo17.com, https://molo17.com, https://support.molo17.com |
|
If outbound internet is blocked, mirror the container images ( |
Prerequisites checklist
Containerized deployment setup
Gluesync is designed to run efficiently in containerized environments. We recommend using Docker, Podman, or Kubernetes for deployment, depending on your needs and familiarity.
| If you’re not familiar with containerized deployment, start with Gluesync’s Docker Compose deployment strategy—it ships with a handy installer that fully automates the setup, so you don’t need to install a separate container runtime when using the provided Compose kit; nor you are required to know anything about Docker and containers at all. |
Docker/Podman setup
| Requirement | Details |
|---|---|
Container runtime & compose |
Ensure one of the following is installed on your system: * Docker Engine and Docker Compose * Podman and Podman Compose (or Docker Compose with Podman) These are required to run the Gluesync Compose kit. |
Installation guides |
Docker: Gluesync’s comprehensive Docker installation guide Podman: Gluesync’s comprehensive Podman installation guide Additional reference guides: Docker: Docker Desktop (Windows, macOS, Linux - for POC/Demo) - Docker Engine binaries (Production Linux) - Windows Server for Windows Containers (Production Windows) |
Gluesync Compose Kit |
After installation, follow the Gluesync documentation for using the Compose kit you received via email. See Useful links below. |
Note |
Gluesync documentation provides basic installation guides for both Docker and Podman. For more detailed instructions, refer to the official container runtime documentation or community tutorials. |
Verify system requirements
You can autonomously verify if your system meets all the requirements by running our pre-flight checker tool. This tool performs various system checks and provides a detailed report of any missing requirements.
-
Download and run the pre-flight checker: Gluesync Pre-flight Checker
-
Follow the instructions in the repository to execute the checks
-
Review the generated report to identify and address any issues
|
The pre-flight checker verifies:
|
Kubernetes Setup
| Requirement | Details |
|---|---|
Kubernetes Cluster |
A running Kubernetes cluster (e.g., Minikube for testing, or a production-grade cluster for deployment). LTS Linux is recommended for production. |
kubectl CLI |
Install and configure |
Supported distributions |
Kubernetes (recommended), OpenShift, or an equivalent orchestrator. See production specs above for hardware guidance. |
Installation guides |
|
Gluesync Kubernetes deployment |
Refer to Gluesync documentation or contact support for deployment guides specific to Kubernetes environments. |
Note |
Gluesync documentation does not cover Kubernetes installation. For setup help, refer to the official Kubernetes documentation. |
Source database requirements
| Requirement | Details |
|---|---|
Connection details |
* Username and password * Connection string (IP address/port) * Table names * TLS certificates (if secure authentication required) |
Access permissions |
Database user must have appropriate read permissions |
Environment Specifications
POC / Demo environment
| Component | Requirement |
|---|---|
Operating system |
Windows, macOS, or Linux (LTS version recommended) |
Container platform |
Docker, Docker Compose, or Kubernetes |
Hardware |
* 8 GB RAM (minimum) * 8 vCPU * 100 GB free disk space (Additional space needed for Prometheus monitoring) |
Production environment
Kubernetes
Recommended specs for handling ~50,000 rows per second (RPS)
| Component | Requirement |
|---|---|
Operating system |
Linux (LTS version recommended) |
Container platform |
Kubernetes (recommended), OpenShift, or equivalent orchestrator |
Cluster configuration |
3 Kubernetes nodes for High Availability (HA) |
Total hardware resources |
* 32 GB RAM * 16 vCPU * 200 GB free disk space (Additional space needed for Prometheus monitoring) |
Docker compose / Podman
Recommended specs for single pipeline or up to two pipelines (small to medium deployments)
| Component | Requirement |
|---|---|
Operating system |
Linux (LTS version recommended) |
Container platform |
Docker Compose or Podman Compose |
Deployment scale |
Suitable for a single pipeline or up to two concurrent pipelines (small to medium deployments) |
Total hardware resources |
* 16 GB RAM * 8 vCPU * 200 GB free disk space (Additional space needed for Prometheus monitoring) |
|
These specifications are baseline recommendations. Actual requirements may vary based on:
|