Table of Contents

Overview

Sinapse is a general-purpose, plugin-based ESB (Enterprise Service Bus) and integration platform: it connects heterogeneous systems, devices, and applications over an internal message bus, with a graphical designer for wiring elaboration/storage/I/O plugins together instead of hand-coding integration glue.

Industrial process control, MES, and OT/IT integration are Sinapse's deepest, most mature domain — with a large catalog of ready-made industrial plugins and protocol support — but that's a strong track record, not an architectural limit: the same message-bus/plugin model applies to any heterogeneous-systems integration problem, industrial or not.

It predates and underlies MASES Group's entire JCOBridge product family — JCOBridge itself is built on Sinapse's DLR (Dynamic Language Runtime) plugin. See Related projects.

What Sinapse is for

  • General-purpose ESB-pattern integration: connecting heterogeneous systems, databases, applications, and services regardless of vendor or domain.
  • ERP integration and management.
  • Industrial process control, MES, and Industry 4.0/IoT evolution of existing plants — Sinapse's most mature and field-proven domain, with the deepest plugin catalog, but not the only one it's built for.

When not to use Sinapse

  • You need a lightweight, single-purpose integration (e.g. just bridging two specific systems with no broader plant/process control need): Sinapse is a full platform with a server, configurator, plugin ecosystem, and client run-time — that overhead may not be justified for a narrow, one-off integration.
  • You specifically need .NET↔JVM interoperability as a developer library, not a platform: that's JCOBridge and its family (JNet, JCOReflector, KNet, KEFCore, KNetOPC), not Sinapse directly — even though JCOBridge is historically built on Sinapse's DLR plugin.
  • You need a fully documented, actively maintained public reference before committing: verify current documentation/support status directly with MASES Group before a purchasing or architecture decision that depends on it.

See also Comparisons and alternatives and the FAQ.