How connections work
Connections behave differently depending on the execution mode selected:- Agent mode
- Hosted mode
- You enter credentials in the Zwiron dashboard
- Credentials are encrypted with the agent’s public RSA key
- Atlas stores the ciphertext; the agent also keeps a local encrypted copy
- When a job runs, the agent decrypts credentials locally and runs the sync — plaintext is not sent back to Zwiron
Source vs. destination connections
A connection can be used as a source, a destination, or both — depending on the connector type.
For example, a Postgres connection can be used as a source (reading tables) or a destination (writing tables). A Snowflake connection is typically used as a destination.
Testing a connection
Click Test Connection to verify connectivity. The test:- Routes through your agent (Agent mode) or Zwiron’s hosted engine (Hosted mode)
- Checks network reachability — can the engine reach host:port?
- Checks authentication — are the username and password valid?
- Checks database access — can the user access the specified database?
Connection status
Reusing connections across jobs
One connection can be the source or destination for multiple jobs. If your database credentials change, you only need to update the connection once — all jobs using it will automatically use the new credentials on the next run.Permissions
Zwiron needs the minimum permissions required for each operation:- Source connections — read-only access to the tables you want to sync
- Destination connections — write access (INSERT, UPDATE, CREATE TABLE) to the target schema
- CDC sources — additional replication permissions (see the connector-specific guide for exact SQL)