Your Marketing Workspace on Every Machine You Use

The laptop has your content library. The desktop has the bigger screen you actually want for Design Studio, and because it is the machine that stays on, it is also the one running your scheduled posts. Somewhere between the two, a campaign you drafted on the couch is invisible from the desk, and the only way to move it is to copy the text into a note and paste it back out on the other side.

Local-first tools make that trade deliberately. Your keywords, drafts, assets and API keys stay on your machine because there is no server holding them. The bill for that arrives the first time you sit down at your other machine and find an empty workspace looking back at you.

What changed

Settings → Sync now creates an encrypted space that carries your workspace to every device you add to it. You can start a campaign on the laptop, finish it at the desk, and never hand the contents to a server in between — because there is no StoicSoft cloud to hand it to.

How it works in practice

Pick a transport, not an account

There is no sign-up step, because there is no account. You choose how the encrypted records travel between your own machines, and the app treats all three the same way underneath.

Nearby pairs two running apps on the same Wi-Fi and moves records directly between them. Nothing is stored anywhere else, and both apps stay open while it works. A synced folder writes encrypted batches into a directory that iCloud Drive, Dropbox, OneDrive, Nextcloud or Syncthing already keeps in sync for you — your provider moves the files and sees only ciphertext. Object storage points at an S3-compatible bucket you own, including AWS S3, Cloudflare R2, Backblaze B2, Wasabi or MinIO, which is the option that works when the two machines are never on at the same time.

Whichever you pick, you name the space and set an encryption passphrase of at least twelve characters. The app then shows a recovery key exactly once. Store it somewhere separate from the passphrase — rejoining the space later needs one or the other, and neither can be recovered for you.

Confirm the second device is really yours

Pairing is a two-step handshake rather than a code you paste and hope about. The one-time code proves an encrypted pairing transcript between the two apps, and then both screens display the same security fingerprint. You confirm only if the digits on this screen match the digits on the other one, which is the check that a stranger on your network cannot fake.

Every participating device needs its own active Pro entitlement. Two machines can share one license key or use entirely different ones — the space never compares, hashes or stores license identity.

Decide what actually travels

Not everything is worth carrying to every machine. The What syncs grid lets an admin device switch whole sections on and off: Content library, Assets & designs, Video storyboards, Scheduling, Automations and App preferences. Workspaces and products are always on, because they are what everything else hangs off.

Turning a section off is not destructive. That data stays on each device from then on, and if you turn it back on later, the space restores the records it was already holding. Media follows its own rule: metadata always syncs, while the actual bytes in your managed asset library obey the policy you pick — Metadata only, On demand, or Keep all if you want every file resident on this machine.

Sync in the background, or review it like version control

Automatic mode converges every device on its own. Local edits get pushed on the next cycle, incoming ones apply as soon as they arrive, and you never think about it again.

Review & push is the git-shaped alternative. Your edits wait in On this device until you select what to share and push it, and incoming work waits in From other devices until you fetch and apply it. You can skip a staged change to leave your local copy untouched — and if you later edit that same record yourself, it surfaces as a conflict instead of quietly disappearing.

When two machines edit the same thing

Editing the same post on two devices does not pick a winner and throw the other version away. Both sides are kept, and the losing version waits in the Conflicts tab rendered as a real record — its title, platform chip, excerpt, media and the fields that actually differ — so you are choosing between two recognisable drafts rather than two timestamps. An admin device presses Review and keeps one.

Roles decide who can do that. Admin manages devices, roles, merges and what syncs; editor pushes and pulls normally; viewer receives changes but never pushes its own. The last remaining admin cannot be demoted, so a space cannot lock itself out.

One machine owns the automation

This is the part that quietly matters. Once two devices hold the same schedule, both of them will happily fire it. Sync avoids that by making automation ownership explicit: publishing, repurpose pipelines and scheduled trackers run only on the device you assign, and every other machine stays out of the way. You can also park it at Paused on every device while you are setting things up.

What never leaves the machine it is on

The space carries your work, not your secrets. API keys, OAuth tokens for connected channels, license keys and other credentials stay in each machine's OS credential vault and never enter a sync batch. That means the second device does need its own channel connections and its own AI provider keys — a deliberate cost, so that a copied folder or a compromised bucket never contains a working set of your credentials.

Before vs After

Moving work between your machines	Before	Now
Getting a draft to the other device	Copy the text out, paste it back in	Already there
Assets and designs	Re-import on each machine	Metadata syncs, bytes on your policy
The content calendar	Whichever machine you built it on	Same schedule everywhere
Two machines publishing	Both fire the same post	One assigned automation owner
Editing the same piece twice	Whichever save happened last	Both kept, you choose
Where the data sits	One machine	Your devices, your folder, or your bucket

Who benefits most

If you work across a laptop and a desktop, this is the whole point — carry on where you left off, with the automation pinned to the machine that is actually always on.

If you are on Windows and macOS at once, object storage is the transport to use. It does not need both machines awake at the same time, and it does not care which platform wrote the batch.

If you switched to a local-first tool specifically to avoid a cloud account, this adds multi-device without giving that up. Encryption is mandatory, the passphrase never leaves your device, and the transport you choose is one you already control.

Try it

Open Settings → Sync on the machine that has your real workspace, create an encrypted space, and save the recovery key somewhere safe. Then open the same panel on your second machine and join it. The first sync will take a moment while the space fills up; after that, the workspace you have been building on one machine is simply the workspace you have on both.