Glass half empty then.

Most vector databases are using some local or external provider to get the embeddings and then using some storage engine to store and retreive the embeddings. Whether it's pgvector leaning on postgresql, or chromadb on sqlite, or pinecone originally being on rocksdb (I believe they've now built their own engine).

This is no different, and is still in it's infancy, so one presumes they might add support for other methods of getting the embeddings much as chromadb has.