What is IntuCloud?

IntuCloud is a managed cloud platform for healthcare integration. You design HL7, FHIR, DICOM and related channels in a visual pipeline builder, test them in an isolated sandbox, and run them in production with monitoring, alerting and message reprocessing.

Underneath it is intu-dev, an open-source integration engine licensed under MPL-2.0. IntuCloud does not run a different, “enterprise” fork — the same engine binary executes your channels in the cloud sandbox, in staging, in production, and on your own laptop.

The open-core split

It helps to be precise about which capability belongs to which layer.

The engine (intu-dev, free and open source)

• All 27 connector types across sources and destinations
• The pipeline model: five source stages plus three per-destination hooks
• TypeScript transformer execution on a Node.js worker pool
• Retry policies, dead-letter queues, and Redis-based clustering
• OpenTelemetry and Prometheus instrumentation
• The intu CLI, including intu import mirth

The platform (IntuCloud, paid above the free tier)

• The visual designer with Monaco-based stage editing and in-browser test runs
• Managed environments — sandbox, staging, production — with promotion gates
• Gateway addresses, TLS termination and inbound allowlists
• Monitor, message browsing with format-aware viewers, and batch reprocess
• Alert rules, audit events, workspace roles, single sign-on
• PHI under a Business Associate Agreement on paid plans

What a channel actually is

A channel is a channel.yaml file plus a folder of TypeScript stage files. The designer canvas is a view of those files, not a separate representation stored somewhere else. That has two practical consequences:

1. A change to a transformer is a diff you can review, not a click somebody made in a GUI.
2. Exporting a project is a real exit path — the exported project runs on the open-source engine with no conversion step.

Where to go next

• Creating your account and organization — the object hierarchy you will work inside.
• Your first channel — a source, a stage, a destination, and a test run.
• Understanding plans and what is free — where the paid line falls.

Engine-level detail — CLI flags, storage backends, clustering topology — lives in the intu-dev docs.