{"id":"2081034217547301087","url":"https://x.com/daleverett/status/2081034217547301087","text":"","author":{"name":"dale","username":"daleverett","avatarUrl":"https://pbs.twimg.com/profile_images/2049549782755205121/y6qaHyA-_200x200.jpg"},"createdAt":"Sat Jul 25 15:09:55 +0000 2026","engagement":{"replies":5,"retweets":14,"likes":63,"views":12261},"article":{"title":"One open source retrieval layer across your data. Built for agents.","previewText":"Built for agents, not keyword search. Every AI demo works beautifully until you connect it to real company data. Then everything breaks. So we do what the industry always does: we add more","coverImageUrl":"https://pbs.twimg.com/media/HOER6CibwAAVGdp.jpg","content":"Built for agents, not keyword search. Every AI demo works beautifully until you connect it to real company data. Then everything breaks. So we do what the industry always does: we add more infrastructure.\n\nBefore long, the “simple AI feature” has become a distributed systems project. We think this is backwards.\n\n> Agents do not need another copy of your data. They need a reliable way to retrieve reality. That is why we are building Polygres.\n\n## Polygres is one retrieval surface for agents\n\n![](https://pbs.twimg.com/media/HOETnkdbEAA-RKQ.jpg)\n\nPolygres brings relational, graph, vector and text retrieval together around the same operational data.\n\nPostgreSQL remains the source of truth. Your application continues using normal database connections for reads and writes. Polygres adds graph traversal, vector similarity, full-text search, fuzzy matching and graph-plus-vector retrieval over those records.\n\nThat means the data your agent retrieves can be the same data your application just wrote.\n\n- No waiting for an indexing pipeline.\n\n- No separate graph copy.\n\n- No detached vector store slowly drifting away from the source.\n\nAn agent can start with a semantic match, follow the relationships around that result, apply structured filters and receive a ranked set of records with their surrounding context. Polygres exposes these retrieval patterns through our API and Python SDK.\n\n[[Sign up for a free polygres account here →]](https://polygres.com/)\n\n## Why we call it Elasticsearch for the AI era\n\nA similar change in the industry is about to happen again.\n\n- Elasticsearch gave developers a common way to retrieve information for human-facing search.\n\n- The AI era needs a common way to retrieve context for machine agents.\n\n![](https://pbs.twimg.com/media/HOEXch7bkAAE9pw.jpg)\n\n## It needs a layer designed for software that does not just search, but investigates, decides and acts.\n\nThat is what we believe Polygres can become.\n\n> Elasticsearch for the AI era.\n\nOne retrieval layer across your data. Built for agents.\n\n[[Sign up for a free polygres account here →]](https://polygres.com/)"}}