Feature matrices reward whoever wrote them. The questions below cannot be answered by a checkbox, which is why they are useful. Bring the list to every call on your shortlist and write the answers down in the vendor’s own words. Ours are here, and three of them are a no.
Ours: three approval modes per conversation, a floor that unattended mode cannot cross, the risk and the exact command shown first; skip, reorder, redirect or stop mid-run.
Ours: none. Open-weight models on infrastructure we run, or yours. No OpenAI, Anthropic or Azure OpenAI account anywhere in the product.
Ours: yes. Credentials are injected server-side from the vault; the plaintext never reaches the browser.
Ours: live. We retired the sync; nothing is duplicated, so nothing drifts.
Ours: none on a managed endpoint. Optional, scoped listeners for a collector and an SNMP trap receiver.
Ours: sign-ins immutable; service desk history append-only, enforced by the database; every credential reveal recorded. Append-only, not hash-chained; we will not call it tamper-proof.
Ours: no. Single-tenant per customer, always.
Ours: not today. T&M and project billing work; automated agreement billing is on the roadmap.
Ours: your single-tenant database, the audit trail and documentation export. You cannot take one module elsewhere.
Ours: not yet. If you are migrating a large documentation estate, this shapes the timeline.
If recurring agreement billing is your month-end, if you are migrating thousands of articles, or if you want to buy one module and keep the rest of your stack, we are probably not your answer yet. Better to know now than three months into an implementation.
Your network is the hard part. You are tired of the seams. You want automation you will actually enable. If one of those is you, the linked-records argument is not marketing; it is the reason to switch.
Each question with why it matters, what a good answer sounds like, and ours. Bring it to every call on your shortlist.