Bringing Your Own Long-Term Memory Provider
The honest scope of bring-your-own memory in Piskes today: one verified provider, a design built to add more, and no key material the platform can ever show back to you.
"Can I plug my own memory backend into this agent" is a real question, especially for teams that already have an external memory or knowledge layer they trust and don't want to abandon. Piskes's honest answer today is narrower than a full marketplace, and it's worth stating exactly that plainly rather than implying more than currently exists.
What's actually available today
Right now, the one long-term memory provider you can connect is Mem0. That's not an arbitrary first pick — it's the provider whose HTTP contract has actually been verified against its own live API reference. The design behind the memory settings screen is built to read its list of available providers from the platform's own registry on every request, rather than hardcoding a fixed list into the UI — which means the catalogue can grow as more providers get verified, without a client-side release. But today, that registry has one entry.
The honest framing is: Mem0 today, more later, with "later" meaning "once someone has actually checked another provider's API against a real account" — not a promised timeline. If you're evaluating this feature, plan around what's real right now rather than a roadmap.
What you can and can't see once it's connected
Once you've connected a provider, the settings screen has no path to ever display your key material back to you, even by mistake — the route that reads your settings back never selects the encrypted key column in the first place, so there's no code path where a leaked key could show up on screen. You can tell that it's connected; you can't retrieve the credential itself through the UI once it's set. That's a deliberate constraint, not a missing feature — the same instinct behind never displaying a password back to you after you've set it.
What to expect if you're evaluating this
If your team already runs Mem0, connecting it here is real and functional today. If you're hoping to bring a different memory provider, that's not currently possible, and it's worth checking back rather than assuming it'll work because the settings screen is architected to support more providers in principle. The architecture being ready and a specific provider being verified are two different things, and only the first is true for anything beyond Mem0 right now.