Floecat

Metadata Control Plane

Planner-ready metadata for Iceberg and Delta

Built for data platform engineers and query engine teams that need consistent metadata semantics across catalogs, clouds, and engines.

Developed by FloeDB.

Run Local Stack Read Docs

Why teams use Floecat

Install by environment

cd docker
FLOECAT_ENV_FILE=./env.localstack COMPOSE_PROFILES=localstack,trino \
  docker compose -f docker-compose.yml up -d --wait

git clone https://github.com/eng-floe/floecat.git
cd floecat
make run

cd docker
FLOECAT_ENV_FILE=./env.localstack docker compose -f docker-compose.yml run --rm cli

duckdb -init tools/duckdb-localstack-init.sql
SELECT * FROM iceberg_floecat.iceberg.orders;

Built for your stack

Try it now

The problem this solves

Open table formats solved storage interoperability, but not planner-ready statistics, cross-catalog semantics, or cross-engine consistency.

Floecat is built for metadata consumption, not mutation: it gives engines a stable metadata layer instead of making each engine rebuild catalog logic.

Quickstart

Clone, start the service, and open the CLI:

git clone https://github.com/eng-floe/floecat.git
cd floecat
make run
make cli-run

Then point Floecat at an Iceberg or Delta catalog and query through its APIs or from engines like DuckDB and Trino.

Contact and contribute

Recent Posts