Cross-Device Sync
Share your marketing workspace between your own devices through an end-to-end encrypted space: pairing, what syncs, review and push, and conflicts.
Settings → Sync keeps workspaces, content, assets, and schedules in step across your machines. Records are encrypted before they leave the device and travel only through a network, folder, or bucket you choose — there is no StoicSoft cloud in between.
Sync is a Pro feature, and every participating device needs its own active Pro entitlement (the same license or different ones). If Pro lapses on a device, its local data stays available but sync pauses there.
Choose a Transport
| Option | How data moves |
|---|---|
| Nearby — Same Wi-Fi | Directly between devices on the same private network. Both apps stay open during sync. |
| iCloud or synced folder | Through a folder managed by iCloud Drive, OneDrive, Dropbox, Nextcloud, or Syncthing. |
| Object storage | Through your own S3-compatible bucket: AWS S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO. Test connection checks access. |
For a folder or bucket, use Create New Space on the first device, then Join Existing Space on the others with the location shown under Use this location on the next device.
Encryption and Keys
Creating a space asks for an Encryption passphrase of at least 12 characters. The app generates a random space key and encrypts every record and media chunk with it (XChaCha20-Poly1305). The space manifest stores that key only wrapped — under a key derived from your passphrase with Argon2id, and under a recovery key. Your passphrase never leaves the device.
Save your recovery key now shows a key beginning STOIC-SYNC- exactly once. Store it away from this device: rejoining later needs the passphrase or that key.
The space key and bucket access keys stay in this device's credential vault.
What Syncs
| Group | Contents |
|---|---|
| Workspaces & products · Always | Workspaces, product profiles, device roles, automation owner |
| Content library | Generated posts, articles, and their statuses |
| Assets & designs | Asset metadata, collections, Design Studio documents |
| Video storyboards | AI Video Maker storyboards and revisions |
| Scheduling | Scheduled posts, channel targets, comment snippets |
| Automations | Repurpose pipelines and AI visibility trackers |
| App preferences | Portable settings such as layout customizations |
An admin device can turn off any group except the first; disabled data stays on each device.
API keys, OAuth tokens, and other credentials belong to no group — Credentials never sync. Some records arrive inactive on purpose: pipelines land paused without their source accounts or watch folders, trackers have no next run, and scheduled posts arrive as drafts unless already published.
Advanced → Managed media decides whether file bytes follow the metadata: Metadata only, On demand (default), or Keep all.
Pair a Device Nearby
- On the device that already syncs, click Pair device. To start a Nearby-only space instead, choose Nearby — Same Wi-Fi, stay on Show Code, enter a Space name and Encryption passphrase, and click Generate pairing code.
- The panel shows a QR code and a
STOIC-LAN1.code with Copy code. It expires after ten minutes. - On the new device — which must not already belong to a sync space — open Nearby — Same Wi-Fi → Enter Code, paste into Pairing code, and click Check code.
- Both screens show a Security fingerprint. If it matches exactly, click Fingerprints match on the device that showed the code, then on the new device. If not, click Cancel.
The code carries a one-time secret and a P-256 public key. Each device proves it derived the same pairing key, and the fingerprint comes from that key. The space key is sent only after both confirmations, encrypted with the pairing key. Nearby traffic accepts private-network addresses only, and every request and response is encrypted with AES-256-GCM.
Devices, Roles, and Automation
On Devices, an admin sets each device's role and can retire other devices:
- Admin — manages devices, roles, merges, and what syncs.
- Editor — creates content and pushes or fetches changes.
- Viewer — receives changes but never pushes its own.
Publishing, trackers, and pipelines run only on the device chosen under Scheduled automation. A new space starts at Paused on every device, so scheduled work stays idle until an admin picks an owner.
Advanced → Disconnect removes this device. Local data stays, and the shared space and other devices are not deleted.
Review and Push
Changes → How changes move has two modes, switchable from an admin device:
- Automatic — every sync pushes local edits and applies remote ones. Syncs run about once a minute and on launch, window focus, and wake.
- Review & push — On this device lists your edits as New, Edited, or Deleted; select them and push. Under From other devices, click Fetch, then Apply all or Skip selected.
Skipping keeps this device's version, so later edits to that record may surface as conflicts. Roles and the automation owner sync even in review mode.
Resolve Conflicts
When two devices change the same record without seeing each other's edit, sync keeps going: the edit with the later sync clock wins on every device, and the other version waits on Conflicts.
Expand a row to compare Kept automatically with Alternative, field by field, then choose Keep [device]'s version, Use [device]'s version (which syncs the alternative to every device), or Dismiss. Only an admin device can decide.
Next
- API Providers — the keys that stay on each device
- Assets — the library that managed media sync draws from
- Content Calendar — the schedule your automation owner runs