The problem
You already own a ticketing tool, a case folder, and a risk register. 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.
One workspace for intelligence teams that cannot afford gaps.
Incidents, investigations and exposure on one shared record. What you uncover in one module is already working for you in the next.
PrismPulseHorizon
The shift
Opsidian runs the three 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, and feed the risk radar with events that really happened.
All three read and write the same records, which is what buys you this:
Nothing is typed twice
The people and companies named in an incident arrive in the investigation as records, not as text to re-key.
Cross-match finds you
A name entering a second case notifies everyone holding it, without exposing a case you are not cleared to open.
The picture is never stale
Exposure reflects what your team logged this month, not the date of the last review.
Configuration
One platform. Your risk domain.
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.
The same three modules, configured for your domain
| Domain | Event categories you define | What it then monitors and scores |
|---|---|---|
| Corporate security | Intrusion, threat to staff, loss of property | 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 three modules, no new release |
What you define, in the library, without writing anything:
Event categoriesSeverity scalesTagsKeywordsKeyword categoriesSearch patternsRisk scenario templatesGeographiesKPI dashboards
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
Which scenarios should your risk register carry?
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.
1Sector2Operations3Exposure
What does your organisation do?
Pick the closest sector. It fills in the next two answers, which you can correct.
Nothing is stored unless you ask for the full list.
Modules
Three modules. One live risk picture.
Prism accumulates what you know. Pulse handles what happens. Horizon scores what it means.
Explore each module
Prism
Investigations & due diligence
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.
Pulse
Events & response
Events and incidents in the same place. Not an incident tool: physical security, fraud, compliance and operations share one queue and one triage path.
Horizon
Exposure & scenarios
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.
Across all three
One record, three modules.
One shared entity
The same person, company, phone or IBAN in the event, the case and the risk profile. Not an integration between separate tools: one record they all read.
Customizable KPI dashboards
The numbers your team is actually measured on, not a fixed template.
Alerts and tasking
Every module raises to the same queue, ordered by what is due.
Collaborative workspace
Shared cases, assignments, notifications and a common library across the team.
Plans
Start focused. Scale across the operating picture.
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.
AI assisted work: Limited
Prism module
Active investigations: 3
Pulse module
Users max: 1
Graph visualization
Plus
Best fitScale
5 users / limited access
Higher usage limits with exports and limited library customization.
AI assisted work: Limited
Prism module
Active investigations: 10
Pulse module
Horizon module
Atlas module
Users max: 5
Graph visualization
Graph edition
Exports access
Bulk case import
Library customization: Limited access
Single sign-on (SSO)
AI report writing
Pro
Full
10 users / full access to all features
Full usage, graph editing, exports, and complete library customization.
AI assisted work: Full access
Prism module
Active investigations: 25
Pulse module
Horizon module
Atlas module
Users max: 10
Graph visualization
Graph edition
Exports access
Bulk case import
Library customization: Full access
Single sign-on (SSO)
AI report writing
Governance
Controls where the decisions happen.
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
Answer governance questions before the call.
Opsidian keeps security, access, source handling, and audit context visible where the work happens.
Is customer data isolated?
Yes. Opsidian is built around tenant isolation, role-aware access, and confidential workflow boundaries.
Do you support SSO or MFA?
Privileged paths are MFA-ready today. SSO and enterprise auth requirements are reviewed during onboarding.
How long does onboarding take?
Invite-only pilots are scoped around the workflows you want to centralize and the data handling needs around them.
Is a trial available?
Access is currently handled through controlled pilots rather than open self-serve trials.
Opsidian
See it on your own data.
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.