What sync carries, and what it never carries

What each app sends through your Edgely account, what stays in the vault on each device, and how the sync password protects what travels.

Applies to
Edgely Console, Edgely Database Manager
Updated

Sync copies your connections and some of your settings between the computers where you use Edgely Console or Edgely Database Manager with one Edgely account. It never carries a password, a key or a token: those stay in the vault of each device. This page says what each app sends, how it is encrypted, what the Edgely server can read, and how connections shared with an organization differ.

Checked on 2026-11-02 against the code of Edgely Console 1.1.0, Edgely Database Manager 1.2.0 and the Edgely server.

Turn sync on

Sync is off until you turn it on, on each device and in each app.

  1. Open Settings > Account & Sync and sign in to your Edgely account.
  2. Under 1. Encryption, type the sync password twice and press Set Password. On your account's first device this chooses it, at least 12 characters; on every other device, in either app, type the same one.
  3. Under 2. Device Linking, press Link This Device.
  4. Under 3. Sync Configuration, turn on Enable Sync, then the categories you want. Every category starts off.

Each app syncs its own data: Console connections never appear in Database Manager, nor the other way round. The sync password belongs to the account, so it is the same in both apps.

What each app sends

SwitchEdgely Console 1.1.0Edgely Database Manager 1.2.0
ConnectionsName, host, username, each protocol with its port and settings, group, tags, notes, favorite, and the link to its jump host. The groups travel with them (names and nesting; icons and order stay on each device) and have no switch of their ownName, database type, host, port, username, database and schema, SSL mode, SSH tunnel settings (host, port, username, sign-in method and the path of the key file, never the key), group, color, notes, favorite, environment and connection properties, except a property named like a credential
PreferencesThe theme and accent colour, the terminal theme and font size, the file browser views and icons, the paste confirmations, the session log options, SSH keepalive, timeout and reconnect, plugin update checks and announcementsThe theme and accent colour, editor, query, data grid and export options, the connection timeout, the update and tray options, whether AI is on, announcements, and the colors of the groups in the explorer

Neither app syncs the language, the vault or its settings, AI provider settings or snippets, nor which vault entry a connection uses. Database Manager's query history, its reports and when each connection was last used stay on each device. What arrives applies at once, with no restart.

A category switched off stops travelling, and with every category off the device downloads nothing.

In Console, a group created with the same name on two devices before they first synced arrives as Name (synced).

What never travels

Passwords, SSH private keys and their passphrases, tokens, client secrets and everything else in the vault stay on the device that holds them. A connection that arrives by sync has no credential: give it one the first time you connect, and it stays on that device.

Each app checks every item before sending it, and the server refuses any that is filed under a credential name or holds a credential-shaped field (such as password or private_key) in content it can read; it cannot read your encrypted items, so for those it checks only their name. A refused item is not stored, and the rest of the push goes through.

A Database Manager connection property named like a credential (password, client_secret) stays on the device: the rest of the connection syncs, and the app's log names the property. Do not put a secret in a connection property.

No setting, plan or organization policy turns credential sync on. To move credentials to another computer, use a password-protected export: see Encrypted import and export. How each device's vault is unlocked is in Silent mode and master password.

How your sync data is encrypted

  • The app turns your sync password into a 256-bit key with Argon2id (64 MiB of memory, 3 passes) and a salt that belongs to your account, so every device derives the same key from the same password.
  • Every item is encrypted with AES-256-GCM, under a new random nonce each time, before it leaves the device. An altered item fails to decrypt and is skipped, never applied.
  • The key is kept in the operating system's keychain, so the app does not ask for the password again. The password itself is not stored.
  • To check a password, the server keeps the salt, the Argon2id settings and an HMAC-SHA256 computed with the key over a fixed label. It shows whether a device derived the right key without revealing the key, but anyone holding these values could test guesses at the password offline, which Argon2id slows down without stopping. A new sync password, the account's first or one set by a reset, needs at least 12 characters in both apps; a device joining the account types the one the others use, even a shorter one (Database Manager refuses fewer than 4 characters).

A device with another password is stopped before it writes anything, with That sync password does not match the one your other devices use. in Console, or That sync password does not match the one your account already uses. in Database Manager.

What the server holdsReadable by the server
Your account; your linked devices with their name (the computer's name unless you change it), platform and its version, app version, the address each linked from, and when each was last activeYes
The app and category of each item, which device wrote it, when, and its versionYes
A SHA-256 checksum of each item's unencrypted content, which devices use to check what they downloadYes
Connection names, hosts, ports, usernames, groups, notes and preferencesNo: encrypted
Connections you share with your organizationYes: see below
Passwords, keys and tokensNever sent

A forgotten sync password

The devices that already sync keep working, since their key is in their keychain: you need the password only to set up another device. Edgely does not have it and cannot decrypt your synced data without it.

If nobody remembers it, start over from Edgely Console (Database Manager has no reset):

  1. On a Console device that has never had the sync password, type a new one of at least 12 characters under 1. Encryption and press Set Password.
  2. Console answers That sync password does not match the one your other devices use. and offers Reset and delete synced data. Choose it.
  3. The new password becomes the account's, and everything synced to your account is deleted from the server, for every Edgely app, including the connections you shared with your organization. Local connections and vaults are not touched; this device uploads its data again on its next sync, the connections it shares with your organization included.
  4. Straight away, on each other Console device, press Sync Now: it notices the reset, forgets the old key and shows The sync password was reset on another device. Enter the new one to sync this device again. Type the new password under 1. Encryption. A periodic sync does not check, so a device left alone notices only when it next starts or syncs a change, and until then it can replace what the reset device uploaded. Database Manager notices the next time it starts and shows Sync is paused on this device: type the new password there too.
  5. A connection shared from another device may not be sent again by itself: if a colleague no longer sees it, share it again from that device (Stop sharing with the team, then Share with the team).

Change accepts only the password the account already uses: moving to another one is this same reset.

Connections shared with your organization

When your Edgely license comes from an organization, Share with the team in a connection's context menu shares it with the other members. This is separate from your personal sync:

  • A shared connection is stored readable, not end-to-end encrypted: the Edgely server and your organization's administrators, on edgely.io, can read it, since each member's key is different and an encrypted entry would be unreadable to the others.
  • It never carries a credential, and the same checks apply to it. Console shares the name, host, port and type of the first enabled protocol, username, tags and notes; Database Manager the name, database type, host, port, database, username and notes. Protocol and SSH tunnel settings and the jump host stay behind: each colleague connects with a credential from their own vault.
  • Sharing needs the device's sync password, its link and Enable Sync on. To receive colleagues' shares, also turn Connections on.
  • Edgely Console lists what colleagues share on the Connections page, and Database Manager in its Connections Manager, under the groups, headed Shared in and the organization's name, each entry with Shared by and its author. The list is read-only.
  • Only the member who shared an entry, or an owner or administrator of the organization, can change it. Stop sharing with the team removes the entry at each colleague's next sync; it cannot erase what someone already read.
  • Removing or suspending a member also revokes their devices in the apps the organization licenses, unless they have a plan of their own: those devices stop syncing altogether, personal data included, and linking them again does not undo it.

Devices and their limit

Each app links a device on its own, and the limit counts devices per app: a computer linked in Console and in Database Manager counts once in each.

PlanDevices
Free1 per app
Database Manager3 in Database Manager
Console (includes Database Manager)5 in each
Suite5 in each
Teams5 per member, in each app

On the free plan only one computer per app can link, so syncing between two computers needs a plan. With several plans, your own or your organization's, the highest limit applies.

A link beyond the limit is refused. Free a seat by unlinking a device: from either app once that device has not synced for 24 hours (Deactivate Device in Console, Deactivate in Database Manager), or at once from your devices on edgely.io.

An unlinked device stops syncing the next time its app starts or opens Account & Sync, and Link This Device brings it back while the plan has a seat free. A device reported stolen, or removed by an organization administrator, is refused by the server on every sync, and linking it again does not undo that.

Edits, deletions and conflicts

  • When two devices change the list between syncs, the lists are merged connection by connection, and each connection keeps its most recent edit. Two copies of one server created before the devices first synced become one connection.
  • In Console, deleting a connection is synced: the other Console devices delete it at their next sync, and a device that still has it cannot bring it back. Deleting a group is not synced, and a device that still has the group brings it back.
  • In Database Manager, deleting a connection is not synced. The other devices keep it, and their next sync can bring it back to the device where you deleted it. To remove one for good, turn Enable Sync off on your other devices, delete it on each, then turn sync back on.
  • A device that has lost the synced connections does not upload what it has left in their place. In Console, use Restore connections from sync under Backup & Restore in Settings > Account & Sync; in Database Manager, import an export.

Turning sync off

  • Enable Sync off stops the device sending and receiving. Nothing is deleted, on the device or on your account.
  • A category switched off stops travelling (see above); what it already synced stays on your account.
  • To delete what is synced to your account, use the reset described above, or delete your Edgely account.

Something missing or wrong?

Documentation gaps are bugs. Tell us which page you were reading and what you expected to find.

Send feedback →

Product names, logos and brands mentioned on this page are the property of their respective owners. They are used for identification and comparison only, and their use does not imply any affiliation with or endorsement by them.