JiCoRedact. Approve. Document.
How JiCo compares
No product we have checked combines redaction before the AI model, approval for every write action and Jira Data Center. Here is how we back that up — criterion by criterion, with sources.
Criterion by criterion
No product combines what JiCo does — a local gateway, redaction before the AI model, approval for every write action, for Jira Data Center. The following five are the closest points of comparison on the market, not direct alternatives. The baseline is what JiCo does — for Atlassian Rovo a verified, detailed analysis exists; for Strac, Portkey, Kong and IBM watsonx.governance only what is publicly documented, because they aren't Jira competitors in the strict sense.
| Criterion | JiCo | Atlassian Rovo | Strac | Portkey | Kong | IBM watsonx.governance |
|---|---|---|---|---|---|---|
| Redaction before the AI model | Yes — personal data becomes placeholders before the AI model sees it. | not documented. | Yes, per the vendor — personal, health and card data, credentials, also in images and PDFs (description). | only in the Enterprise tier, whose price is not public. | not documented. | not documented for this use case — a general governance platform, not built for a chat assistant inside Jira. |
| Approval before every write action | Yes, for every action — unknown tools count as write actions (fail-closed). | partly — in chat, not in automation rules (Rovo MCP Server). | partly — high-risk actions such as writes or status changes can be blocked or routed for approval by policy (description). | not documented. | not documented. | governance workflows exist, but not built for individual write actions as described here. |
| Re-checked state before execution | Yes — a ticket updated or commented on since the analysis is not executed. | not documented. | not documented. | not researched — not part of the existing competitive analysis. | not researched — not part of the existing competitive analysis. | not researched — not part of the existing competitive analysis. |
| Record of what reached the AI model | Outbound log with a hash chain and placeholders, append-only. | partly — MCP calls are logged as an audit event, the content is not (settings). | Yes, per the vendor — per call: time, user, tool, data classes detected and redactions (description). | logging is the product's core purpose (100,000 logs in the cited tier), but not Jira-specific and without a redaction tally. | not documented in detail. | governance reporting is the product's core purpose, but not Jira-specific. |
| Jira Data Center | Yes. | No — only via the free Rovo Connector, which copies the data into the Rovo cloud; Rovo itself is paid (Marketplace listing). | not documented — setup only mentions an "Atlassian Cloud tenant" (Atlassian page). | no Jira connection. | no Jira connection. | no Jira connection. |
| Deployment | local, offline licence, no multi-tenant SaaS. | cloud/SaaS. | vendor-run proxy endpoint, set up via OAuth; self-hosting not documented. | cloud/SaaS. | the cited "Plus" tier is a cloud tier. | SaaS. |
| Multi-user, SSO | No — v1 is single-seat. | Yes (settings). | not researched. | not researched. | not researched. | not researched. |
| Certification | None. | Yes — SOC 2, ISO 27001 (settings). | per the vendor SOC 2, HIPAA, PCI-DSS, ISO/IEC 42001 (description). | not researched. | not researched. | not researched. |
| Price | €490 (CHF 460.60) per month and installation, introductory €295 (CHF 277.30) for orders by 31 Dec 2026; up to 200 installations — see Pricing. | 20 USD per developer per month, 2,000 credits included, 0.01 USD per additional credit (pricing page). | on request, by scope (pricing page). | 49 USD/month for 100,000 logs (pricing page). | 100 USD/month per LLM AI model, plus 25–500 USD/month for the control plane (pricing page). | 42,000 USD/year for 25 users and 5 use cases (pricing page). |