Your leaked credentials, found first.
darkforce ingests public breach data, dedupes every record, and matches it to the domains you watch. Your team gets a ticket the same hour a credential lands.
How it works
Collect
We pull breach data from public sources and run it through a dedup pipeline. One credential, one record.
Link
Records get matched to the domains you monitor and sorted by exposure type.
Act
Tickets, alerts, and dashboards put each finding in front of the person who can close it.
Features
Records core
SHA-1 dedup, hash-addressed records, severity labels, and notes on each one.
Tickets
Auto-ticketing with three comment tiers and a full status lifecycle.
Alerts & delivery
Multi-channel receivers, write-only secrets, and SSRF guards baked in.
Pipeline ops
Drain controls, worker health, and partition rotation runbooks.
Audit viewer
Bounded exports and a side panel for every sensitive read.
Dashboards
Role-scoped counts. Switch between exact and estimate numbers as you need.
Public API
Token-auth REST that mirrors the UI, plus an OpenAPI spec that never goes stale.
Observability
Request correlation, health probes, and SLO signals across the stack.
Pricing
Business
- Up to 25 monitored domains
- Full alert channels
- Audit viewer + exports
- Priority support
Enterprise
- Unlimited domains
- Public API + SSO
- Dedicated support
- Custom retention
Why it matters
Cross-tenant isolation, write-only secrets, server-side authority, and a full audit trail. Security runs on the server, not in the browser.
Read the Security & Privacy overviewFAQ
Where does the breach data come from?
Public breach datasets. We aggregate them and run each through a gated, deduplicating pipeline.
How are credentials deduplicated?
Every record is normalized and SHA-1 hashed against one authoritative index. One credential yields one record.
Can I integrate programmatically?
Yes. The public REST API uses Sanctum bearer tokens, mirrors every UI action, and ships an always-current OpenAPI spec.
Is my data shared across tenants?
No. Every query is scoped to your company. A cross-tenant lookup returns the same 404 as a missing record, so nothing leaks.