← All help topics

Linked instances and project transfer

How to link several copies of the service (e.g. by region) and transfer a project to another instance. Admin section.

1Why it exists

The service can run as several linked copies — e.g. a separate “regional instance” for your jurisdiction or network. Linked instances can:

  • 🔗 check connectivity (a status indicator);
  • 📦 transfer a whole project from one instance to another;
  • 🔄 keep the transferred copy up to date.

All model/token/worker work stays on the origin instance — only a managed copy goes to the other one.

2Link two instances

In «Administration → Instances»:

  1. 🏷️ in the “This instance” block set the name, your own URL and region (optionally mark “Regional instance”);
  2. ➕ add a linked instance: its name, address and a shared link secret (you can “Generate” one);
  3. 🔁 add the same secret on the second copy, pointing it at the first one’s address;
  4. ✅ click “Check” — the indicator turns green once the link works.

🔒 The link secret is encrypted and never exposed; inter-instance requests are signed and replay-protected.

3Transfer a project to an instance

In «Administration → Projects» open a project and use the “Transfer to instance” block: pick a recipient and click “Transfer”. A copy marked “remote” appears on that instance.

What goes: project settings, sources, channels, plan, templates and posts. What does NOT: bot tokens and model keys — they stay on the origin.

4How the mirror copy works

On the second instance the project mirror:

  • ✍️ lets you edit settings (profile, models, bots, sources, channels) — changes apply in the main region (master);
  • ✍️ lets you work with posts and the queue: view, approve, edit, regenerate, publish;
  • 🔄 pulls fresh data from the master (automatically when the plan opens and via “Refresh”).

Generation and publishing run in the main region (models and tokens live there) and the result flows back to the mirror.

5Full migration (master handoff)

Beyond the regular transfer there is “Full migration (master)”: the project moves ENTIRELY, including bot tokens, model keys and the owner (all encrypted with the link secret). After migration:

  • 🛰️ the remote instance becomes a full master — it runs workers, models and publishing;
  • 🔁 this copy turns into a mirror: settings/bots/sources and posts are edited here and changes go to the master;
  • ⏹️ no background work for the project happens here anymore.

⚠️ It's a one-click action that changes where the project “lives” — use deliberately.

6Project members

The project card («Administration → Projects») has a “Project members” block: add a user by email or id with a role — 🖊️ editor (can change content) or 👁️ viewer (read-only). You can change a member's role or remove them. The owner is set at project creation. For a remote (slave) copy, members are managed on the origin instance.

Didn't find an answer? Write to us — we'll help.

Contact support