Straight answers, before the briefing.
What the platform monitors, how collection stays authorized, where your data lives, and how every finding traces back to a sealed capture.
Questions buyers ask first.
What does {{PRODUCT_NAME}} monitor?
Public forums, closed communities your organization is authorized to access, deep-web sources, onion services and ransomware leak sites, continuously and in many languages.
Is collection authorized?
It collects only from sources your organization is authorized to access. It never bypasses access controls, compromises accounts or exploits sites. Your own policy decides what is monitored.
Does it download leaked data?
No. Ransomware listings and the files a gang claims to publish are recorded as metadata and defanged references. Leaked files are never downloaded.
Where does our data live?
In your own environment. {{PRODUCT_NAME}} is self-hosted on Kubernetes or Docker Compose, with credentials kept in a vault.
Which AI models does it use?
Local models, a self-hosted model server or an OpenAI-compatible provider you choose. AI results are labelled and never overwrite what the source said.
Which languages can it handle?
Sources in many languages, including Russian and other Cyrillic-script forums, with language detection and optional, labelled translation.
How are new sources added?
As source packages, without changing the platform, and their history can be backfilled.
How do alerts reach our tools?
Watchlists raise alerts you can assign and close, webhooks deliver them to your tools, and a REST API covers everything else.
How do we know collection still works?
Every run ends in a named outcome, each source shows its health, and layout changes are detected.
Can we prove where a finding came from?
Each finding links to a sealed capture with its SHA-256 fingerprint and its full provenance trail.
See it on your own sources.
Tell us what you need. We will walk you through a live capture, from post to sealed record.
Prefer email? Write to {{CONTACT_EMAIL}}.