IMS Incident Monitoring System
Real-time incident intelligence · pre-launch · founding cohort open

See the pattern before the headline.

Real-time, source-corroborated incident intelligence for UN missions, multilateral agencies, and institutional security teams. Search any country in 500 ms. Generate a briefing-grade PDF in one click. Forward to your superior with a tamper-proof audit trail.

Built on public open-data signals — full source registry available on request to qualified buyers.
Published indicative pricing · no sales-call to evaluate
Public live feed · no login required
Source-cited on every card · no black-box scoring
Pre-launch · founding-partner programme open
A subset of the active source feeds today — full live registry on request
Listed sources are confirmed integrations or active pilots. Additional source families are on the roadmap and listed in the registry. We do not claim integration with any source we have not yet built against.
The three-step workflow

Search. Brief. Forward.

The act of producing a credible threat brief, collapsed onto a single screen.

01

Search

Type a country, region, or keyword. Results in under 500 ms. Filter by severity, source, time window, or geographic radius.

Sudan refugee corridor — last 72h
Severity ≥ 3Verified onlyGeo: Darfur, Chad border
02

Brief

Drag incidents into the side panel. One click generates a UN-style PDF briefing — executive summary, timeline, geo heat-map, source provenance, and a tamper-proof SHA-256 hash.

OFFICIAL USE ONLY
Situation Brief — Darfur Corridor
SHA-256 · 4f8a…e21c
03

Forward

Send the brief to your superior via secure link. Full audit trail: who opened, when, from where. Optional auto-route to mission lead by region.

ToDSS Regional Security Officer · East Africa
Linkims.app/b/4f8a-e21c · expires 7d
AuditOpened 2 times · last from Nairobi · 12:47 UTC
IMS workflow walkthrough
Animated 12-second walkthrough · the full interactive tour is below.
Self-guided tour · 60 seconds

Click through the workflow as an analyst would.

Live Feed
Search
Briefs
desk-officer · East Africa
Step 1 — Search. Three incidents, source-cited, in under 500 ms. Click 2 · Brief to see what happens when an analyst drags these into the side panel.
Built for the people who actually use it

Three operators. One console.

UN & Multilateral Agencies

Diplomatic security, field-mission safety, OCHA situational awareness, country-team daily briefings. Replaces the morning OSINT scramble.

  • Mission-team workspaces with role-based access
  • Country-desk daily auto-brief at 06:00 local
  • Procurement-ready: SOC 2, GDPR, EU data residency
Talk to us about a UN pilot →

Institutional Security Teams

Embassy DSS officers, corporate global security, sovereign-wealth risk desks. Same console, different data ACL — political risk meets operational ground truth.

  • Executive-protection geofencing
  • Asset & facility watchlists
  • API access for SIEM / SOC integration
Talk to us about an institutional pilot →
Inside the console

Anatomy of a corroborated incident.

Every card in IMS is auditable down to the source URL and timestamp. This is what an analyst sees — and what your buyer will paste into their procurement deck.

Severity 3 · Verified
12:14 UTC · 23 Apr 2026

Convoy attacked on El Fasher–Tawila road, North Darfur

North Darfur, Sudan 13.6278° N, 25.3531° E Conflict · Civilian
Sources · 4 corroborating
  • ReliefWeb12:04 UTCsituation report 042/2026
  • AFP12:07 UTCwire alert
  • OCHA Sudan12:09 UTCflash update
  • Local channel (verified)12:14 UTCTelegram · ID 4471
Suggested escalation

Forward to DSS Regional Security Officer, East Africa · auto-include adjacent corridor incidents (last 48h).

How we verify

Provenance is a feature, not a footnote.

1

Deduplication

The same event reported by four sources surfaces as one incident — not four. We cluster on entity, geo, and time, not just text similarity.

2

Cross-corroboration

A signal is promoted to Verified only when ≥ 2 independent sources of distinct type confirm the core facts. Single-source items remain visible but flagged.

3

Provenance hashing

Every fact is hash-linked to its original source URL and timestamp. Every PDF export carries a SHA-256 you can verify offline. No invisible edits, ever.

Where IMS wins

IMS vs. the alternatives.

An honest comparison. Where the incumbent is genuinely better, we say so.

IMS Dataminr First Alert Manual OSINT
Public live feed (no login required)YesNoN/A
One-click UN-style briefing PDFYesNoManual
Source-by-source provenance on every cardYesPartialYes
Tamper-proof export (SHA-256)YesNoNo
Transparent pricingYesNoN/A
Time-to-first-pilot14-day target≥ 60 days typicalN/A
Designed for multilateral procurementYesGenericN/A
Raw signal scale (firehose volume)CuratedBest-in-classLimited
Years of brand recognitionEmergingEstablishedN/A

We win on workflow, transparency, and procurement fit. Dataminr wins on raw scale and brand recognition. If your job is to produce a credible brief by 09:00, IMS is built for you.

Security & compliance

What gets you past ICT review.

EncryptionTLS 1.3 in transit · AES-256 at rest · live today
Privacy by designNo facial recognition · no PII scraping · public sources only · live today
GDPR alignmentPrivacy-respecting architecture today · DPA template available on request · EU data residency on contract (not currently provisioned)
SOC 2Roadmap: Type I targeted Q3 2026 · not currently in audit
SSORoadmap: SAML 2.0 (Okta, Entra ID, Google Workspace) · bespoke integration on contract today
On-prem / air-gappedRoadmap: signed Helm chart · bespoke build available on contract today

Roadmap items are stated as roadmap. We will never label a planned capability as “available” on this page. Ask us for the engineering log if you want to see exactly where we are.

Pricing

Transparent. Tiered. No "contact sales" wall.

Public
$0
Read-only access to the public live feed.
  • Live feed of verified incidents
  • Search by country & keyword
  • Source citations visible
  • No PDF export · No alerts
Open the live console →
Institutional
Talk to us
Multilateral agencies, embassies, sovereign desks. Bespoke engineering today; productised tier on the roadmap.
  • Everything in Mission
  • Custom source ingestion (private feeds, RSS, APIs) — bespoke today
  • SSO · role-based access · custom domains — roadmap Q3 2026
  • On-prem / air-gapped deployment — bespoke today, productised roadmap
  • Named contact · SLA · custom DPA
Book an institutional briefing
Resources

Briefing-grade material, ungated.

If we want you to trust us with a mission, we have to start by being trustworthy with our writing.

Intel brief · 6 pages · ungated PDF

Sample Mission Brief — Recent Verified Incidents

A live-generated, SHA-256-stamped PDF built from the last 24 hours of corroborated incidents on the public feed. The exact format your team would receive.

Download the sample PDF →
Curated brief · 14-day · ungated PDF

Sahel Corridor — 14-day Situational Brief

Auto-curated from public GDELT 2.0 articles + IMS corroborated incidents across Mali, Burkina Faso, Niger, Chad & Sudan. SHA-256 verifiable.

Download the Sahel brief →
Audit walkthrough · 8 pages · ungated PDF

Audit Trail — One Incident, Seven Phases

Worked example following one synthetic incident through signal, cluster, corroborate, brief, forward, open, verify. Hand to your security/audit team.

Download the audit trail →
Pre-filled SIG-Lite · ~150 questions · PDF

SIG-Lite Security Questionnaire — Scaffold v1

The Shared Assessments SIG-Lite, pre-filled with IMS architecture. Every row tagged ANSWERED · PARTIAL · PLANNED · ORG-SPEC · N/A. Read it before the call.

Open SIG-Lite scaffold →
Live webinar · 45 min

How OSINT verification actually works

A walk-through of dedup, cross-corroboration, and provenance hashing — with a live incident worked end-to-end.

Reserve a seat →
Sample artifact · PDF

Mission brief · template & example

The exact UN-style PDF IMS produces — classification banner, source list, geo heat-map, SHA-256.

Download a sample →
Founding Partner Program

The first ten missions get to shape the product.

IMS is being built in the open, with a small cohort of UN missions, humanitarian operators, and institutional security teams. Founding Partners get direct access to the team, custom source ingestion, and lifetime preferred pricing.

  • Direct line to the engineering team — your roadmap influence is real.
  • Custom source ingestion for your private feeds, included.
  • Lifetime preferred pricing — no surprises at renewal.
  • Co-authored case study, only with your explicit approval.
Apply for the program →
From signal to action

Brings clarity when minutes matter.

Every minute between a signal appearing and a decision being made is a minute that costs your operation. IMS exists to close that minute.

Book a personalised briefing →
FAQ

Procurement-grade questions, answered up front.

Where does your data come from?

Public open-data sources only at this stage: GDELT 2.0, ReliefWeb, OCHA, and a set of newswire and humanitarian feeds. The live /tracker/api/processor/status endpoint returns the real active source count and the real incidents-in-last-24h as live numbers — those are the numbers shown in the stats strip above when the API is reachable. We do not invent counts.

How do you handle source bias?

We never weight a source by editorial stance. Promotion to Verified requires ≥ 2 independent sources of distinct type (e.g., wire + sitrep, not two wires). Single-source items remain visible but explicitly flagged.

What happens if a source is wrong?

Retraction is propagated within minutes — the incident card is marked Retracted and any forwarded brief surfaces a banner the next time it is opened. The audit trail is preserved.

Can we self-host?

Yes — air-gapped on-prem deployment is available on the Institutional tier. Includes a signed Helm chart, hardened base images, and quarterly security patches.

What languages does the system handle today?

The ingestion pipeline parses signals across multiple source languages (the multilingual GDELT 2.0 corpus is one feed; ReliefWeb publishes in EN/FR/ES; AFP feeds are multilingual). The briefing UI is currently English-only — additional UI locales are on the roadmap and will be prioritised by the founding cohort. We don't claim a specific language count until each one is fully tested end-to-end.

What is your uptime SLA?

Uptime SLA is offered on contract, not as a marketing claim. Live status is published at /ims/status, which reflects real numbers from the operating console at quintarthai.com/tracker. We will not advertise an SLA percentage we cannot defend in a procurement audit.

How long is a typical pilot?

Target time-to-pilot is 14 days from signed contract. We are pre-launch and have not yet completed our first paid pilot, so this is a target — not a measured median. Procurement docs (DPA template, security questionnaire) are available on request; the SIG-Lite pre-fill is on the founding-cohort roadmap.

Start with the live console.
When you're ready to brief your team, we are too.

Pilots in 14 days. No 12-month contract to find out if it works.

We reply within one business day. No spam, ever.