Private telemetry lake

Logs and telemetry are operational assets.
Put them to work with your AI agents.

People read dashboards because the logs were too large to trace. Agents follow the log and act. FFWD keeps that memory searchable, with anomaly intelligence, inside your environment.

Fast Operational speed. Long-term immutable history.

2 storage paths.
1 telemetry strategy.

Keep recent data you need investigating close at hand. Extend your telemetry history into open tables on object storage you own and control.

Quiver Lake

Short-term · Parquet · Arrow · in memory

A Parquet store with in-memory Apache Arrow search. Telemetry is immutable and time-indexed, so ingestion stays fast and schema is applied when you query.

  • Logs are the common format, structured or not
  • High-cardinality metrics, without the usual bottleneck
  • PromQL and SQL for other systems. Agents use MCP
Inside Quiver Lake

Long-term Data Lake

Apache Iceberg + your object storage

Extend retention into open Iceberg tables, with catalog integration to make historical telemetry discoverable and queryable.

  • Bring your own object storage
  • Keep history in open table formats
  • Explore retained telemetry with SQL and agents
Explore the long-term lake
Quiver Lake · Rust

Logs are heavy.
Quiver is built for them.

People left logs for dashboards because the volume was too much to trace. Agents are good at exactly that trace, and a metric value does not give them an action. Logs land here as Parquet and are searched in memory with Apache Arrow.

Logs first, structured or not

Logs are the common format. Structured or raw, if they are time-indexed they ingest fast. Quiver is tuned for that path, not for a general database.

High cardinality, not a bottleneck

Typical time-series stores slow down as metric cardinality grows. Quiver does not. Log search stays in memory, in Apache Arrow, and anomaly detection runs on those logs.

Explore anomaly intelligence →

MCP for agents. APIs for everyone else

Agents reach the logs through MCP. PromQL and SQL stay open for third parties, such as a Grafana dashboard or another system, to query the same store directly.

Iceberg · Rust

The memory of your infrastructure.
Query it immediately.

Long-term telemetry is written as Iceberg tables on object storage you own. FFWD hosts the Iceberg catalog in Rust, the same stack as Quiver, so those tables are open to an external query engine as soon as they are stored.

01 / WRITE

Many buckets. Many tables.

The Iceberg connector writes tables to object storage. Use more than one destination, and more than one table in each bucket, so retention matches how you want the history kept.

02 / CATALOG

A catalog, hosted in FFWD

Iceberg catalog runs inside FFWD, in Rust. It serves the catalog for external queries, so the tables on object storage are discoverable rather than files sitting in a bucket.

03 / QUERY

No rehydrate. No ETL.

Logs dumped as files have to be pulled back out and transformed before anyone can analyse them. Iceberg tables are already tables. Bring a query engine and the history is ready.

The foundation for agentic operations

Give agents logs
they can actually use.

Agents cannot work through terabytes of raw logs. FFWD filters that down to a signal, keeps the recent evidence fast in Quiver, and leaves the older history queryable in Iceberg. Agents reach both through MCP.

INVESTIGATE NOW

“What changed before this service started failing?”

Search the logs already in fast storage, with anomaly evidence beside them. The useful signal, not the raw lake.

LOOK BACK

“Have we seen this pattern before?”

Older logs are Iceberg tables, not files waiting to be rehydrated. Bring a query engine and the history is ready.

RECOVER FASTER

“Where is the cause, and can we act?”

The agent traces the logs through MCP and gets to the cause sooner. Time to recovery gets shorter.

Explore agent assurance →

FFWD by core0

Let’s talk

Tell us what you need — or email us at

What are you interested in?

We’ll reply by email — usually within one business day.