Skip to main content
Agent installation is only required for Agent mode. If your source and destination are reachable over the internet (Snowflake, BigQuery, public RDS, SaaS APIs), use Hosted mode and skip this page. See Hosted vs Agent or When to use the agent.
The Zwiron Agent is a lightweight binary that runs inside your network. Sync work happens on the agent; it dials outbound only to Zwiron — no inbound ports, VPN hairpin, or firewall holes on your side.

What you get

  • Outbound connection to the control plane (HTTPS / gRPC on port 443)
  • Sync execution next to your data (full refresh, incremental, CDC)
  • Agent-mode credentials decrypted locally with the agent’s RSA key
  • System service that auto-starts on reboot (native install)
  • Same UI: connections, pipelines, catalog, and quality

Prerequisites


1. Create an agent token

  1. Sign in at zwiron.com
  2. Open Settings → Agents
  3. Click New Agent and copy the one-time install token
The dashboard also shows a ready-to-run install command with your token filled in.
This:
  1. Resolves the latest version from https://downloads.zwiron.com/agent/channels/stable.json
  2. Downloads zwiron-agent-<version>-<os>-<arch>.tar.gz from the CDN
  3. Verifies the SHA-256 checksum
  4. Installs the binary to /usr/local/bin/zwiron-agent
Pin a version (optional):
Register and start the service:
Verify:
You should see the agent as online under Settings → Agents.

3. Install (Windows)

Download the Authenticode-signed exe (preferred) or the zip that contains the same binary: Latest version: stable.json · download page In an elevated PowerShell / cmd from the download folder (rename the versioned exe if you want the short name):
Windows should show publisher Zwiron (or your company legal name on the cert). Verify:
If Microsoft Defender SmartScreen still says “Windows protected your PC” on a newly signed release: More info → Run anyway. That warning fades as the publisher reputation builds. Chrome may also flag a rarely downloaded .exe until Safe Browsing reputation catches up — use Keep / Download suspicious file, then verify the signature above.

4. Direct downloads

Prefer a manual download? Grab signed builds from the CDN: Latest version string: stable.json Also on each release path: checksums.txt and checksums.txt.minisig (minisign). Browse platforms on zwiron.com/download/agent.

5. Docker

Official public image on Docker Hub: zwiron/agent (linux/amd64 + linux/arm64). Quick start
Mount /data so RSA keys and checkpoints persist across restarts. Production — pin a version (recommended):
Foreground / debug:
Hub page (bookmark this): https://hub.docker.com/r/zwiron/agent

6. Kubernetes


7. Use the agent day to day

Register, start, stop

Create Agent-mode connections

  1. Confirm the agent is online
  2. Connections → New connection
  3. Choose Agent execution and select this agent
  4. Enter DB credentials (encrypted to this agent’s key)
  5. Profile / test the connection
  6. Create a pipeline as usual (full, incremental, or CDC)

Multiple agents

Install one agent per environment or network segment (staging vs production, AWS VPC vs on-prem). Each agent appears under Settings → Agents. Assign connections to the agent that can reach that database.

Security model (short)

  • Outbound-only — agent initiates connections; no inbound ports on your side
  • mTLS — agent authenticates to the control plane with ECDSA certificates
  • Credential isolation — Agent-mode DB passwords are encrypted to the agent’s RSA key; Zwiron stores ciphertext
  • Row data moves on your network during sync; the control plane receives operational metadata
Details: Security · The Agent concept

Troubleshooting

On Linux: sudo systemctl status zwiron-agent
On macOS: check the launchd service via sudo zwiron-agent status
Confirm outbound access to get.zwiron.com and downloads.zwiron.com.
Check the channel and artifact:
curl -fsSL https://downloads.zwiron.com/agent/channels/stable.json
Re-download; do not ignore checksum errors. Compare against checksums.txt for that version. Optionally verify checksums.txt.minisig with the published minisign public key in the agent repo.
The agent must reach the database host/port from its machine (not from your laptop). Check security groups, local firewall, and DB user permissions for your connector.
Allow HTTPS 443 egress to agent.zwiron.com. Corporate proxies may need allowlisting.
The Windows agent is Authenticode-signed. Chrome Safe Browsing and SmartScreen still warn on brand-new publisher reputation. Chrome: Keep / Download suspicious file. SmartScreen: More info → Run anyway. Then verify the publisher:
Status should be Valid and the signer should be Zwiron (or your company legal name).

Last modified on September 5, 2026