Data sediment analytics

Find the fingerprints systems keep.

Every system leaves sediment: logs, traces, events, and the cold data everyone else discards. faex reads those layers, reconstructs what happened, and surfaces the signal that settled underneath the noise.

Platform

Turn exhaust into evidence.

Four layers of analysis over the data your systems were already producing.

🌊

Log & Trace Analysis

Ingest high-volume logs, traces, and events; parse and structure them without pre-defining every schema.

OpenTelemetry · streaming
🔎

Data Forensics

Reconstruct incidents from what the system left behind: timelines, lineage, and root cause from residue.

Timeline · lineage graph
📈

Signal Extraction

Separate anomalies from noise across billions of events with statistical and ML-based detection.

Anomaly · correlation
🗄️

Cold Strata

Query archived, low-cost storage layers directly, with no rehydration and no data left unexamined.

Columnar · time-partitioned
How it works

Ingest, settle, surface.

The same way sediment records time: layer by layer, oldest at the bottom, all of it queryable.

01

Ingest

Point your log, trace, and event streams at faex. No schema up front, no data dropped on the floor.

02

Settle

Data is layered and time-partitioned into cheap columnar strata, hot and cold, all still addressable.

03

Analyze

Query across every layer, run forensics, and let detection surface the anomalies worth your attention.

04

Surface

The signal that settled underneath: root causes, patterns, and answers, delivered to the people who need it.

Who it's for

Teams that can't afford to discard the record.

Wherever the answer is hiding in data everyone else archives and forgets.

Platform & SRE Security & incident response Observability teams FinOps Data engineering Fraud & risk Compliance & audit ML / analytics
PB
Scale per deployment
<1s
Query across cold strata
90%
Lower retention cost
0
Events dropped
Why the name

faex is Latin for sediment.

Sediment is what settles when everything else has moved on, and it's where the record is kept. Your systems produce the same thing: exhaust data that piles up, gets archived, and is written off as cost. We think that's backwards. The sediment is the archive: a stratified, timestamped record of everything your infrastructure has ever done. faex is built to read it.

See what's at the bottom.

Point faex at a week of your logs and we'll show you the signal you've been archiving away.

Book a demo