VXLake
A data lakehouse that ingests from many connectors into versioned tables, with schema evolution, time-travel, and per-table access control.
What VXLake does.
Many connectors
Ingest from Postgres and pgCDC, MySQL, MongoDB, S3 and VXS3 watch, webhook, VXQueue, and VeexaDB.
Versioned tables
Write to versioned tables so every change is tracked and reproducible.
Schema evolution
Adapt table schemas over time as source data changes.
Time-travel queries
Query tables as of a point in time with query-at for historical views.
Compaction and catalog
Compact table files for efficient reads and organize datasets in a catalog.
Per-table RBAC
Control who can read and write each table with per-table role-based access.
Where teams use it.
- Consolidate operational databases into a governed lakehouse
- Capture change data from Postgres, MySQL, and MongoDB
- Reproduce historical state with time-travel queries
Part of the Veeexa platform.
VXLake shares one identity (VXAuth), one bill (VXBilling), and one API surface with the rest of Veeexa. Adopt it alone, or alongside the services below.
VXQueue
A Kafka-style message queue and broker for high-throughput event streaming, with topics, partitions, and durable produce and consume APIs.
SQL QUERYVXQuery
A DuckDB-backed federated SQL service that queries object-store data in place across S3 and VXS3 sources without moving it first.
LOG PLATFORMVXLogStream
A cloud-native, multi-tenant log aggregation platform for ingesting, storing, indexing, and querying logs with built-in governance.