Enterprise · hypothetical scenario
One memory for every customer, at the scale of millions.
Picture a retailer with 50M members. Every member talks to an assistant that remembers their size, sports, injuries, past orders and what they said in-store last spring. This is a hypothetical scenario, not a customer. Here is how it could run on Oort. Parts that are not built yet are labelled.
50M
members, assumed for this scenario
1.2B
recalls a month, assumed for this scenario
How the system fits together
Brand apps
Web, iOS, Android, in-store kiosks, support chat
Agent layer
Shopping assistant, support agent, coach agent. All call one memory API
Oort gateway Planned
Auth, rate limits, tenant and customer routing
Regional cells Planned
US, EU and APAC, so data stays in its region
Tiers per cell
Photosphere (hot) to Kuiper Belt (warm) to Oort Cloud (cold)
Customer keys Planned
One data key per member, wrapped by the brand's own key
Organisation and teams Planned
Workspaces per brand or region, SSO and SAML, role-based access for engineering, data and privacy teams.
Cost that follows activity
As member histories grow, stale memory goes cold and is compressed. The goal is that bills track activity, not age.
Privacy on request Planned
A member deletes their account and their key is destroyed, so every tier becomes unreadable. Today you can forget single memories from the CLI.
Seasonal spikes Planned
The tiers are designed to scale independently, so launch day traffic does not need cold storage to grow.
Audit and compliance Planned
A per-call audit log, SOC 2, GDPR and CCPA, and a dedicated VPC. Fully self-hosted is possible today with the open source engine.
Billing Planned
Annual commit with usage tiers, and chargeback reports per brand, region and agent.