Today we are announcing vector search in Onehouse Lakegres, with a native index stored inside existing and new open tables. You can search embeddings through a Postgres endpoint on the same tables you already have in your data lake. The index and data are managed in open formats in your own bucket.
A few years ago, adding vector search required a separate database. Postgres now has pgvector, OpenSearch has k-NN, and MySQL, Oracle, MongoDB and SQL Server have their own implementations. Databricks also offers vector search in Lakebase Search. Similarity search has become a standard index type for application data.
Most of the data an agent needs to query is in the lakehouse. Support transcripts, logs, documents, product catalogs and years of event history are stored in open tables on object storage. These datasets are 100 to 1,000 times larger than a typical Postgres instance. To search them with any of those databases, you have to copy the data into the database first. Copying lake-scale datasets into a relational database just to search their vectors is an absurd requirement. You end up paying to store the data twice and operating a pipeline to keep the copies in sync.





