Fight fire with DFIRe.

Case management for digital forensics and incident response

DFIRe keeps cases, evidence with chain of custody, indicators, regulatory deadlines and reports in one place. It runs on your own infrastructure, with no seat limits and no vendor access.

v1.12.2ChangelogDocumentation90-day trial

The DFIRe dashboard: active cases with severity, phase, team and status, and an incident open in containment

Exhibit 01dashboard-light.webp

Unlimited

users and cases on one licence

15

default playbooks to start from, and no limit on your own

12

enrichment providers, called with your own API keys

90

day trial with every feature included

01How a case runs

From first alert to final report.

Follow one ransomware incident through DFIRe. Most of the team's time goes into three places: the actions, the timeline and the report. All three work from the same case record.

  1. CriticalDeclare

    Open the case and declare the incident.

    A responder opens the case, or an integration opens it through the API. The playbook for the case type adds its fields and the actions for each phase, and the incident clock starts.

    Incident response
    Incident timeline with the phase, the incident duration and entries for added evidence and indicators
  2. ActionsRespond

    Work through the response actions.

    The playbook fills the Actions tab with the response steps for each phase. Start from one of the fifteen default playbooks, edit it, or build your own.

    • Assign each action to an investigator, or to a team or an outside organisation.
    • Block an action with a note on what it waits on. It keeps its phase open until it moves.
    • Mark it done and post the completion note to the timeline.
    • Add the steps the playbook did not foresee.
    The action checklist
  3. EvidenceCollect

    Put the evidence on the record.

    Add each item with its type, location and attributes, in a hierarchy that shows what came from where. DFIRe encrypts files with AES-256 under keys per case and per item, and hashes every custody handover into a chain.

    Evidence Try the custody chain
    Evidence tab with a workstation, its EDR log and a file server in one hierarchy
  4. IntelEnrich

    Enrich and correlate indicators.

    Indicators go into a registry shared across cases, so a second sighting shows at once. Enrichment runs with your own keys for VirusTotal, AbuseIPDB, GreyNoise, Shodan and eight more providers.

    Indicators of compromise
    Indicator list with a file hash, a domain and an IP address, each marked malicious and TLP:AMBER
  5. TimelineRecord

    Keep one timeline of the incident.

    DFIRe records evidence, indicators, phase changes and completed actions on the timeline as they happen. Add entries for what happened outside DFIRe, and hide the ones that do not belong in the report.

    Timeline
    Timeline entries for indicators, evidence and a phase change, each with its time and author
  6. DeadlineNotify

    Watch the regulatory clock.

    Start a timer for each notification you owe, such as the 72 hours GDPR gives you to notify the data protection authority. The case shows the time left, and a reminder goes out while it still matters.

    Compliance timers
    Compliance tab with a GDPR data protection authority notification timer and its time remaining
  7. ReportClose

    Write the report from the record.

    DFIRe generates the title page, the timeline, the indicators and the evidence inventory from the case. Each written section goes through QA on its own, and an LLM you choose can draft a section if you switch it on.

    Reports

02Chain of custody

Tamper-evident chain of custody.

DFIRe hashes every custody entry together with the one before it. Change one field and every hash after it changes, so an alteration shows instead of passing silently.

  • SHA-256 over the whole entry. The hash covers parties, times, location, purpose, condition and notes, and links to the entry before.
  • Checked each time it opens. A failed check names the entry and stops further transfers for that item.
  • Verifiable without DFIRe. Export the chain as JSON and check it with a short Python script. It needs no access, credentials or network.

Workstation - J. Virtanen (Patient Zero)

CASE-2026-5897 · Custody · demo data

Verifying the chain…This page recomputes every hash in your browser.
    verify_custody_chain.py, run in this page
    Waiting for the chain to load.

    03Capabilities

    The whole case in one system.

    All features are included in one licence. Click the parts below to see their documentation.

    Enriched and shared indicators

    Keep indicators on the case and in a registry across cases, so a second sighting is obvious. Enrich them with your own keys, then publish to your threat intelligence platform over TAXII 2.1 or as a MISP feed.

    Indicators of compromise

    Compliance deadline tracking

    Set timers for GDPR, NIS2, DORA, HIPAA, SEC and your own rules, and get a reminder before time runs out.

    Compliance timers

    Per-item encryption

    DFIRe encrypts attachments up to 4 GB with AES-256-GCM, under separate tenant, case and item keys.

    Storage

    Reports from the case record

    You define the sections. DFIRe generates the inventories and timelines, and QA keeps a second reader in the loop.

    Reports

    Fail-closed audit logging

    DFIRe writes every action to the audit log before the action completes. If that write fails, the action does not happen.

    Audit log

    Integrations and a full API

    Coordinate in Slack and sync with Jira Cloud both ways. The REST API is open to your integrations, so external systems can create cases, indicators, evidence items and other records in DFIRe.

    Integrations

    SSO and role-based access control

    Sign in over OIDC, build roles capability by capability, and scope access to each case team.

    Users and roles
    VirusTotalAbuseIPDBAlienVault OTXGoogle Safe BrowsingGreyNoiseMalwareBazaarMISPShodanSpurThreatFoxURLhausurlscan.ioDNSWHOIS
    SlackJira CloudTAXII 2.1STIX 2.1OpenAPIModel Context ProtocolOIDCAmazon S3SMB/CIFSSFTPPostgreSQL 16+Docker ComposeAmazon SESMicrosoft 365AnthropicAzure OpenAIGemini

    04Security

    How DFIRe protects case data.

    Your security team will review DFIRe before it reaches production. The answers are in the documentation, and every release carries its own evidence.

    • Your infrastructure only

      DFIRe runs on Docker Compose on your hosts, with your PostgreSQL and your storage. The vendor has no access to your instance.

      Deployment
    • Air-gapped option

      The standard licence checks in with the DFIRe licence server. Convert it to an offline licence to run DFIRe in an air-gapped network.

      Air-gapped installs
    • Encryption with separate keys

      AES-256-GCM protects attachments and backups. Stored credentials use a key separate from the file keys.

      Application security
    • Fail-closed audit log

      An action without an audit record does not happen. Forward the log to your SIEM and keep it under your own retention.

      Audit log
    • Access per case

      Sign in over OIDC, use TOTP for password accounts, and compare roles side by side.

      Single sign-on
    • Supply chain controls

      DFIRe pins its dependencies and adopts no version younger than 14 days. Each release ships an SBOM and build provenance for both images.

      Supply chain
    release/x.x.x/SHA256SUMS
    $ curl -fsSL https://dfire.fi/release/x.x.x/SHA256SUMS
    Loading the checksums of the current release.

    Each release publishes checksums, SBOMs and build provenance next to its Compose bundle. The installer verifies the bundle against these checksums.

    05Install

    Running in two commands.

    The installer downloads a release-pinned, verified Compose bundle, generates the secrets and the configuration, and starts the services.

    1. Download the installer

      curl -fsSL https://dfire.fi/install.sh -o install.sh
    2. Run it

      chmod +x install.sh && ./install.sh

      The script walks through the configuration and starts DFIRe. Production binds to localhost, behind your own HTTPS reverse proxy. Plain HTTP on port 8080 is an explicit choice for evaluation.

    3. Sign in and open a case

      The quick start covers first sign-in and your first case. Air-gapped and custom deployments start from the deployment guide.

    06Pricing

    One licence per production installation.

    The price does not change with seat count, company size or the features you use.

    Non-commercial

    Free

    Granted case by case

    • Individual, student and educational use
    • Small charities and community efforts
    • All features included
    Am I eligible?

    Small teams

    Let's talk

    Smaller team or tighter budget

    • Custom pricing for small organisations
    • Same deployment model and features
    • Unlimited cases
    Contact us
    Training for your team: live online workshops for analysts and for administrators. Training workshops

    Questions

    Before you buy

    Anything else, ask us. We answer by email, usually within two working days.

    What does one licence cover?

    One production installation of DFIRe, with unlimited users, unlimited cases and every feature.

    How does the trial work?

    Every installation starts with a 90-day trial. Install DFIRe, run real cases with your team, and buy a licence by invoice or by card when you decide to keep it.

    Can DFIRe run in an air-gapped network?

    Yes, with an offline licence. By default, DFIRe checks its licence online and needs to reach the DFIRe licence server. An offline licence removes that connection. The deployment guide covers installing without internet access.

    Where does our case data live?

    On your own infrastructure. DFIRe is self-hosted only, you choose the database and the storage backends, and the vendor has no access to your instance.

    Who qualifies for a free licence?

    Individuals, students, educators, small charities and volunteer efforts doing non-commercial work can ask. We grant them case by case. Read the details.

    Do you offer training?

    Yes. A four-hour live online workshop for analysts, and a shorter one for administrators. See the curriculum and prices.

    Put every incident on the record.

    Install it on your own hardware and run a real case this week. There are no seat counts to declare, and no case data leaves your network.