Proven integration partner, now with Frends as well

Harmony has been building integrations for years, as a MuleSoft Premium partner for organisations with complex landscapes.

The Finnish platform Frends, which focuses on European sovereignty, complements that for anyone who wants to start faster, with a smaller team, or with a runtime that runs entirely within their own network.

Start with Frends
Frends

What we do

What a Frends implementation at Harmony involves

A Frends implementation at Harmony runs from architecture and build to management after go-live, for clients in the Netherlands, Belgium and Luxembourg. That can be a complete implementation project, or a Frends consultant who joins your team on an environment that is already running.

  • We design processes and architecture

    We set up processes, data flows and APIs visually in BPMN 2.0: an open notation, not a proprietary dialect.

  • We connect your source systems

    We connect source systems through 300+ ready-made connectors, with a built-in AI layer for routing and processing.

  • We set up security and governance

    Access management and policies, within a platform that is ISO 27001 certified and NIS2 and GDPR assessed.

  • We manage it after go-live

    Cloud, on-premises or hybrid, with 24/7 visibility of what is happening and error handling that keeps watch.

Our approach

In 5 steps to Frends in production

After the first two steps you know whether this is the right platform, with an integration from your own landscape already running. We usually take these steps in this order, and they have proven themselves in practice.

  1. Quick scan

    We map your application landscape, the existing integrations and the processes around them, and decide together whether Frends is the right choice. If MuleSoft is the better fit, we tell you at this stage.

  2. Proof of Concept

    With a trial licence, we build a real integration from your own landscape in a secure test environment. Your own data and your own systems on both ends, so the decision rests on something tangible.

  3. Architecture

    We define the initial architecture: where the agents run, how shielded zones stay separated, how data is routed and stored, and how sovereignty and compliance requirements are built into the design rather than added afterwards.

  4. Implementation

    Environments, user management and the CI/CD pipeline are set up, then the processes are developed and tested in an Agile way. Each integration only goes live after your approval and is then handed over to support.

  5. Maintenance and management

    Proactive monitoring of processes and platform by a service desk available 24/7. In the event of an incident, we analyse it, liaise with third parties where needed and roll out the fix. Through Service Level Management, we propose improvements.

Where we use it

Integration in energy, manufacturing and logistics

Harmony has been delivering integrations at the largest organisations in the Benelux for years. Below is what that achieves in each sector.

Another sector? No problem. We have broad experience.

Talk to an expert
Technician with a tablet at a transformer in a medium-voltage substation.Operator at a control panel next to a production line.Planner with a handheld scanner in a distribution centre, talking to a colleague.
  • Automate market messages
  • Connect SAP and OT
  • Fast process flows
  • Connect ERP, MES and WMS
  • Integrate EDI easily
  • Automate production flows
  • Connect the transport chain
  • EDI with partners
  • Real-time order statuses

Energy and utilities

The rules are being rewritten right now, on systems that have been in place for decades. This is what an integration layer solves there.

  • Accurate invoices, less correction work

    Quarter-hourly consumption flows without gaps to billing, the customer portal and the market parties.

  • Out on time, without rework

    Messages to grid operators and suppliers go out in the right format and within the deadline, via EDSN in the Netherlands and Atrias in Belgium.

  • The office sees operations, and operations notice nothing

    SCADA and metering systems feed ERP and CRM, without affecting the availability of operations.

  • Keeps running when the connection drops

    The runtime runs within Europe, on-premises where required, and keeps running when the connection to the outside drops.

Manufacturing

A factory runs on systems chosen layer by layer: ERP in the office, MES and WMS on the shop floor. This is what an integration layer solves there.

  • One way of working, even after an acquisition

    Growth and acquisitions rarely leave you with a single ERP. A process now runs across them without manual work in between.

  • Less retyping between shop floor and office

    MES, WMS and SCADA deliver their data to ERP, via OPC UA where the machines speak it, and orders travel the same way back to the line.

  • From fault to ordered part without intervention

    A deviation automatically becomes a work order and an ordered part, right through to the supplier's confirmation.

  • An audit that does not turn into a search

    A rejected batch can be traced back to supplier, machine and moment, without three systems side by side.

Logistics and supply chain partners

Supply chain partners each bring their own system and their own format. This is what an integration layer solves there.

  • Every partner in their own format, without extra work

    Orders, packing slips and invoices come in as EDIFACT, GS1 or through an API, and all land in the same place.

  • Fewer lost sales thanks to one view of stock

    Sales channels, WMS and ERP see the same thing, even when something changes in three places at once.

  • Fewer calls asking where the shipment is

    Status updates from carriers flow through to the order, customer service and the customer, without anyone opening a portal.

  • See it before it stalls

    A faltering message flow is visible before a lorry or a dock is left waiting.

Imagine: every system works with the same up-to-date data

Enter it once, up to date everywhere

Take the first step

Comparison

Frends or MuleSoft: which one suits you?

Frends and MuleSoft are both integration platforms, but they are built for different situations. Frends suits teams that want to start quickly and keep things compact. MuleSoft suits organisations that set up integration broadly and in a standardised way.

Harmony delivers both, so the choice does not have to be made in advance. We look at your landscape first and then tell you which platform fits. Below, you see them side by side.

Read about MuleSoft
Frends iPaaS and MuleSoft Anypoint Platform, compared on ten criteria.
Comparison criteriaFrends iPaaSMuleSoft Anypoint Platform
Architecture and infrastructureHybrid network of lightweight .NET 8 agents, with a control panel in the cloud or on-premises.API-led network of JVM runtimes: CloudHub 2.0, Runtime Fabric or on-premises.
Air-gapped capabilityDesigned for isolation. Agents and control panel work autonomously, with offline distribution of NuGet artefacts.Possible via Anypoint PCE, with a heavy Kubernetes cluster and complex on-premises maintenance.
Total cost of ownershipVolume-based, on monthly executions. Unlimited agents and processes, no extra cost for microservices.Capacity-based, on vCores or API calls. Higher entry cost and modular add-ons for MQ, monitoring and connectors.
Profile and development languagesC#, .NET and BPMN 2.0. Gentle learning curve for regular back-end and full-stack developers.Mule XML, DataWeave and Java. Steep learning curve and certified specialists.
Development speed and reusabilityVisual canvas with C# snippets. Custom connectors become ordinary NuGet packages.AI-assisted Anypoint Code Builder. Custom connectors require the Java or Mule SDK.
Data sovereignty and legal frameworkEuropean entity, GDPR-native. Not subject to the US CLOUD Act.Salesforce, a US entity. Subject to the US CLOUD Act.
Error handling and observabilityTraceability per BPMN step, with try-catch and automatic retry.Anypoint Visualizer and Titanium monitoring, with proprietary on-error scopes.
Scalability and peak loadHorizontal agent groups behind a load balancer, asynchronous via Azure Service Bus or RabbitMQ.Multi-AZ replicas in CloudHub 2.0, with autoscaling and Anypoint MQ.
Vendor lock-inLimited. The logic is written in standard C# and can be moved to any .NET environment.Considerable. DataWeave logic needs manual rebuilding or conversion tools when you migrate.
AI and agentic innovationEarly adoption of the open Model Context Protocol, including local, isolated LLMs.Strong integration through Salesforce Agentforce and the MuleSoft AI Chain framework.

Talk to an expert

A short conversation is usually enough to tell how we can best get you started.

Fields marked with an asterisk are required.

Step 1 of 2
Step 2 of 2
When is the best time to reach you?

Feel free to pick several. If nothing suits you, leave it empty and we will email a suggestion.

Our insights and stories