Question 1

What is Kolmos?

Accepted Answer

Kolmos is a cloud database engine built for PostgreSQL, MySQL, and MongoDB workloads. It combines self-compressing storage, columnar architecture, and multi-wire compatibility to reduce database storage and cloud infrastructure costs.

Question 2

Which database wire protocols does Kolmos support?

Accepted Answer

Kolmos natively supports PostgreSQL (port 5432), MySQL (port 3306), and MongoDB (port 27017) wire protocols. Standard drivers, ORMs (Prisma, Drizzle, SQLAlchemy, Hibernate), and database clients connect seamlessly with zero application code changes.

Question 3

How does Kolmos reduce cloud database storage costs?

Accepted Answer

Kolmos uses an autonomous Explanation Ladder that mines Minimum Description Length (MDL) formulas and prototype clusters to compress data 1.66×–2.12× smaller than Parquet-zstd. It stores files directly on Cloudflare R2 object storage ($0.015/GB/mo) with zero data egress fees, cutting overall cloud database storage bills by 10× to 40×.

Question 4

Is Kolmos data recovery 100% lossless?

Accepted Answer

Yes. Kolmos guarantees 100% mathematical fidelity via Invariant #1: decode(encode(x)) == x across all SQL and BSON data types. Every row decodes bit-perfectly with zero precision drift.

Question 5

How does Kolmos execute fast analytical queries on cloud object storage?

Accepted Answer

Kolmos embeds min/max statistics and Bloom filters into segment headers. Using Apache DataFusion vectorized execution and predicate pushdown, the engine prunes irrelevant segments and streams zero-copy Apache Arrow memory buffers without downloading unneeded data.

Question 6

What prevents vendor lock-in with Kolmos storage formats?

Accepted Answer

Every Kolmos segment footer pins an open, self-contained WASM decoder covenant executed in an isolated Wasmtime sandbox. This guarantees your database files remain readable perpetually decades later without requiring proprietary server runtimes.

Databases should
explain themselves.

Welcome back

Databases should explain themselves.

Welcome back

Databases should
explain themselves.