Skip to main content

​
At a glance

​
The philosophical difference

Polygres (with its underlying open-source extensions pgGraph and pgContext by Evokoa) makes standard PostgreSQL “AI-native.” It treats your existing relational database tables as the source of truth, building an in-memory graph index over your custom SQL schemas so you can execute multi-hop graph traversals and vector searches directly inside Postgres without moving data. Worlds approaches context with opinionated, interoperable defaults. Instead of requiring you to design, migrate, and maintain custom relational table schemas and SQL join topologies, Worlds enforces standard RDF triples in an append-only chronological ledger, with SPARQL verification out of the box. The tradeoff is do-it-yourself schema design vs. ready-to-use graph context:
  • Polygres is ideal when you want to build graph-style retrieval over your own existing relational schemas and custom Postgres tables (“DIY graph over SQL”).
  • Worlds is just as flexible, but provides opinionated RDF defaults, standards-based SPARQL verification, and portable memory SDKs (memsdk) so you do not have to design a custom graph database schema yourself.

​
When Worlds fits

  • You want W3C open standards (RDF, SPARQL, SHACL) and portable agent memory across databases and model providers.
  • You prefer an opinionated fact ledger out of the box rather than designing custom relational tables and graph indexes.
  • You need chronological provenance tracking for every asserted triple.
  • You are deploying to edge environments (e.g. SQLite/LibSQL via worlds-libsql) where full Postgres infra is unavailable.

​
When Polygres fits

  • You already have an extensive PostgreSQL relational database with custom schemas and want to add graph traversal (pgGraph) over existing tables.
  • You want to keep all operational data and agent retrieval strictly within standard Postgres SQL queries without adopting RDF or SPARQL.
  • Your team prefers constructing and maintaining custom relational schema definitions for agent data.

​
Coexistence

Applications backed by a primary Postgres database can use Polygres for relational operations and Worlds as the SPARQL-driven agent context engine. Authoritative domain facts sync into Worlds, while operational SQL queries run on Polygres.