Sesam

Sesam takes a different route from the flow-builder tools in this category. Its Sesam Hub keeps a copy of the data from each connected system and synchronises it in both directions, so a change in one system reaches the others without a custom link between each pair.

The company's privacy policy names Sesam.io AS with organisation number 922 409 676, and the about page states that Sesam merged with its long-standing parent Bouvet on 1 January 2025.

The data hub approach

According to the homepage, Sesam synchronises and manages data between systems at a semantic level, which removes the need to modify any connected system. Each application keeps working on its own while the hub supplies consistent data.

That suits master data problems such as customer, product or employee records spread over many applications, and it fits less well where the job is triggering actions in real time.

Ownership change

From 1 January 2025 Sesam is part of Bouvet. The about page says customer relationships and service continue, but a prospective buyer should ask which Bouvet entity signs the contract and who runs product development.

Both Sesam.io AS and Bouvet are Norwegian, so the contracting question is about continuity rather than jurisdiction.

Limitations to Consider

The public site is brief: pricing, hosting region, connector counts and plans are not listed on the pages checked. The hub model copies data into a central store, which is a design choice with its own data protection implications, and it is not a drag-and-drop flow builder like n8n. Since the merger with Bouvet, the product sits inside a consultancy group rather than a stand-alone software company, so confirm the roadmap and support terms before a long commitment.

Who Should Use Sesam

Norwegian and Nordic organisations that need master data kept consistent across ERP, CRM and other systems and are comfortable with a hub-based design.