Timesketch
Open-source collaborative forensic timeline analysis application.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Helm / Kubernetes operator; Kubernetes manifests; VM image
Runs in
Documented customer environment
Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack.
- Google Cloud: Customer cloud account
- Azure: Customer cloud account
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
OSDFIR Getting Started ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
SecureAnyCloud Azure ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Helm / Kubernetes operator; Kubernetes manifests; VM image |
|---|---|
| Infrastructure | Servers / containers Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The versioned configuration supports trusted web-server REMOTE_USER SSO and separately Google OIDC/Cloud IAP options, with actual token/authentication implementation. Configure the selected mode, trusted proxy boundary, identity claims and group policy; these mechanisms are not interchangeable and must not trust spoofed headers.
Timesketch 20261014 configured user SSO/OIDC/IAP paths · Source ↗ · Google token validation ↗ · Application authentication views ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Google maintains OSDFIR Helm charts with Timesketch values and production installation guidance. Select compatible chart/application/OpenSearch versions, expose ingress deliberately and configure secrets, persistent storage and backups. Local Minikube instructions and default port-forward access are not production deployment.
Maintainer Timesketch Kubernetes/Helm deployment; chart and application versions separate · Deployment artifact ↗ (Current OSDFIR Timesketch chart guide reviewed on this date) · Reviewed 2026-11-21
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The upstream scaling guide gives at least 8 GB RAM for its described Ubuntu environment and stresses fast local storage and OpenSearch sizing/shard limits. This is an entry baseline, not capacity for arbitrary timelines/events or an HA cluster; separately size indexes, imports, workers, replicas and backups.
Timesketch published entry baseline and search-scaling guidance · Source ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Timesketch; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Reviewed upstream 20261014 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.
Timesketch upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
Community & maintenance
The reviewed upstream contributor history includes berggren, kiddinn, jaegeral, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Incident & investigation management
- Open-source collaborative forensic timeline analysis application.
Compare within Incident & investigation management
- ArkCase Enterprise (self-managed)Configurable case management platform with FOIA and investigative solutions.
- AWS
- Darktrace Forensic Acquisition and InvestigationCommercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.
- AWS
- Azure
- Google Cloud
- FormKiQ Incident and Investigation Management Directory PublisherManage document-centric intake, investigation, and resolution of incidents, complaints, and regulatory matters with structured workflows and audit trails.
- AWS
- Sandfly SecurityCommercial self-hosted Linux threat-hunting and investigation platform.
- DigitalOcean
- SAP S/4HANA EHS — Customer-OperatedCustomer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.
- AWS
- Azure
- Google Cloud
- TheHive Self-HostedSelf-hosted security incident-response case management for investigations and analyst collaboration.
- AWS
- Azure
- TinesCommercial self-hosted automation platform with an AWS Fargate deployment guide.
- AWS
- Tracecat Self-HostedOpen-source security-workflow automation with an upstream customer AWS deployment.
- AWS
Showing 8 of 10 other listings in Incident & investigation management. These products address related workflows; read their category-fit notes before comparing scope. See all of Incident & investigation management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- OSDFIR Getting Started ↗google.github.io
- SecureAnyCloud Azure ↗secureanycloud.com
- OSDFIR Timesketch ↗google.github.io
- Apache-2.0 ↗github.com
- Releases ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- OSDFIR Getting Started ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
- SecureAnyCloud Azure ↗ · Azure
Third party package · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
- OSDFIR Getting Started ↗ · Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com