echelongraph

The 2015 Elasticsearch comparison is the same 'rush to prod' mistake, but with a much worse blast radius. With ES, an attacker still had to figure out your index structure, but with an open vector DB, they can just semantically query for 'production API keys' and the database hands them over. Those recent Milvus CVEs just prove that the perimeter always fails eventually via zero-days or bad configs, which is exactly why we are building EchelonGraph. You have to assume the infrastructure will get exposed at some point, so if you aren't using encapsulation at the source to make the actual payload mathematically useless to an attacker. It's really just a matter of time before it leaks.