Fig

Name: Fig
Brand: Fig

AI Native

Don't break for a change.

Est 2025|Valuation $51.7M|Raised $38M|3 Ref Customers

LinkedIn 7K|Website|FTEs 25|HQ Israel

01Competitive Landscape

Narrative analysis

Fig versus Cribl: Cribl is oriented toward ensuring the right telemetry reaches downstream systems efficiently; Fig describes a focus on whether detections and responses continue to trigger correctly as upstream changes occur. Some buyers may address detection continuity through data engineering and testing processes, rather than introducing a separate resilience layer.
Fig versus Splunk: Splunk can be the system of record for detections and automation, but customers commonly report data quality and pipeline-change issues. Fig’s described capability to trace from detections back to data lineage is intended as an overlay that can operate alongside a SIEM such as Splunk.

- Fig versus Cribl: Cribl is oriented toward ensuring the right telemetry reaches downstream systems efficiently; Fig describes a focus on whether detections and responses continue to trigger correctly as upstream changes occur. Some buyers may address detection continuity through data engineering and testing processes, rather than introducing a separate resilience layer. - Fig versus Splunk: Splunk can be the system of record for detections and automation, but customers commonly report data quality and pipeline-change issues. Fig’s described capability to trace from detections back to data lineage is intended as an overlay that can operate alongside a SIEM such as Splunk.

Adoption trends

Fig is early-stage, with a recent public launch and limited public review coverage at the time of this research.

	Fig (Resilience for detection/response flows)	Cribl (Telemetry pipeline)	Splunk ES + Splunk SOAR (SIEM + SOAR suite)
Starting Price	Not public (demo/contact sales)	Free offering and paid tiers; pricing details available through vendor	Typically contact sales; some marketplace references exist
Best For	SOCs seeking tools to detect interruptions in detection/response flows during change	Teams focused on routing, transforms, and cost control for telemetry ingestion	Organizations standardizing on Splunk for SIEM + automation with mature Splunk operations
Key Strength	Focus on tracing detections back to upstream data and modeling change impact	Strong control of telemetry plumbing, widely used for ingestion normalization	Broad ecosystem and feature breadth for SIEM and SOAR use cases
Key Weakness	Limited public proof points and a limited third-party review footprint; security/compliance posture not clearly documented publicly	Does not provide end-to-end detection health validation; addresses the plumbing layer	Can be expensive and operationally complex; ingestion economics are a common concern

Fig

01Competitive Landscape

Narrative analysis

Adoption trends

02Market Map

01Competitive Landscape

Narrative analysis

Adoption trends

02Market Map