Home / Features
What you actually getMonitoring for the engine you already run, fully hosted engines for the ones you would rather not, and a deployment path that treats channels like the production code they are.
Monitoring
Open-source engines fail in a small number of predictable ways: a heap that creeps up all week, a queue that stops draining at 3 a.m., a feed that goes quiet without ever throwing an error. We watch for those specifically, not just "is the process alive".
Hosted engines
A dedicated Open Integration Engine per customer, so one noisy tenant can never touch another. We handle the JVM, the message store, TLS certificates and version upgrades — the work that has nothing to do with your interfaces but eats the week anyway.
Channels as code
Channel configurations are versioned by content hash, diffed without leaving the browser, and promoted up a dev → staging → prod ladder. The ladder refuses to skip a rung, and what it promotes is what the lower environment is actually running — not what someone believes it is running.
Migration
Upload a channels.xml export and the analyzer walks every channel, transformer and code template, flagging the things that actually break on the move — Java 17 changes, XML parser calls, date utilities — with a verdict per channel. Your export is analyzed in memory and never stored.
Also included
Signed inside the signup flow, from the $199 monitoring plan up. Not an enterprise-only negotiation.
Hash-chained and enforced by database triggers, so a row cannot be quietly edited or deleted — not even by us.
Taken every night and restore-drilled — a backup nobody has restored is a hope, not a backup.
Share engine health with a partner or customer through a token URL — health signals only, never message content. Off by default.
Releases are Ed25519-signed and verifiable with stock openssl before you install them on your own server.
Resellers provision their own clients under their own branding, with per-client isolation and roll-up invoicing.
Fourteen-day trial, no card, no sales call. Point the agent at the engine you already run and see what it finds.