Agent memory means customer conversations, internal documents, and reasoning traces land in a third-party service. That's a data-governance question before it's a technical one.
Enterprise · Security · Governance
Agent memory your security team can sign off on.
Jennah keeps everything an agent remembers in one externally consistent store - so there is one tenant boundary to secure, one snapshot to audit, and one operation that proves a deletion actually happened.
Jennah is in early access. This page is explicit about what ships today and what does not - including the certifications we don't hold.
Why agent memory stalls in security review
Developers evaluate agent memory on ergonomics and latency. The people who approve it evaluate something else entirely - and a stack of three stitched databases answers them badly.
When an agent takes a costly action, someone has to reconstruct what it knew at that instant. Logs in one system and embeddings in another can't be replayed together.
An erasure request has to reach execution logs, embeddings, and graph edges. Spread across three stores, deletion is a best-effort script - not a guarantee you can attest to.
A vector database, a graph database, and an app database each carry their own access model, encryption posture, and audit trail. Every one gets reviewed separately.
What ships today
Available now in the memory layer, running on live infrastructure. Everything in this section is built - the roadmap has its own section below.
Atomic erasure
AvailableDelete an agent and everything it remembered vanishes in one atomic operation - execution logs, embeddings, and graph edges together, never a partial deletion - returning the instant it committed. One transaction is what an erasure process needs to attest to.
Time-travel audit
AvailableRead an agent's complete memory exactly as it stood at any past instant - logs, vectors, and graph on a single snapshot. You reconstruct what the agent knew when it acted, not what the store looks like now.
One tenant boundary
AvailableEvery read and write is clamped to the enterprise on your credential, server-side, inside the query itself - including graph traversals, which are generated by us rather than accepted as caller-supplied query text. It's an enforced invariant with tests that fail if an unclamped statement can ever be emitted, not an application convention.
Roles and permissions
AvailableRole-based access control with custom roles, so operators, engineers, and auditors get different reach into the same enterprise. Membership is many-to-many: one person can hold different roles in different enterprises.
Revocable machine credentials
AvailableEnterprise-scoped API keys for agents and CI: minted by an admin, shown once, stored only as a hash, with optional expiry and instant revocation. Per-key fine-grained scopes are on the roadmap, not shipped.
Region pinning and residency
AvailableEach agent's memory is pinned to a home region and served from the nearest data plane - a single region, one geography, or global. Where data lives is a deployment choice you make, not a side effect of how we scaled.
One backend instead of three
Most teams assemble agent memory from a vector database, a graph database, and a relational store, then write glue to keep them in sync. Jennah is one store for all of it - which changes the cost structure and the review surface at the same time.
One store to provision, upgrade, back up, monitor, and capacity-plan - instead of three, each with its own failure modes and on-call surface.
One access model, one encryption posture, one set of credentials and network paths. Your security team reviews a single system, once.
Logs, embeddings, and graph edges commit in one transaction and are readable the instant it lands. There's no window where an agent's graph disagrees with its vectors.
We won't quote you a savings percentage from someone else's deployment. The saving here is structural; what it's worth is a figure from your own bill and your own headcount, and we'll help you build it from your workloads.
On the roadmap - talk to us
The standard enterprise checklist, and where we honestly are on each item.
Nothing in this section is available today. It's here so you can see the plan, weigh it against your own timeline before we take up your security team's week, and tell us what to prioritise. Design partners have real influence over this order.
Dedicated single-tenant instances
DesignedA private database or instance rather than a shared multi-tenant one, with its own region, capacity, lifecycle, and embedding model. Designed and specified; not yet built. Today every tenant shares a multi-tenant database with row-level isolation.
SSO / SAML 2.0
PlannedOkta, Microsoft Entra ID, and other SAML identity providers, with SCIM provisioning to follow. Today sign-in is social OAuth login for people and enterprise-scoped API keys for workloads.
Exportable audit log
PlannedAdministrative and access events exported or streamed to your SIEM. Today an agent's own execution history is queryable and time-travellable through the API, but control-plane audit export isn't built.
Customer-managed keys
PlannedCMEK on the underlying managed database, so key rotation and revocation sit with you. Today data is encrypted at rest and in transit with provider-managed keys.
Fine-grained key scopes
PlannedRead-only keys, and keys scoped to an environment or a subset of agents, so a production credential can't be used against staging. Today a key is enterprise-scoped and member-equivalent.
Compliance program
Not startedWe hold no certifications today - no SOC 2, no ISO 27001, no HIPAA attestation - and we won't imply otherwise with a badge strip. If a specific certification gates your purchase, tell us which one and by when: that's the input that decides what we do first.
Starting a security review
Security review is where enterprise infrastructure deals go to die, usually because nobody said early what the vendor couldn't do. So here's both halves.
What we can put in front of your team this week
- An architecture summary: what runs where, what's stored, what leaves the region
- The tenancy and isolation model, down to how the tenant clamp is enforced and tested
- Encryption at rest and in transit, and our subprocessor list - the cloud provider and the embedding model provider
- Data handling for embeddings: what content is sent for vectorisation, and what's retained
- A data processing agreement on request
- A direct line to the founder who built the system, not a support queue
What we can't do yet
- Hand you a SOC 2 report, an ISO 27001 certificate, or a HIPAA attestation
- Run the data plane inside your own cloud account
- Give you customer-managed encryption keys or SSO today
- Turn around a 300-question vendor questionnaire in a week - we're a small team and we'll tell you honestly how long it'll take
- Point you at a peer reference in your industry - we're early, and we'd rather say so than imply one
Procurement: a listing that lets you buy through your existing AWS agreement and committed spend is in progress - not live yet. If that's how your organisation prefers to onboard vendors, it's worth telling us; it moves up the queue.
Where this fits best
We're not going to claim customers we don't have. These are the shapes of problem Jennah was designed around - long-lived agent state, a real need to explain past decisions, and data that can't be casually copied between systems.
Financial services
Research, risk, and onboarding agents where every action needs a defensible trail. Replaying an agent's exact knowledge at the moment it acted is the difference between an explanation and a guess.
Healthcare and life sciences
Clinical and trial-facing agents that need hard tenant isolation, regional residency, and complete erasure across every place a patient detail could have landed - including embeddings.
Support and IT automation
Long-running resolution agents that carry customer context across months. Recall the relevant history instead of replaying whole transcripts into the context window on every turn.
Talk to us
Tell us what your security team will ask and what your timeline looks like. You'll get a straight answer about whether we're ready for you yet - and if we aren't, we'll say when we expect to be.
Prefer email? Reach us at info@nightblue.io.