PAGES
← all tools
◆ Digital Forensics & Incident Response

osdfir-infrastructure

osdfir-infrastructure-2.16.0 open-source

Free plan: not checked yet · Open source: yes

OSDFIR Infrastructure simplifies deploying and integrating open source digital forensics tools to Kubernetes clusters using Helm.

What you can do now

Checking Plays…

Summary

osdfir-infrastructure is an open-source DFIR deployment framework that packages forensic and incident-response services as Helm charts for Kubernetes, with no paid license. It is run by Kubernetes operators or DFIR teams in local or cloud clusters, using configurable charts rather than installing each service separately. The deployment can combine Timesketch, Yeti, OpenRelik, GRR, HashR, and dfTimewolf, with integrations linking investigative timelines, threat intelligence, collection, and processing workflows. Its README places it in the open-source digital forensics infrastructure space; ongoing releases cover authentication, ingress, storage, and multi-instance deployments.

OSDFIR Infrastructure simplifies deploying and integrating open source digital forensics tools to Kubernetes clusters using Helm.

How osdfir-infrastructure helps

Which forensic and incident-response services can my Kubernetes cluster run together?

deploys supported components such as Timesketch, Yeti, OpenRelik, GRR, HashR, and dfTimewolf as integrated Helm-chart components, though the available services depend on the chart configuration

How can I connect forensic collection, processing, and investigation across my environment?

links dfTimewolf recipes, OpenRelik workflows and artifact storage, GRR remote collection, and Timesketch analysis so processed evidence can move between stages

Where can responders correlate forensic timelines with threat intelligence?

provides Timesketch for collaborative timeline analysis and connects it with Yeti, which stores and analyzes observables, tactics, techniques, and campaigns

Can I run separate investigation environments in the same Kubernetes cluster?

supports multiple Timesketch instances and multiple Turbinia instances, allowing distinct deployments within one cluster

How can I preserve or reuse storage and configuration that my cluster already manages?

lets deployments attach existing persistent volume claims and provide existing Timesketch or Turbinia configuration rather than relying only on chart-generated defaults

How do I expose these investigation services securely to my users?

provides configurable ingress, single-host access, external URLs, OIDC authentication for selected services, identity-aware proxy support for OpenRelik, and certificate options through self-signed certificates or cert-manager; the exact protection depends on the configured ingress and authentication settings

all 8 features, with the evidence for each →

Languages

Not documented

Features

8 capabilities

Built from osdfir-infrastructure's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What osdfir-infrastructure offers you

  • Kubernetes-native deployment4
  • Self-hosted deployment1

All capabilities 8 capabilities
Kubernetes deployment via Helm charts Provides Helm charts for deploying OSDFIR cyber tools (Yeti, Timesketch, Turbinia, GRR/Fleetspeak, dfDewey, HashR) on Kubernetes clusters, with support for multiple simultaneous instances, reproducible image-tag pinning, and custom configuration overrides. 33 releases · 4 other sources · first seen Jan 2024

Also counts toward: Kubernetes-native deployment, Self-hosted deployment

Kubernetes ingress and load balancer configuration Configures ingress and global load balancing for OSDFIR Kubernetes deployments, including Nginx integration, self-signed certificates, cert-manager support, and generalised ingress settings for non-GKE clusters. 8 releases · first seen May 2024

Also counts toward: Kubernetes-native deployment

GRR client build and repackaging in-cluster Supports building and repackaging GRR client containers directly within a Kubernetes cluster as part of the GRR/Fleetspeak Helm chart. 2 releases · first seen Sep 2024

Also counts toward: Kubernetes-native deployment

Stateful workload persistence and environment configuration Configures StatefulSets for Yeti Agents with persistent storage and LLM-related environment variables. 1 release · first seen Aug 2026

Also counts toward: Kubernetes-native deployment

Kubernetes service account configuration Allows Kubernetes service accounts to be enabled for all OpenRelik pods via the OpenRelik Helm chart. 1 release · first seen Feb 2026
OpenSearch node initialization Deploys an OpenSearch DaemonSet to apply required sysctl kernel settings on cluster nodes before OpenSearch starts. 1 release · first seen Aug 2025
OIDC authentication for Kubernetes deployments Enables OIDC-based authentication for Turbinia and Timesketch when deployed on Kubernetes via Helm charts. 1 release · first seen Jun 2024
Helm deployment integration testing Provides an integration test script to validate OSDFIR infrastructure Helm chart deployments. 1 release · first seen Jan 2024

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for osdfir-infrastructure, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail osdfir-infrastructure puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

40 entries

  1. November 20261
  2. September 20261
  3. August 20261
  4. July 20261
  5. June 20261
  6. May 20262
  7. March 20261
  8. February 20263
  9. January 20263
  10. December 20251
  11. November 20252
  12. August 20253
  13. May 20251
  14. April 20252
  15. February 20251
  16. September 20244
  17. June 20245
  18. May 20241
  19. April 20241
  20. March 20242
  21. January 20243
    Show

    40 entries

    Project health

    Issue, contributor and maintainer activity in google/osdfir-infrastructure, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 22% of issues opened, last 12 months
    5. Median time to close 2.2 years first maintainer reply 51 days
    6. Open backlog 6 of 66 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 6
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 33%
    • features 67%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.