Integration that grows with your landscape

Harmony is a MuleSoft Premium partner and has been building integrations for years for organisations whose processes run day and night.

Anypoint Platform is the more complete of our two platforms, built for landscapes where many systems have to connect, in the cloud or within your own infrastructure.

Start with MuleSoft
MuleSoft

What we do

What a MuleSoft implementation at Harmony involves

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

  • We design the API architecture

    Integrations become APIs in layers, so a source system is opened up once and can then be reused by every project that follows.

  • We connect your source systems

    We connect ERP, CRM, databases and SaaS through Anypoint's connectors, and build whatever is not there ourselves.

  • We set up governance and security

    Policies, access and versioning per API in API Manager, so reuse does not come at the expense of control.

  • We manage it after go-live

    CloudHub 2.0, Runtime Fabric or on-premises, with proactive monitoring and a service desk available 24/7.

Our approach

In 5 steps to MuleSoft 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.

Let us take a look

  1. Quick scan

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

  2. Proof of Concept

    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 API architecture: which layer exposes which system, where the runtimes run, how versions and policies are managed, and how 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 APIs 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 APIs 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 healthcare, telecom and manufacturing

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
Nurse updating data at a wall-mounted screen in a hospital corridor, while a colleague walks past.Two technicians in safety harnesses at the equipment on a transmission mast, overlooking a village.Operator reading data from a terminal at a production line.
  • Connect EHR, CRM and scheduling
  • Secure data exchange
  • Manage and monitor APIs
  • OSS/BSS integration
  • Real-time customer data
  • Faster new services
  • Connect ERP, MES and IoT
  • Automate the supply chain
  • Modernise legacy
IT for healthcare

Healthcare, care and cure

Healthcare runs on systems that never learned to understand each other, while the standards for data exchange keep getting stricter. This is what an integration layer solves there.

  • Fewer repeated questions, a complete picture sooner

    Data from the electronic client or patient record, laboratory systems and pharmacy comes together, so nobody has to piece the story together again.

  • Demonstrable compliance with exchange standards

    Messaging in HL7 and FHIR, with logging to NEN 7513, so you can show afterwards what was exchanged.

  • Fewer misunderstandings about appointments

    Rosters, availability and appointments stay in sync between the source system and the channels where clients and staff look.

  • Claims without manual work

    Registrations flow through to claims and billing, and rejections come back to the place where they can be resolved.

Telecom and fibre

In a fibre rollout, a single order passes through sales, planning, the contractor and billing, each with its own system. This is what an integration layer solves there.

  • Shorter lead time from order to active line

    The whole chain from order to delivery runs as one flow, with every handover automated and traceable.

  • Less detective work for customer service

    CRM, billing and self-service show the same status, so customer service does not have to guess which system is right.

  • The technician has what he needs

    Data on build, capacity and faults reaches planning and the technician without an export in between.

  • Peak volumes without manual work

    A migration or a rollout wave of thousands of connections runs through the chain without anyone dividing up batches by hand.

Industry and high-tech manufacturing

On the shop floor, machines and systems from different generations sit side by side, while the office expects real-time figures. This is what an integration layer solves there.

  • Less double entry between ERP and the shop floor

    Production orders, confirmations and time registration flow between ERP and the shop-floor systems without double entry.

  • From order to planning without retyping

    An order from sales or a customer portal reaches planning and purchasing without retyping.

  • A shortage shows up before the line stops

    Stock, purchasing and production planning look at the same figures, so a shortage shows up before the line stops.

  • A recall without a search

    Measurement and inspection data stay attached to the batch, so an audit or a recall does not turn into a search.

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

Enter it once, up to date everywhere

Take the first step

Comparison

MuleSoft or Frends: which one suits you?

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

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 Frends
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