twin memory

The same memory, inside your controls.

Everything on Scale, with single sign-on, audit export, your own keys, a dedicated deployment and an SLA. Most of these are not built yet, and each is marked.

Enterprise addsState
Single sign-onSAML and OIDC for the console, with domain captureSoon
Audit log exportWho did what in the console, streamed to your SIEMSoon
Customer-managed keysMemory encrypted at rest under a key you hold and can revokeSoon
Dedicated deploymentA single-tenant deployment, in our cloud or your VPCSoon
Uptime SLAA committed uptime with service creditsSoon
Data processing agreementOur DPA, or yours, signed with the contractDraft

Already true on every plan

The controls a security review asks about first are not an Enterprise upgrade. Every account, Free included, gets them.

Every plan
  • A file per end userNo end user's memory shares a database with another's
  • Erasure receiptsEvery copy removed, counted per table
  • Daily spend capPer organisation; past it, nothing is refused
  • Logs without bodiesMetadata only, kept 7 days

Talk to us

There is no form. Email sales@twinmemory.dev and a person who builds memory will answer.

It helps to say

  • How many end users, and roughly how many events and searches a month.
  • What your security review needs: SSO, audit export, keys, a DPA.
  • Where memory must run: our cloud, a region, or your VPC.
  • When you need it by.

Write to

sales@twinmemory.dev

Security questions go to security@twinmemory.dev.