Deploy and operate Gluesync
Start with the setup wizard at Get Gluesync. It provides the installation kit and standard setup flow. Use the manual deployment references only when your infrastructure team must control the container runtime itself.
Choose a deployment path
| Path | Use it when | Guide |
|---|---|---|
Kit installer |
You want the supported default on Linux, Windows Server, or macOS. The Get Gluesync setup wizard prepares this path. |
|
Docker Compose (DIY) |
Your operations team manages the container runtime and must inspect or customize every service. |
|
Kubernetes and Helm |
Gluesync must run in an existing Kubernetes environment with your ingress, storage, and registry policies. |
|
Offline |
The target environment cannot reach the Gluesync registry or other required Internet endpoints. |
|
Do not begin with the Docker or Podman references just because Gluesync uses containers. The setup wizard and kit handle the standard installation. Those pages are DIY references for system administrators who cannot use the default flow. |
Installation sequence
-
Check system requirements.
-
Request or download a Gluesync kit.
-
Follow one deployment path from the table above.
-
Sign in to the Control Plane.
Day-two operations
| Task | Guide |
|---|---|
Prepare an evaluation for production |
|
Update platform services |
|
Back up, restore, or duplicate configuration |
|
Perform routine administration |
|
Monitor pipelines and infrastructure |
|
Configure alerts and notifications |
|
Diagnose a failure |