Open Source
Run intu-dev on your infrastructure. Keep our engineers on call.
Some organizations will never move PHI off-premise, and that is a decision worth respecting rather than working around. Enterprise support subscriptions put the team that builds the engine behind your self-hosted deployment, under SLA.
What's included
What a subscription covers.
Named technical contact
A specific engineer who knows your deployment, not a queue. They keep context between tickets so you are not re-explaining your topology every time.
Response-time SLAs
Contracted response times by severity, so an incident on a clinical feed has a defined path rather than a best-effort one.
Upgrade planning and assisted upgrades
Release notes read for your configuration, a planned upgrade path, and an engineer on the call when you cut over.
Priority fixes and roadmap escalation
Issues from support subscribers are triaged first and can be escalated directly into the engine roadmap.
Mirth migration assistance
Help importing and validating channel XML at volume, including the transformer logic that does not translate mechanically.
Architecture and deployment reviews
Clustering topology, high availability, storage backend choice, observability wiring — reviewed against how the engine actually behaves under load.
How it works
Three steps, no procurement theatre.
- 1
Tell us about the deployment
Channel count, message volume, the systems on either end, and where the engine runs today. Ten minutes on a call is usually enough.
- 2
We scope the subscription
Severity definitions, response times, and the number of environments covered are agreed against your actual footprint.
- 3
Annual contract, then onboarding
Support subscriptions are contracted annually through sales. Onboarding starts with an architecture review so your contact is not learning your setup during an incident.
Support subscriptions are priced against your deployment rather than a public tier, so there is no number on this page. Tell us what you are running and we will come back with a scope and a price.
Position
This does not close the open source.
A support subscription works alongside the community, not instead of it. intu-dev stays MPL-2.0. Clustering stays in the open source rather than moving behind a license. Issues filed on GitHub by people who pay us nothing still get read and still get fixed.
What a subscription buys is a contractual relationship: a named person, a response time, and somebody accountable at 3am. If you do not need that, run the engine for free and we would still rather you ran it than something else.
Alternatives
Or let us run it entirely.
Self-hosted with support
You operate the engine inside your own compliance boundary. We are accountable for the engine and for helping you run it well. Data never reaches us.
IntuCloud managed platform
We operate the engine, the environments and the gateways. You get the designer, monitoring and PHI under BAA, on published plans.
Keep the data in your building. Keep our engineers on call.
Support subscriptions are contracted annually. Tell us about your deployment and we will scope one.