Team Sync & Device Transfer

Settings → Transfer / Team sync has two different ways to get your setup — servers, apps, databases, templates, every credential involved — onto another machine. Pick based on whether this is a one-time move or an ongoing relationship.

Team sync

Team sync creates a tightly restricted account on one of your servers for each person (or device) you add. That account can do exactly one thing — hand back its own encrypted copy of your current setup — and nothing else about the server changes or becomes reachable through it.

Adding a member

1. Go to Settings → Team sync, pick which server should host the account (only asked if you have more than one), and click + Add team member.
2. Give them a label (their name) and a password — 12+ characters, or click Generate one for a secure random password.
3. Click Add member. DeployOS creates the account, then makes a completely fresh connection using nothing but that password to confirm it can actually read the file back before calling it done. If that check fails for any reason, the account is rolled back entirely — nothing partial is left on the server.
4. The server address and that member's username/password are shown once, right after creation, with a Copy all button. They aren't retrievable again after you navigate away — send them to your teammate before you do.

Share just those three things with your teammate — host:port, username, password. They open a brand-new DeployOS install and join with that; no SSH key needs to change hands.

Keeping members up to date

Once someone's joined, this install pushes them a fresh copy automatically after you make changes, usually within about a minute. You can also force it immediately:

• Push now — re-pushes the current setup to every member on that server right away.
• Sync everyone now — shown right after adding a member, catches them (and anyone added earlier) up to the latest version instead of waiting for the automatic push.

Pushing is one-directional and non-destructive to the receiving side: a push lands as an available update on the other end, which that install still has to approve pulling — see below.

Removing a member

Click Remove next to their name. This deletes their account on the server entirely — nobody else's access is touched.

The receiving side

On a device that's joined someone else's team sync, Settings → Synced from lists every setup it's joined, with the last version pulled and when. While DeployOS is open, it checks for new pushes every few minutes and prompts you when one's available — or check/pull manually:

• Check now — looks for a newer push without applying anything.
• Sync now — pulls and applies the newer version, and shows a summary of what changed (servers, apps, databases affected).

Nothing from a push ever applies automatically — pulling always requires this explicit action, even when the app auto-detects one is available.

Stop syncing on a subscription only makes this install forget it locally; it doesn't touch the account on the server. To fully revoke a member's access, remove them from the owner's side instead.

One-time device transfer

For moving your own install to a new machine — no server or SSH account involved, nothing sent over any network:

1. On the old device: Settings → Transfer → Export from this device. This generates a one-time code, then an encrypted blob containing everything (servers, apps, databases, secrets).
2. Copy both the code and the blob over to the new device however you like (a password manager note, an encrypted message — anything other than posting them somewhere public, since together they unlock everything).
3. On the new device: Settings → Transfer → Import from another device, paste both, and import.

This is a single snapshot taken at export time — it doesn't keep syncing afterward. If you want an ongoing connection instead (for a teammate, or your own second device you'll keep using alongside this one), use team sync above.