Right now it's more for data analysts who's data eng team doesn't have the capacity to support all types of data processing requirements. Data analysts can just do it themselves simply with SQL! But we are also open to explore the opportunities for the data eng teams if we see a strong use case of automating their data pipelines.

Great question! The answer is two fold: 1. Not like a vector database, in addition to searching, VolansDB also store the files (pointers) directly in the table. So you are able to manage files (RBAC etc.) as table cells, apply batch data processing jobs easily with SQL, and even unstructured data lineage & pipeline. 2. VolansDB is columnar so it's optimized for analytical use cases rather than for product DB access patterns.