Not exactly. DuckDB itself does not have native vector index support; the vector search functionality comes from extensions such as VSS, which use their own index format. Those indexes are managed by DuckDB and are not designed to be shared as standalone artifacts or queried directly from a browser.
ParqDB takes a different approach: the vector index itself is stored in Parquet format. This makes the index a portable dataset that can be published, shared through object storage, and queried directly by clients (including browsers via WASM) without a database server.
ParqDB takes a different approach: the vector index itself is stored in Parquet format. This makes the index a portable dataset that can be published, shared through object storage, and queried directly by clients (including browsers via WASM) without a database server.
More details and examples are available in our GitHub repo: https://github.com/parqdb-io/parqdb