Skip to main content
Bethemesh
GuideConcepts and technologies

First synchronization

Learn how to synchronize your pipelines across multiple devices while keeping full control over your data.

Published 27 July 2026Updated 6 August 2026Reading : 2 minBy Bethemesh Team
Beginner
Show contents
  1. Synchronization is entirely optional
  2. What is synchronized?
  3. Why synchronize?
  4. A continuous working environment
  5. Still Local First
  6. Best practices
  7. What happens if two versions exist?
  8. In summary

After creating several pipelines, a common question naturally arises: how can you access them from another computer?

This is exactly what synchronization is designed for.

Synchronization allows you to retrieve your pipelines across multiple devices without rebuilding them manually. You can start working on one computer, continue later on another, and keep the same organization throughout your projects.

Synchronization is entirely optional

Using synchronization is not required.

You can use Bethemesh exclusively in Local First mode without creating an account or synchronizing anything.

Synchronization is simply available for users who want their workflows to follow them across multiple devices.

This means you are always free to choose between a fully local experience and a synchronized one.

What is synchronized?

Synchronization mainly concerns your pipelines.

It stores information such as:

  • pipeline names;
  • workflow structure;
  • selected modules;
  • execution order;
  • module settings.

Your working files, however, remain intended for local processing whenever possible.

This distinction is essential to preserve Bethemesh’s Local First philosophy.

Why synchronize?

Synchronization quickly becomes useful in many situations.

For example:

  • you work both at home and at the office;
  • you regularly switch between different computers;
  • you reinstall your operating system;
  • you simply want your workflow library available everywhere.

Instead of rebuilding your workflows, synchronization restores them automatically.

A continuous working environment

Synchronization is about more than backup.

Its real purpose is to provide a consistent working environment across all your devices.

You recover the same pipeline library, the same organization, and the same workflows wherever you work.

Still Local First

Enabling synchronization does not change Bethemesh’s philosophy.

Whenever processing can happen directly inside your browser, it continues to do so.

Synchronization simply complements the Local First approach by making your workflows available on multiple devices.

Best practices

To get the most from synchronization:

  • use descriptive pipeline names;
  • remove obsolete workflows;
  • avoid duplicate pipelines;
  • synchronize regularly if you work on multiple computers.

A well-organized library is much easier to manage across every device.

What happens if two versions exist?

Sometimes the same pipeline may be modified on different devices before synchronization occurs.

When this happens, Bethemesh detects the conflict and asks you which version should be kept.

The guide Resolving synchronization conflicts explains exactly how this process works.

In summary

Synchronization extends the Workspace by allowing your pipelines to travel with you.

It provides flexibility across multiple devices while remaining fully compatible with Bethemesh’s Local First philosophy and your control over your data.

GuideConcepts and technologiesIntermediate

Resolve a synchronization conflict

Understand why synchronization conflicts occur and learn how to resolve them without losing your work.

27 July 20262 minRead
GuideConcepts and technologiesBeginner

Create your first pipeline

Learn how to build your first pipeline in Bethemesh to automate repetitive tasks and reuse your workflows with just a few clicks.

27 July 20263 minRead
GuideConcepts and technologiesBeginner

Reuse a pipeline

Learn how to reuse your Bethemesh pipelines efficiently to save time and standardize your workflows.

27 July 20262 minRead

Was this article useful?