Incidents, investigations and exposure on one shared record. What you uncover in one module is already working for you in the next.
The problem
You already own a ticketing tool, a case folder, a risk register and a news feed. Monday’s incident never reaches the register, the second investigation never learns what the first one found, and the exposure review is a snapshot nobody trusts.
The shift
Opsidian runs the four in one place. Declare an incident, triage it and drive the follow-up into a full investigation when it warrants one. Run due diligence on what that turns up, feed the risk radar with events that really happened, and let news monitoring open the next case.
All four read and write the same records, which is what buys you this:
The people and companies named in an incident arrive in the investigation as records, not as text to re-key.
A name entering a second case notifies everyone holding it, without exposing a case you are not cleared to open.
Exposure reflects what your team logged this month, not the date of the last review.
Configuration
Nothing here is hard-wired to one kind of risk. The taxonomy is data you own rather than code we ship, so the same workspace runs whichever domain your team is accountable for.
| Domain | Event categories you define | What it then monitors and scores |
|---|---|---|
| Corporate security | Intrusion, threat to staff, asset loss | Site and travel exposure |
| HSE | Near miss, injury, spill, equipment failure | Site safety and environmental release |
| Financial crime | Suspicious transaction, sanctions hit, internal fraud | Counterparty and sanctions exposure |
| Natural hazards | Flood, storm, seismic event, wildfire | Business interruption and site damage |
| Geopolitical events | Unrest, expropriation, export control | Country instability and route disruption |
| Anything else | Categories you write yourself | The same four modules, no new release |
What you define, in the library, without writing anything:
Why it matters
Configuration, not development. Adding a category, a scenario or a source is an afternoon in the library, not a professional services engagement and not a release cycle. One team can run several domains side by side in the same tenant, each with its own taxonomy.
Try it yourself
Three questions, no account, no cookie. This runs the same matching the product runs - your answers against a curated library of security scenarios - so you see what a register built for your organisation would open with.
Pick the closest sector. It fills in the next two answers, which you can correct.
Modules
Prism accumulates what you know. Pulse handles what happens. Horizon scores what it means. Atlas watches what is coming.
An investigative database that compounds. Every case adds entities, links and findings to a base your whole team works from. Prism is worth more in year two than it was in year one.
Events and incidents in the same place. Not an incident tool: physical security, fraud, compliance and operations share one queue and one triage path.
Where you are exposed, what could hit you, what you are doing about it. Assisted risk profile building on your real footprint, at whatever granularity you work in: a single site, a country, the whole group.
Local news, read locally. A monitoring system for the countries you operate in, searched in their own language and tuned by you rather than by a vendor default list.
Across all four
The same person, company, phone or IBAN in the event, the case, the map and the risk profile. Not an integration between four tools: one record they all read.
The numbers your team is actually measured on, not a fixed template.
Every module raises to the same queue, ordered by what is due.
Shared cases, assignments, notifications and a common library across the team.
Plans
Starter
Entry
1 user / a taste of the full platform
A taste of the full platform: run the core investigation workflow, automated due diligence and assisted search under entry-level caps.
Plus
Best fitScale
5 users / limited access
Higher usage limits with exports and limited library customization.
Pro
Full
10 users / full access to all features
Full usage, graph editing, exports, and complete library customization.
Governance
Not an administration module nobody opens. Access, confidentiality and provenance sit inside the working screens.
Role-aware access
Sensitive cases stay closed, including inside the features that reach across cases.
Access in the flow
Requested, granted and logged where the work happens, not in an admin module nobody opens.
Full audit trail
Every module, every record.
Source provenance
Every claim keeps the source it came from, all the way to a stamped export.
Tenant isolation
Your workspace is yours, separated at the database level.
Bilingual, EN and FR
The whole product, not a translated website.
FAQ
Opsidian keeps security, access, source handling, and audit context visible where the work happens.
Yes. Opsidian is built around tenant isolation, role-aware access, and confidential workflow boundaries.
Privileged paths are MFA-ready today. SSO and enterprise auth requirements are reviewed during onboarding.
Invite-only pilots are scoped around the workflows you want to centralize and the data handling needs around them.
Access is currently handled through controlled pilots rather than open self-serve trials.
Not a canned demo. We set up a tenant, load a sample of what your team actually handles, configure your taxonomy, and show you the cross-match firing on it.