Statewave

Open-source memory runtime for production AI agents.

5.0•15 reviews•

88 followers

Open-source memory runtime for production AI agents.

5.0•15 reviews•

88 followers

Visit website

Open-source memory runtime for AI agents. Durable, structured context with provenance, self-hosted on Postgres.

Statewave Reviews

Name: Statewave
Rating: 5.0 (15 reviews)

The community submitted 15 reviews to tell us what they like about Statewave, what Statewave can do better, and more.

5.0

Based on 15 reviews

Review Statewave?

Reviewers consistently praise Statewave for being fast to set up, easy to self-host, and unusually strong on governance: they repeatedly mention clear provenance, tenant isolation, access controls, audit trails, and visibility into what is remembered. Users say it helps multi-agent, coding, and workflow setups keep context, decisions, and architecture preferences across sessions, saving time and keeping sensitive data private. The main criticism is maturity around adoption: reviewers want better end-to-end docs, more real examples, a richer admin dashboard, more integrations, and a cloud-hosted option for teams.

Summarized with AI

Agent Builder by AirtopWeb agents that heal themselves.

Promoted

Reviews

Most Informative

Founder Reviews

Other Reviews (15)

•3 reviews

What's great

Dead simple to set up. One command and it's running. No painful config, just works. Self-hosted, you own your data, governance is actually there. Free and open source too.

What needs improvement

Docs could use more real examples

vs Alternatives

Most memory stuff is just vector stores. I needed something where you can actually see what's being remembered and control who accesses it.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

109 views2mo ago

Thanks Sid — "one command and it's running" was exactly the bar we set, so glad it held. And you're right on the docs: more real, end-to-end examples is genuinely near the top of our list. If there's a specific workflow you were setting up, tell us — we'll prioritize that one first.

Report

2mo ago

•33 reviews

What's great

Found Statewave while looking for a memory solution for a multi-agent setup I was building. Most of what I tried either used vector stores with zero visibility into what's actually being remembered, or required me to build the whole governance layer myself. Statewave was running in under 5 minutes, self-hosted on Postgres, and the provenance tracking was there out of the box, not something I had to wire up manually.

The thing that actually stuck with me was how clean the access control is. I'm working across a few different projects with different sensitivity levels, and being able to set tenant isolation without fighting the tool to do it is genuinely rare. Context persisting properly between sessions has already saved a noticeable amount of time, no more re-explaining architecture decisions every time a new conversation starts.

What needs improvement

Docs need more end-to-end examples for real use cases, not just basic setup. The admin dashboard is functional but pretty minimal right now, more visibility into what's stored and who's accessing what would help a lot, especially for team use. A cloud-hosted option for teams that want shared memory without managing their own infra would also be a big unlock.

vs Alternatives

Tried a couple of managed memory services before this. The permission models were weird and opaque, and I didn't love the idea of sensitive project context sitting on someone else's infrastructure. Vector stores were the other option but they don't track decisions or preserve the kind of structured context I needed. Building it from scratch was on the table for about a day before I decided it wasn't worth the months it would take.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

27 views1mo ago

This might be the most useful review we've had all day — thank you, Nolan. You've put your finger on exactly the hard parts: tenant isolation across projects with different sensitivity levels was one of the trickiest things to get clean, so hearing it held up in a real multi-agent build means a lot.

And your improvement list is spot-on — more end-to-end doc examples, deeper visibility in the admin dashboard for team use, and a shared/hosted option so teams don't run their own infra. All three are exactly where we're heading. If you're open to it, I'd genuinely like to hear more about your multi-project setup as we build those out — that's the feedback that shapes them right.

Report

1mo ago

•3 reviews

What's great

Using it for a multi-session coding agent. Tech stack, decisions, architecture preferences actually persist between conversations. No more explaining context every session. Self-hosted so code stays private.

vs Alternatives

Vector stores don't track decisions or preserve project context properly. Building memory manually was too much work.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

53 views2mo ago

Love this — the multi-session coding-agent case is one of our favorites: tech stack, decisions and architecture choices persisting so you stop re-explaining context every session, and self-hosted so the code stays private. "Building memory manually was too much work" is basically why Statewave exists.

Thanks for both the review and the hosted-version question earlier — you're clearly putting it through real use, which is exactly the feedback we want. If anything comes up as the project grows, we're around.

Report

2mo ago

•2 reviews

What's great

Statewave gives AI agents reliable, persistent memory with clear provenance. It is open-source, self-hosted, and easy to integrate with different AI frameworks.

What needs improvement

More integrations, beginner-friendly examples, and a more advanced admin dashboard would make it even easier to adopt.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

73 views2mo ago

Thanks 🙏 Provenance + framework-neutral was the core bet, glad it lands. Your improvement list is spot-on and honestly matches our roadmap: more connectors and beginner-friendly examples are actively in progress, and the admin console is getting deeper. If there's one integration you'd want first, tell us — it helps us prioritize.

Report

2mo ago

•1 review

What's great

Integrated it with Slack and n8n workflows. Team context actually builds up instead of resetting. Access controls mean sensitive discussions stay private. Audit trail is real.

vs Alternatives

Managed services had weird permission models. Needed something self-hosted and open source.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

63 views2mo ago

This is exactly the use case we built for, thanks Parv. "Team context builds up instead of resetting" + access controls keeping sensitive threads private is the whole point. And yeah — the weird permission models in managed services were a big part of why we went self-hosted and open. Would love to hear how the n8n side holds up as you scale it.

Report

2mo ago

•1 review

What's great

Query-scoped isolation per tenant, policies enforced, audit receipts signed. Exactly what production needs. Free to run, open source, no vendor lock-in.

vs Alternatives

Vector stores don't handle multi-tenant governance. Building it myself was going to take months.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

41 views2mo ago

This is a great use case to hear, thanks Mayur. Multi-tenant governance — query-scoped isolation, enforced policies, signed receipts — is exactly the gap vector stores leave you to build yourself, and yeah, that's easily a months-long project. Noticed the 4/5 on ease of use: if there was a rough edge getting the multi-tenant setup going, tell us — that's precisely the kind of thing we want to smooth out.

Report

2mo ago

•1 review

What's great

Got it running in like 2 minutes. No setup headaches. Works with Claude, Cursor, all the tools I already use. Governance layer is clean and doesn't slow things down.

vs Alternatives

Needed agent memory that actually tracks provenance. Everything else either doesn't care where memories come from or makes you manage it manually.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

71 views2mo ago

"Running in 2 minutes, works with the tools you already use, and governance that doesn't slow things down" — that's the exact bar we set, so this means a lot. Provenance as a first-class thing (not bolted on) was non-negotiable for us. Thanks for giving it a real run 🙏

Report

2mo ago

•2 reviews

What's great

Statewave is useful in that it provides structured memory management through origins, ownership, lifecycle and governance, allowing AI memory to be kept systematic, traceable, and stable over time.

vs Alternatives

The reason I chose Statewave is that it provides a free, easy-to-use platform that allows for high customization even at the source code level.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

94 views2mo ago

Thanks Yanfeng 🙏 Source-level customization was a deliberate call — governance you can't inspect isn't really governance. Appreciate you calling out the origins/ownership/lifecycle framing; that's exactly how we think about it. If you ever hit something you'd want to extend or a missing hook, we'd love to hear it.

Report

2mo ago

•2 reviews

What's great

I’m using this self-hosted with VS Code. I was able to set it up quickly and easily with a single command, following the prompts as I went.

What needs improvement

It would be great to have a cloud-hosted option with similarly simple setup, so the memory store can be shared with other team members.

vs Alternatives

Being able to manage and view the memory store in action is a real advantage over the alternatives.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

30 views1mo ago

Thanks Long 🙏 Single-command setup with VS Code is exactly the experience we were aiming for, glad it held up. And you've landed on a theme we're hearing a lot today: a hosted option with the same simple setup so a whole team can share one memory store. It's on the roadmap — self-hosted stays first-class, but a managed/shared option is coming for exactly this team use case. Also really appreciate the "manage and view the memory store in action" point — that visibility is a core design goal, not an afterthought.

Report

1mo ago