Dagobert
github.com
- Linux
- Web
- API
- Self-hosted
What Dagobert is
Dagobert is a free, MIT-licensed, open-source workspace for incident response and forensic investigations. It supports separate case workspaces with role-based, per-case access managed in the interface. Teams can track timelines, assets, indicators, evidence, malware, tasks, notes, comments, and findings, with CSV import and export for structured records. A cross-case dashboard provides a MITRE ATT&CK heatmap, unified timeline, evidence and indicator tracking, and a lateral movement graph. Reports are generated from user-supplied Word, Excel or Calc, Writer, and Impress templates in DOCX, ODS, ODT, and ODP formats. Background jobs can process evidence with Hayabusa, Zircolite, Chainsaw, Plaso, and Dissect. Indicator enrichment can query VirusTotal, AbuseIPDB, and Hybrid Analysis, and timelines can exchange with Timesketch. Hooks trigger automations on record changes. An authenticated, read-only MCP endpoint exposes case data. Dagobert is a Go binary backed by SQLite, with Docker self-hosting instructions, local or OIDC sign-in, and optional OIDC provisioning.
Who it suits
The project identifies DFIR consultants handling outside-client cases as its primary audience, with internal CIRT and SOC teams as a secondary audience. It suits teams wanting a self-hosted collaborative investigation workspace.
Good to know, and what to watch
- Separate investigations with per-case role-based access
- Cross-case MITRE ATT&CK heatmap and unified timeline
- Generates multiple document and spreadsheet report formats
- Supports evidence-processing tools and indicator enrichment
- Provides authenticated read-only MCP access
- No commercial offering, pricing, or support tier
- README advises against direct internet exposure
- Repository releases page states there are no releases
- Support is directed to GitHub issues
The verdict
Dagobert provides broad case tracking, collaboration, evidence processing, reporting, and integrations in a self-hosted open-source package. Its lack of commercial support and release listings matters when planning operational ownership.
What the maker publishes
- Authentication
- Users can sign in with built-in local accounts or an OIDC provider; OIDC auto-provisioning is optional. source
- Automation
- Hooks can trigger automations when records are created or updated, with conditions written as expr expressions. source
- Automation and API
- Hooks can trigger automations on record creation or updates, and an authenticated HTTP MCP endpoint exposes case data read-only to MCP clients. source
- Case management
- It supports multiple investigations in separate workspaces with role-based, per-case access control managed in the UI. source
- Commercial status
- The product document says there is no commercial offering, pricing, or support tier. source
- Deployment
- The project describes itself as a single Go binary backed by SQLite and provides Docker-based installation instructions for self-hosting. source
- Evidence processing
- Background evidence-processing jobs can use Hayabusa, Zircolite, Chainsaw, Plaso, and Dissect. source
- Integrations
- Indicator enrichment can query VirusTotal, AbuseIPDB, and Hybrid Analysis, and Dagobert can exchange timelines with Timesketch. source
- Intended users
- The product document identifies DFIR consultants working cases for outside clients as its primary audience and internal CIRT/SOC teams as a secondary audience. source
- Investigation features
- Features include a cross-case dashboard with a MITRE ATT&CK heatmap, a unified timeline, evidence and indicator tracking, and a lateral movement graph. source
- Investigation records
- Teams can track timelines, assets, indicators, evidence, malware, tasks, notes, and comments, with CSV import and export for structured records. source
- License
- The repository states that Dagobert is released under the MIT License. source
- License and releases
- The repository identifies the project as MIT-licensed and its releases page states that there are no releases. source
- Maker
- The repository owner’s GitHub profile identifies the maker as Thomas Kastner. source
- MCP access
- An authenticated, read-only MCP endpoint exposes case data to MCP clients using an API key created in the UI. source
- Purpose
- Dagobert provides incident response teams a shared workspace for forensic investigations, including findings, timelines, tasks, notes, and report generation. source
- Reporting
- It generates reports from user-provided Word, Excel/Calc, Writer, and Impress templates in DOCX, ODS, ODT, and ODP formats. source
- Reports
- It generates reports from user-supplied Word, Excel/Calc, Writer, and Impress templates in .docx, .ods, .odt, and .odp formats. source
- Security controls
- The configuration reference says secure cookies and the Strict-Transport-Security header are enabled by default, and describes a compressed and decompressed archive size limit of 10 GiB each. source
- Security guidance
- The README warns against exposing Dagobert directly to the internet and recommends deploying it behind an HTTPS reverse proxy with access restricted to the team. source
- Support
- The README directs users to open a GitHub issue for questions and bug reports. source
Checked against the maker's pages on 7 Oct 2026.