| InTouch AI | Jenkins |
|---|
| Type | Full-spectrum workflow automation — individuals to enterprise | Open-source CI/CD automation server |
| Architecture | Single JAR (JVM/Kotlin/Micronaut) | Java server + master-agent architecture |
| Primary Focus | Workflow scheduling, automation, AI-native, 35 tools | CI/CD pipeline automation |
| Installation | Seconds — single JAR | Minutes to hours (WAR + plugins) |
| Licensing | Free Personal; licensed Team, Dept, Enterprise | Open-source (MIT); CloudBees from $3,500/yr |
Feature-by-feature tables are useful, but they bury the actual difference. These are capabilities of the platform itself rather than of any one tool.
| InTouch AI | Jenkins |
|---|
| Determinism is a choice, per workflow | Run a workflow fully deterministically with no model in the execution path, fully AI with the assistant reasoning every run, or have the assistant author it once and then run that artifact forever at zero AI cost per run. The same engine does all three. | Groovy pipelines or freestyle jobs, deterministic only. |
| Schema Designer & generated forms | Describe a tool's inputs as a schema and InTouch renders its entire configuration form — including for tools you wrote yourself. No UI code is written per tool, ever. | Parameterized builds give a basic form; plugin UIs are hand-written Jelly or Groovy. |
IToolConnector plugins | One interface, one JAR, hot-loaded without restarting the server. Your tool arrives with credential handling, scheduling, retries, audit and alerting already attached. | Plugins — a large, mature ecosystem, but a heavier contract and usually a restart. |
| A vault the AI cannot read | Credentials are AES-256 encrypted and referenced by name. The assistant can use a credential to do work without the secret ever entering its context. | The Credentials plugin. |
| Audit trail + execution log the AI can read | Every action attributed and timestamped; every run's inputs, outputs and result code retained — and both are readable by the assistant, so “why did this fail” is a question you can simply ask. | Build logs. Auditing requires the Audit Trail plugin. |
| MCP in both directions | A 271-tool MCP server lets Claude Code and any other MCP client drive InTouch, and InTouch is itself an MCP client. The two amplify each other. | None. |
| Works in any language | The assistant operates in whatever language you type. A global team runs InTouch in their own languages with no localization project. | No assistant. |
| Capability grants (Enterprise) | Grant or revoke individual tools, AI providers, skills — and the assistant itself — per user or per group. Deny-by-default, enforced where a user reaches for the capability: listing tools, adding one to a workflow, running a skill, opening the assistant. (Department governs objects through roles; capability grants are Enterprise.) | Matrix authorization over Jenkins objects; no AI-provider or tool grants. |
| AI provider redundancy (Ent) | Gateway routes with failover across providers, plus cheapest, fastest and round-robin selection policies. One provider going down is not an outage. | None at the AI layer. |
| AI cost reporting (Ent) | Token spend and estimated cost broken out by provider, model and project, with retention control. You can answer “what is AI costing us, and where”. | None. |
| Capability | InTouch AI (All Editions) | Jenkins |
|---|
| Workflow Creation | Web UI (no code) + IML Workflows (workflows-as-code) | Jenkinsfile (Groovy) or Freestyle jobs |
| Tools | 35 in the free download: SQL (11 databases), SSH, FTP/SFTP, rsync, HTTP, AWS (entire CLI v2), Google Workspace, OS/spawn, messaging, skills and the AI family (Essbase and TM1 bring it to 37 once licensed) — Excel, PDF, Git, LDAP, MongoDB, Cassandra and Docker from the Hub | Via 1,800+ community plugins (quality varies) |
| Enterprise Systems | Essbase and TM1 available under licence | Not available |
| Plugin Ecosystem | 6 signed IToolConnector JARs bundled, plus 40 curated connectors on the Hub | 1,800+ community plugins — conflicts, vulnerabilities common |
| Workflows-as-Code | IML with ordered task chains | Jenkinsfile (Groovy — not YAML) |
| Capability | InTouch AI | Jenkins |
|---|
| Schedule Types | 7 native: Day, Week, Weekday, Weekend, Month/Specific, Month/Relative, Custom | Cron syntax with hash-based balancing |
| Blackout Dates | Built-in | Not built-in |
| File Triggers | Built-in file monitoring | Filesystem trigger plugin (limited) |
| Monitors | Built-in watch-and-act primitive (schedule + check + AI or condition arms + actions) | Not available |
| SCM Triggers | Not applicable | Core feature — Git, GitHub, GitLab webhooks |
| Alert System | Dedicated alerts, multi-channel | Not built-in (plugins) |
| Choose InTouch AI When You Need | Choose Jenkins When You Need |
|---|
| Workflow automation with 35 built-in tools, no scripting | CI/CD pipeline automation with deep SCM integration |
| Agentic AI assistant reaching every InTouch capability, with 8 channels | Build automation (Maven, Gradle, npm, Docker) |
| 7 native schedule types with blackout dates | 1,800+ community plugins for various integrations |
| Essbase and TM1 available under licence; MongoDB and Cassandra from the Hub | Master-agent distributed builds |
| AWS tool wrapping entire AWS CLI v2 | GitHub/GitLab webhook integration |
| SQL across 11 databases, FTP, SSH built-in | Jenkinsfile (Groovy) for complex build/deploy |
| InTouch skills + IML Workflows | DevOps teams invested in Jenkins ecosystem |
| Free Personal edition with all tools | CloudBees for enterprise support |