# Roadmap

<Callout type="info">
This page gives a concise view of direction. It is not an implementation plan,
release checklist, or API commitment.
</Callout>

## Current Baseline

pgGraph supports PostgreSQL 14 through 18 and keeps registered PostgreSQL rows
authoritative. The current code provides bounded graph registration,
projections, traversal, paths, selected analytics, supported GQL and Cypher
profiles, mutable synchronization, persisted rebuildable artifacts, resource
governance, and caller-scoped security behavior.

Exact current surfaces are documented in the
[SQL Profile](/user_guide/sql-profile),
[GQL Profile](/user_guide/gql-profile),
[Known Issues](/known-issues), and
[Release Notes](/release-notes).

PostgreSQL [removed SQL/PGQ from its PostgreSQL 19 release branch](https://github.com/postgres/postgres/commit/2b9e1aff4d3d933ae8ee377fef22c2af9c7797e8)
on September 7, 2026. PostgreSQL-version compatibility and future native
SQL/PGQ integration are independent directions. No target major is committed
for native integration, and pgGraph does not depend on SQL/PGQ.

## Direction

Future releases may improve these broad areas:

- selective-visibility scale evidence and adaptive execution. Adaptive execution
  must reuse known verdicts when completing an eager scope and may never restart
  policy work from zero;
- bounded path, traversal, query-language, and analytics coverage;
- set-based ingestion ergonomics over authoritative PostgreSQL tables;
- synchronization, persistence, recovery, and resource governance;
- reusable topology primitives for optional external consumers;
- PostgreSQL-version, packaging, conformance, and performance coverage.

These directions do not promise a particular API, order, version, or date. A
capability is shipped only when implementation, tests, public profiles,
limitations, and release notes agree.