n8n

Not necessarily. The community edition carries no licence fee and no cap on how many workflows you run, and it is enough for most organisations. The enterprise edition adds single sign-on, role-based access control, audit logs, log streaming and version control over your workflows, which is usually what regulated environments need.

No. n8n runs as an automation layer in its own right, with or without an ITSM platform underneath it. It connects systems that were never designed to talk to each other.

On a machine you provide, so your data stays in your own environment. We build three fully separate environments for development, testing and production, each with its own database, job queue and vector store, behind encrypted access, plus a private package registry so what runs in production is versioned rather than whatever was last edited.

One Linux virtual machine with a container runtime and administrative access, the DNS records and certificates for its addresses, and someone able to confirm configuration decisions. We set out the exact specification at the technical deployment meeting and check the environment before anything is installed.

Yes. A deployment includes twenty hours of consulting in the first year, which is there to get real work running rather than leaving you with an empty platform.

Through our connector, which lets Ivanti call an n8n workflow, pass it the record, wait for the answer and act on the result. Our n8n nodes themselves are free and open source, published by us and verified by n8n; what is licensed is the Ivanti-side piece.

There are ready-made workflow sets you can switch on: triaging incoming incidents with a suggested resolution, category and priority; grouping related incidents into a proposed problem record; and removing personal data from records for data-protection purposes. Anything beyond those, you or we can build.