# DFIR Swarm > Open-source agentic digital forensics and incident response. A swarm of AI agents works one forensic case in parallel on a shared board, each agent in a microVM of its own; heavy tool work runs as jobs in throwaway worker microVMs whose output is sealed into a store; a hash-chained trace, a ledger and a custody verdict are written by the host, where the agents cannot edit them. Key facts, as of 2026-09-27: - Source code: https://github.com/halilozturkci/dfirswarm, licensed GNU AGPL v3 or later. - Runs on macOS with Apple silicon or Linux with KVM, one microVM per agent; host mode runs the same swarm unisolated on other machines and is labelled as such. - The agents are Pi sessions; a team can mix cloud providers, a private endpoint and local models. - Editions: Community is free. Pro and Enterprise are by contact: https://dfirswarm.ai/editions#contact - Maintainer: Halil Öztürkci, a digital forensics practitioner: https://dfirswarm.ai/who-builds-this - CTF and challenge answers are never published on this site; the posts and the ledger describe methods. ## Pages - [Home](https://dfirswarm.ai/): Open-source agentic DFIR: a swarm of AI agents works a forensic case in parallel, writes its own tools, and leaves a tamper-evident record fit for a court. - [The platform](https://dfirswarm.ai/platform): An interactive map of the agentic DFIR platform: the evidence, the agents in their microVMs, the tool VMs, the hub, the sealed record, custody and the signed case file. - [The swarm](https://dfirswarm.ai/swarm): How a swarm of forensic AI agents divides a digital forensics case with no orchestrator: peers, a shared board, leases, a critic and agent-written tools. - [The harness](https://dfirswarm.ai/harness): A microVM for every AI forensic agent: evidence read-only, an egress allowlist, keys kept on the host, and a chain of custody the agents cannot edit. - [Case studies](https://dfirswarm.ai/cases): Public forensic challenge images: Windows and Linux disks, memory, a phone, a Hadoop cluster: worked end to end by the swarm and published with the full record. - [Blog](https://dfirswarm.ai/blog): Long reads from the record of real runs: how the agents divided a public forensic case, what they called themselves, which tools they used and what those gave back, what they found and what they missed. - [Editions](https://dfirswarm.ai/editions): Community is free under the AGPL with twelve forensic method and tool packs. Pro adds a verified toolset and prebuilt images; Enterprise, a dedicated host per case. - [Get started](https://dfirswarm.ai/get-started): Install DFIR Swarm, prove the protocol with no key and no network, run two agents on the hello goal, then work your first case with your own evidence. - [Who builds this](https://dfirswarm.ai/who-builds-this): The design decisions behind the forensic harness and the digital forensics practitioner who makes them: twenty-five years in security, founder of two companies. ## Blog - [Bogus Bill: the key to the laptop was on the phone](https://dfirswarm.ai/blog/bogus-bill-the-key-to-the-laptop-was-on-the-phone.md): BelkaCTF 6, worked by the swarm across an iPhone and a Windows laptop: a vault opened with a key found in a note on the phone, a cropped bank screenshot rebuilt from what the crop left behind, a phone Shortcut's cipher re-implemented to read a secret channel, and the questions it did not answer. - [Encrypt Them All: the keys never touched a command line](https://dfirswarm.ai/blog/encrypt-them-all-the-keys-never-touched-a-command-line.md): Ali Hadi's Encrypt Them All, worked by the swarm: a rush for the same seat, a BitLocker volume opened by learning from each failed attempt, secrets passed by reference and never printed, and a critic that signed exact hashes. - [Meeting Location: the case was in the free space](https://dfirswarm.ai/blog/meeting-location-the-case-was-in-the-free-space.md): Ali Hadi's Meeting Location challenge, worked by the swarm with every agent in a tool-less microVM and every heavy step a sealed job: a sweep of the whole free space, a clock that ran backwards, an argument about who did what, and a password nobody found. - [Feed](https://dfirswarm.ai/blog/feed.xml): every post, as Atom ## The case ledger - [The ledger as Markdown](https://dfirswarm.ai/cases.md): every published run, what it asked, the team, the caps, the cost, the time, the checks and what it showed. - [The ledger as JSON](https://dfirswarm.ai/cases.json): the same records, machine-readable. - [Write-ups in the repository](https://github.com/halilozturkci/dfirswarm/tree/main/docs/use-cases): each run's full record: board, ledger, trace and report. ## Source and documentation - [README](https://github.com/halilozturkci/dfirswarm/blob/main/README.md): what it is, how a run works, the guards and their limits. - [Quick start](https://github.com/halilozturkci/dfirswarm/blob/main/docs/quick-start.md): install, prove the protocol, a first swarm. - [Usage](https://github.com/halilozturkci/dfirswarm/blob/main/docs/usage.md): every command and option of swarm.sh. - [Architecture](https://github.com/halilozturkci/dfirswarm/blob/main/docs/architecture.md): the components and how they connect. - [Protocol](https://github.com/halilozturkci/dfirswarm/blob/main/docs/protocol.md): the board, leases and the words the agents use. - [Safety](https://github.com/halilozturkci/dfirswarm/blob/main/docs/safety.md): what each guard holds and what it does not. - [Packs](https://github.com/halilozturkci/dfirswarm/blob/main/docs/packs.md): the method and tool packs. - [Troubleshooting](https://github.com/halilozturkci/dfirswarm/blob/main/docs/troubleshooting.md): kickoff refusals and what to do about each. ## Optional - [security.txt](https://dfirswarm.ai/.well-known/security.txt): how to report a vulnerability. - [Licence](https://github.com/halilozturkci/dfirswarm/blob/main/LICENSE): GNU AGPL v3 or later.