Hosted by us.
We run and update it. We can host in the region your organisation needs.
Nissy for organisations builds a decision ledger from your team's AI sessions. When someone asks why it's built this way, the answer is there, even after the people who made the call have moved on.
Plan review flagged an uncapped retry loop on 9 Sep 1.
You capped it at five that afternoon, as the ledger shows 2 3.
Sessions
Decision ledger
People move on. Their decisions stay, with the sessions behind them, so whoever picks up the repository next can still ask why.
You can't watch every repository, and not all of them carry the same risk. This shows you where concerns keep landing and what kind they are, so you know which one needs your attention this week.
| Repository | 3 Augthis week | Total |
|---|---|---|
| billing-svcmostly testing | 11 | |
| shop-apimostly scope | 11 | |
| inframostly security | 4 | |
| web-appmostly scope | 2 |
Answers cite the sessions and decisions behind them.
Every decision, who made it, and which went beyond the plan.
By repository and category, week by week.
What admins and members see, what gets stored, and project rules for what Nissy looks out for.
For regulated teams, the record of what was decided and by whom, kept as your policy requires.
Title, summary and milestones of each shared session, every decision and who made it.
Sharing is off until the developer and your organisation both turn it on.
Sessions, tokens, cost and tool calls by agent, project and person.
Counts only. No prompts or replies.
Prompts, replies and tool output, once it's turned on in the agent and in your organisation.
Developers join through an invitation in the desktop app, and from then on your organisation's settings apply to their sessions.
Every switch can only narrow what your deployment allows, and every change is logged.
Sessions come in from the tools your developers already use.
Sign-in with Microsoft Entra.
Hosted by us, or inside your own environment.
We'll come back with a setup and a quote.