DFIRe vs SandsBytes
DFIRe
dfire.fiSandsBytes
sandsbytes.comSide by side
| Figure | DFIRe | SandsBytes |
|---|---|---|
| Price from | €825/mo | — |
| Free plan | Yes | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 3 | 0 |
| Spec score · Incident Response Software | 9.1 (#1) | 7.3 (#16) |
| Deployment | Installation uses a release-pinned Docker Compose bundle and supports manual or air-gapped deployment. | The platform is deployed as a containerized stack on Ubuntu Linux 20.04.6 LTS or later, with Docker Engine and Docker Compose. |
| Headquarters | Vantaa, Finland | Riyadh, Saudi Arabia |
| Integrations | Native integrations include Slack case workflows, two-way Jira Cloud synchronization, outgoing webhooks and SIEM/SOAR forwarding. | Workflows can connect to external systems such as HTTP APIs, databases, queues, and file storage. |
| Product purpose | DFIRe is a self-hosted case-management platform for digital forensics and incident response. | SandsBytes is a cybersecurity investigation and incident response case management platform for triage, threat hunting, evidence, IOCs and reports. |
| Security controls | The security documentation describes OIDC single sign-on, two-tier role-based access control, AES-256-GCM attachment encryption, and an immutable fail-closed audit trail. | Deployment instructions call for setting unique secrets for authentication, internal service communication, database access, and SMTP credential encryption. |
| Support | Documentation covers deployment, configuration, cases, evidence, SSO, backups, integrations, security and changelog topics; additional help is offered by email. | The maker directs customers to [email protected] for deployment sizing questions and unresolved support issues. |
| Threat intelligence | The IOC registry supports STIX 2.1 types, enrichment from named threat intelligence providers, and sharing through MISP and TAXII. | Sands Investigate enriches artifacts with threat intelligence and external lookups and detects IoC hits and suspicious patterns. |
Plans
In their own words
DFIRe
DFIRe is self-hosted case management software for digital forensics and incident response. Teams can configure case types, severity, assignments, and escalation from triage to incident response while keeping case history. Evidence records can be organized hierarchically with configurable attributes, custody verification, printable receipts, and transfer records. The software includes default playbooks for fifteen common case types, which users can adapt or replace, plus timers and reminders for breach notifications, statutory reporting, and other deadlines. Its IOC registry supports STIX 2.1 types, enrichment from named threat intelligence providers, and sharing through MISP and TAXII. Documented integrations include Slack, bidirectional Jira synchronization, webhooks, and SIEM or log forwarding. Reports support structured sections, QA, evidence inventories, and optional LLM drafting through a customer-selected provider. Security documentation describes OIDC sign-on, role-based access, encrypted attachments, and an immutable audit trail. DFIRe supports air-gapped use and offline licensing. The annual licence is €9,900 a year for unlimited users and cases in one production deployment; a 90-day trial is available.
SandsBytes
SandsBytes is a cybersecurity investigation and incident response case-management platform for triage, threat hunting, evidence, indicators of compromise, and reporting. Its three products divide that work: Sands Investigate converts forensic artifacts into searchable, ECS-normalized records, enriches them with threat intelligence and external lookups, and flags indicator matches and suspicious patterns. Sands Manage supports collaborative cases with evidence, timelines, findings, task assignment, indicator tracking, and automated reports. Reports can be produced as PDF or DOCX files from configured templates. Sands Flow offers visual playbooks for enrichment pipelines, alert routing, and service-level escalation. Workflows can connect with external HTTP APIs, databases, queues, and file storage. The Hunt interface supports dashboard and table analysis, pivot filtering, CSV export, and bulk tagging. Deployment is self-hosted on 64-bit Ubuntu 20.04.6 LTS or later, accessed with Chrome, Firefox, or Edge; minimum resources are 6 CPU cores, 16 GB RAM, and 100 GB free storage. A license key expires after its specified validity period, and access is rejected until renewal. Pricing is on request.