Skip to content
IntuCloud is built on the open-source intu-dev engine — star it on GitHub

Resources

Changelog

What has actually shipped, most recent first. Capabilities that are engine-supported but not yet exposed in the cloud beta are labelled as such rather than counted as launched.

  1. Connectors Platform

    MLLP over TLS listeners in the cloud beta

    HL7 v2 listeners are now available in the IntuCloud beta, terminating TLS at the gateway.

    • TCP source connectors can run in MLLP mode on a cloud gateway address under *.gw.intucloud.ai.
    • TLS 1.2 or higher is terminated at the gateway; plain MLLP over an untrusted network is not offered.
    • ACK and NACK behaviour matches the engine, including retryable NACKs under backpressure.
    • Production MLLP listeners require an inbound allowlist, configured alongside the listener.
  2. Designer

    Capture test data directly from sandbox runs

    The message that broke your mapping is now one click away from becoming a fixture.

    • Capture the payload at any stage of a sandbox run and save it into the project test-data library.
    • Captured fixtures are reusable in the in-browser stage runner.
    • Fixtures travel with a project export, so they survive a move to self-hosted intu-dev.
    • Free-plan workspaces remain restricted to synthetic data.
  3. Platform

    Alert rule templates and muting

    Alerting picked up the two things operators kept asking for.

    • Notification templates control what an alert actually says, so the channel, environment and condition lead the message.
    • Rules can be muted for a window — useful during a planned downstream outage, without deleting and forgetting to recreate the rule.
    • Acknowledgements record who took the alert and when.
    • Alert history shows what fired, how long it stayed open, and how it was resolved.
  4. Platform Connectors

    Dedicated gateway IP add-on

    Counterparties that need a stable IP to allowlist can now be given one.

    • Dedicated ingress and egress address sets are available as a $40/mo add-on on Team.
    • Dedicated addresses are included on Enterprise.
    • Shared gateway pools remain the default for workspaces that do not need a fixed address.
    • Address sets are assigned per environment, so staging and production can be allowlisted separately.
  5. Platform

    Batch message reprocessing

    Replaying a whole outage window no longer means clicking one message at a time.

    • Select a range in the message browser and reprocess it in bulk.
    • Available on every plan, including Free.
    • Each reprocess run is recorded in the event stream with the user who initiated it.
    • Single-message reprocess remains available from the message detail view.
  6. Platform

    Deployment gates — preflight, soak and approval

    Promotions now run through configurable gates instead of going straight out.

    • Connector preflight verifies every connector against the target environment before the promotion proceeds — DNS, TLS handshake and credentials.
    • Soak runs the channel in the target environment for a configured window while error rates are watched.
    • Approval requires a named approver to sign off in-app; the approval and approver land in the audit event stream.
    • Undeploy now drains in-flight messages rather than cutting them off.
  7. Connectors

    FHIR R4B subscriptions in the engine

    The engine gained a FHIR subscription source using the R4B subscription model.

    • Receives notifications from a FHIR server you have subscribed to, rather than polling it.
    • Lower latency and less load on the source system than a scheduled search.
    • Available today on self-hosted intu-dev; cloud exposure is still pending, so it is listed as engine-supported in the connector catalog.
    • The FHIR R4 server listener and FHIR destination remain available in the cloud beta.
  8. Designer Platform

    Mirth Connect import wizard

    Mirth Connect channel XML can be imported into an editable pipeline from inside the app.

    • Upload one channel or a group export; each channel arrives as a visual pipeline on the canvas.
    • Source connectors, destinations, filters and transformers map onto the intu-dev pipeline model.
    • Rhino ES5 transformer bodies come across for you to modernize into TypeScript.
    • The engine CLI equivalent, intu import mirth, is the better route for scripted bulk migration.

Looking further ahead? The roadmap covers what is next.

Start building today.

Free plan, no credit card — design and test unlimited channels.

Get started free View pricing