Polygres documentation
Polygres gives your team a managed PostgreSQL database and graph, vector, TSVector full-text, Fuzzy text, and hybrid retrieval over the same data. Use standard PostgreSQL connections for application reads, writes, migrations, and imports. Use the Polygres dashboard or API when you need connected-record exploration, semantic similarity, language-aware keyword search, typo-tolerant lookup, or graph-and-vector hybrid results.
Polygres is designed for SaaS teams that want one operational data store instead of separate database, graph, vector, and text-search systems. PostgreSQL remains the source of truth for your application, including tsvector, pg_trgm, and pgvector-backed retrieval.
Start here
- New to the product? Read What is Polygres?.
- Ready to create a project? Follow the Quickstart.
- Building a shared team workspace? Learn the Key concepts, starting with organizations and roles.
- Deciding how your team and application should connect? See Dashboard, API, and database access.
- Working from a terminal? Use the Polygres CLI for project setup, imports, migrations, and retrieval configuration.
Explore the overview
- What is Polygres?: product fit and capabilities.
- Core workflow: the SaaS journey from account to query.
- Key concepts: organizations, roles, projects, connections, credentials, and retrieval.
- Dashboard, API, and database access: which access method to use for each job.
- Polygres CLI: terminal workflows for projects, credentials, imports, migrations, and retrieval setup.
- Quickstart: the shortest complete setup path.
- Common use cases: concrete patterns for SaaS products and data teams.
Next steps
Platform Guide
CLI
SDK Guide
- Connect and credentials
- Connection examples
- Configure and query retrieval
- Retrieval integration patterns
Reference
Last updated on