Postgres plus retrieval primitives
Polygres combines PostgreSQL hosting with native graph traversal, HNSW vector search, and hybrid retrieval APIs so relational, semantic, and structural queries can run against the same data source.
Polygres
Polygres is a Postgres platform for AI agents that combines hosting with graph traversal, HNSW vector search, and hybrid retrieval APIs. It helps teams turn relational data into queryable working memory for agent workflows.
Postgres for the agent era
Polygres is a Postgres platform for AI agents that combines database hosting with graph traversal, vector search, and hybrid retrieval APIs. Its core pitch is to make rows, relationships, and embeddings queryable together, so an agent can retrieve grounded context from the database instead of relying on prompt stuffing.
The product is organized around two retrieval layers described on the homepage as pgGraph and pgContext. pgGraph turns existing foreign keys into graph traversal for multi-hop relationship search, while pgContext runs multiple search methods in parallel and fuses the results into a single ranked answer. The output is presented as a token-ready context block that can be passed into an agent workflow.
The site also shows supporting surfaces around the core platform: a public retrieval playground for user memories and Wikipedia, and Polygres Pocket, a separate CLI-oriented package that folds codebases, files, and memories into a queryable context window for agents. The pricing page offers a free self-hosted option and managed cloud plans for users who want hosted infrastructure.
Core capabilities
Graph traversal over relational data
The homepage describes pgGraph as graph retrieval over existing foreign keys, with multi-hop traversal, shortest paths, and relationship search over the tables you already have.
Hybrid retrieval fusion
The homepage describes pgContext as fused search that runs multiple search methods at once and merges the results into one ranked list.
Context assembly for agents
The product returns a token-ready context block for agents, assembling rows, paths, and matches into a single result that can be passed to an LLM or agent workflow.
Managed or existing-schema workflow
The site positions the product as usable with an existing schema or as a managed instance, and the Pocket page shows an MCP-style workflow for connecting agent tools.
Inspectable demo controls
The user demo pages expose retrieval controls for graph depth, semantic, lexical, and graph weighting, plus answer synthesis settings in the interface.
Where it fits
Agent memory over relational data
Use Polygres when an agent needs to follow foreign-key relationships, look up related records, and return a grounded answer in one request. The product is designed to turn relational data into traversable memory.
Retrieval evaluation and prototyping
Use the public playground style workflows to inspect how semantic, keyword, and graph signals are fused for a specific query. The demo pages make the retrieval process visible for evaluation and experimentation.
Hybrid search over live tables
Use Polygres when your application needs to combine vector similarity with graph expansion and typed filters without building separate systems. The homepage shows a single query path that merges these signals into one ranked list.
Agent coding and codebase recall
Use the Pocket workflow when you want a CLI-mediated context store for codebases, files, and memories that can be attached to an agent through MCP. The product page frames it as a way to give coding agents a larger working memory.
Hosted or self-managed deployment
Use the managed cloud if you want hosted PostgreSQL infrastructure, or self-host if you already have a Postgres instance and want to run the open-source components yourself.
Pros and Cons
Pros
- Combines relational storage, graph traversal, and vector search in one Postgres-centered platform.
- Supports hybrid retrieval that can fuse semantic, lexical, graph, and filtered signals into one ranked response.
- Returns token-ready context for agent workflows instead of separate search outputs.
- Offers both a free self-hosted path and managed cloud pricing.
- Includes public demos that make the retrieval model visible before deployment.
Cons
- The public demo pages are rate-limited, so they are not a substitute for benchmarking the platform under your own workload.
- Some managed cloud tiers are marked as coming soon, so the pricing page does not present a fully mature hosted lineup yet.
- The source material leaves integration details and supported environments partly unspecified, so buyers will need the docs for implementation fit.
FAQ
What is Polygres?
Polygres is a Postgres-based database platform that combines managed hosting with native graph traversal, HNSW vector search, and hybrid retrieval APIs. It is positioned for agents that need relational, graph, and semantic retrieval from the same database.
Does Polygres have both self-hosted and managed options?
The source shows managed cloud options, a free self-hosted path, and an open-source workflow. The pricing page also says Polygres is currently looking for design partners.
How does retrieval work in Polygres?
The homepage shows retrieval flows that combine graph hops, semantic search, lexical search, filters, and token-ready context assembly. The user demo pages also show a public playground with adjustable retrieval controls.
Is there a free way to use Polygres?
The site mentions that you can start free, and that the managed cloud has a free Launch plan plus paid Scale and enterprise options marked coming soon. The pricing page also offers a $0 forever self-hosted option.
Are the public demos production benchmarks?
The public demo pages note that queries are rate-limited to prevent abuse, so responses may be slightly slower. They also say the point of the demo is to show how Polygres works, not to provide full performance benchmarks.
Quick Facts
- Category
- Database platform
- Primary use
- Agent retrieval and context assembly
- Core technologies
- PostgreSQL, graph traversal, HNSW vector search, hybrid retrieval
- Deployment
- Self-hosted and managed cloud
- Source domain
- polygres.com
- Pricing signal
- Free self-hosted option plus managed plans
Alternatives à Polygres
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
Lasso
Lasso is an ecommerce product data platform for enriching catalog records, processing supplier files, generating product content, and monitoring competitors. It combines a web app with a REST API, SDK, and MCP server for teams and developers.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
hob
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.
Ably Chat
Ably Chat is a chat API platform for building custom realtime chat applications. It supports room-based messaging, typing indicators, presence, reactions, and message updates, with usage-based pricing options for different deployment stages.
Botacts
Botacts is a web directory for finding AI bots and agents you can contact by phone, email, SMS, WhatsApp, Telegram, or Signal. It also lets creators suggest bots for manual review before publication.