Statewave
An AI memory solution that builds agent memory on Postgres and pgvector, with support for graph-structured storage.
Timeline (last 90 days)
Statewave uses the Apache-2.0 license, depends on Postgres 14+, pgvector, and Python 3.11+, and provides HMAC-SHA256-signed receipts and a replay endpoint that can reconstruct the four properties of an audit trail.
Statewave has no managed cloud, so you must operate Postgres yourself; it has no entity relationship graph; no multimodal RAG; tenant isolation is at the application layer rather than Postgres row-level security; and server-side CI testing has been done only on Linux.
Statewave organizes memory by subject (user, account, ticket, Agent, or repository), each memory carries a confidence, a validity period, and a source Episode ID, the policy layer uses YAML to define deny and redact rules for sensitive tags, and it outputs a signed receipt for the assembled package.
Statewave's known limitations include: no entity relationship graph or traversal, no managed cloud or cross-region clustering, tenant isolation enforced at the application layer rather than via Postgres row-level security, and server-side CI testing done only on Linux.
Statewave Guide is built on top of Statewave, which is an open-source, self-hosted AI agent memory runtime emphasizing governance and provenance, under the Apache 2.0 license.
All Facts (5)
Statewave uses the Apache-2.0 license, depends on Postgres 14+, pgvector, and Python 3.11+, and provides HMAC-SHA256-signed receipts and a replay endpoint that can reconstruct the four properties of an audit trail.
50%UnverifiedStatewave has no managed cloud, so you must operate Postgres yourself; it has no entity relationship graph; no multimodal RAG; tenant isolation is at the application layer rather than Postgres row-level security; and server-side CI testing has been done only on Linux.
50%UnverifiedStatewave organizes memory by subject (user, account, ticket, Agent, or repository), each memory carries a confidence, a validity period, and a source Episode ID, the policy layer uses YAML to define deny and redact rules for sensitive tags, and it outputs a signed receipt for the assembled package.
50%UnverifiedStatewave's known limitations include: no entity relationship graph or traversal, no managed cloud or cross-region clustering, tenant isolation enforced at the application layer rather than via Postgres row-level security, and server-side CI testing done only on Linux.
50%UnverifiedStatewave Guide is built on top of Statewave, which is an open-source, self-hosted AI agent memory runtime emphasizing governance and provenance, under the Apache 2.0 license.
50%