JiCoRedact. Approve. Document.

Log inTry for free

Blog

What we write about JiCo — decisions, limits, background.

Lead article · 2026-09-19 · 6 min read

The order decides

Almost every tool on the market filters after the model has read. That is the difference this is about.

Read →

NL-4711 · Payroll accessExample, made up
Reporter
Erika Mustermann«Person 1»
Assignee
Max Mustermann«Person 2»

Please grant access for max.mustermann@example.com«E-Mail 1», the IBAN is in the attachment: DE00 0000 0000 0000 0000 00«IBAN 1».

Reading path:
Route map of all articlesRedactApproveDocumentBackgroundJiCo1. The door Atlassian closed12. The Swiss question23. Why we do not build this ourselves34. Local first, cloud as an option45. The licence that never phones home56. One package per company67. A certificate only for itself78. The order decides89. Reference instead of reproduction910. The scanned document in the attachment1011. The question that is never asked1112. What we do not promise1213. Similar tickets, without knowing the answers1314. The one emergency exit1415. The night run and the morning after1516. No second assistant1617. How the model knows what a defect is1718. The chain that reports every gap1819. Why the works council is asked first1920. What we deliberately do not measure2021. The canary in the code21

Background

Why JiCo is built this way

  1. 1The door Atlassian closedSince 30 March 2026, Jira Data Center can no longer be bought new. For everyone already running it, the question changes abruptly — from "whether" to "how much longer".2026-09-19 · 6 min read
  2. 2The Swiss question"We are not in Switzerland at all, so why data residency?" Because the same mechanism serves more than a single law.2026-09-19 · 5 min read
  3. 3Why we do not build this ourselvesNot every part of JiCo is built in house. Only the part that no vetted tool on the market actually covers.2026-09-19 · 6 min read
  4. 4Local first, cloud as an optionThe model is interchangeable. What JiCo starts with when nobody does anything is not interchangeable by accident.2026-09-19 · 5 min read
  5. 5The licence that never phones homeAlmost every commercial piece of software checks its licence online — a quiet control channel over which everything else could travel too. JiCo talks to exactly one known recipient, only on your click, and never transfers Jira/Confluence content; every licence is checked exclusively offline.2026-09-19 · 6 min read
  6. 6One package per companyMost SaaS products bundle all customers into one shared system — an advantage in operations, a risk in an incident. JiCo deliberately takes the more cumbersome route.2026-09-20 · 5 min read
  7. 7A certificate only for itselfThe browser warns "your connection is not private" — for a program that never leaves your own machine. That very warning is the reason JiCo can show it in the first place.2026-09-20 · 5 min read

Redact

What did the AI model see?

  1. 8The order decidesAlmost every tool on the market filters after the model has read. That is the difference this is about.2026-09-19 · 6 min read
  2. 9Reference instead of reproductionA pseudonym mapping that stores everything is just a second plain-text store with a politer name.2026-09-19 · 6 min read
  3. 10The scanned document in the attachmentMost PII filters check text. The genuinely sensitive data, though, often sits in a scanned PDF or a photograph that nobody recognises as text — until somebody actually reads it.2026-09-20 · 5 min read
  4. 11The question that is never asked"Which Catholics are in the system?" A question that sounds harmless — and precisely for that reason the most dangerous kind of request an AI assistant can receive.2026-09-19 · 5 min read
  5. 12What we do not promise"Does the gate really detect everything?" — No. And we say so here, in the running text, not in the small print.2026-09-19 · 6 min read
  6. 13Similar tickets, without knowing the answers"Have we had this before?" is one of the most common questions in everyday support work — and one of the questions for which many vendors upload the entire ticket store to somebody else's cloud.2026-09-20 · 5 min read

Approve

What does the AI want to do?

  1. 14The one emergency exitEvery path from the AI client to Jira runs through JiCo — except one, and that one is marked, not hidden.2026-09-19 · 6 min read
  2. 15The night run and the morning afterAn assignment that checks 400 tickets overnight does not present 400 lines in the morning — but a handful of groups that genuinely need a decision.2026-09-19 · 5 min read
  3. 16No second assistantA chatbot alongside JiCo would not be an extension but a duplication — and precisely in the place where duplication does the most harm.2026-09-19 · 5 min read
  4. 17How the model knows what a defect isThe same word often means two completely different things in two Jira instances. A language model does not know that difference by itself — unless somebody tells it.2026-09-20 · 5 min read

Document

Who approved what?

  1. 18The chain that reports every gapA record that could be shortened unnoticed is worthless as evidence — no matter how complete it looks at the moment.2026-09-19 · 6 min read
  2. 19Why the works council is asked firstA tool that records who approved what and when quickly looks like an instrument of surveillance from the wrong perspective. That is exactly why this perspective is not ignored, but heard first.2026-09-19 · 5 min read
  3. 20What we deliberately do not measureA dashboard that only shows how much faster everything has become sometimes measures decay in disguise — and celebrates it as progress.2026-09-19 · 5 min read
  4. 21The canary in the codeEvery piece of software claims that it sends nothing out without authorisation. The interesting question is how one actually proves that — rather than merely promising it.2026-09-19 · 5 min read