One memory for the whole company.
Deployed on your machines, audited to the fact.
Runs beside the assistants and tools your teams already use.
- Claude
- ChatGPT
- Cursor
- Claude Code
- Codex
- Perplexity
- Windsurf
- VS Code
- Slack
- Notion
- GitHub
- Linear
- Jira
- Confluence
- Google Drive
- Ollama
The knowledge base your team already has — finally written down
Decisions, owners, policies and customers, captured from the tools where they happen and served to every assistant your people open.
What did we decide about data residency for EU customers?
Recalled 3 facts from Esment · Acme LabsShip faster, without losing the thread
Every fact has a source, an owner, a history and an access rule. Agents build on what the team decided, and what they learn goes to review before anyone else sees it.
src › dispatch › builder.rs › Dispatcher
1use crate::geo::{Geofence, Point};
2use crate::matching::{Driver, Matcher};
3
4pub struct Dispatcher {
5 matcher: Matcher,
6 fences: Vec<Geofence>,
7}
8
9impl Dispatcher {
10 pub fn assign(&self, pickup: Point) -> Option<Driver> {
11 let driver = self.matcher.nearest(pickup)?;
12 // TODO: validate the service area
13 Some(driver)
14 }
15}
Chosen by the people who have to run it
Admins give each workspace its members and roles, issue keys that can never exceed their own permission, and see who wrote what — on your own servers.
Seats
10
unlimited
Members
10
Workspace
Acme Labs
Owner
Authors
9
who wrote something
| Member | Role | Memories | |
|---|---|---|---|
| AKalex.kim@acme.devyou | Owner | 2,418 | |
| PSpriya.shah@acme.dev | 1,907 | ||
| JWjonas.weber@acme.dev | 1,655 | ||
| ARanna.ruiz@acme.dev | 1,203 | ||
| AOamara.okafor@acme.dev | 988 | ||
| ELerik.lindqvist@acme.dev | 874 | ||
| LFlucia.ferrer@acme.dev | 640 | ||
| TNtom.nguyen@acme.dev | 512 | ||
| SCsara.cohen@acme.dev | 12 | ||
| SLsam.lee@acme.dev | 0 |
Invite a member
The invitee needs Pro or higher on their own account to join.
Who knows about…
Workspace
AI is changing how teams work. Memory decides what they keep.
0
outbound calls at runtime in the air-gapped profile. Inference, embeddings and storage are processes on your box.
< 40 ms
median recall on a laptop — text, vectors, graph and rerank, before the model sees the question.
100%
of facts with a source, a commit hash and a history you can diff or read as of any date.
Powerful, yet adaptable
Standardise what your teams can save, who can read it and which models can see it.
Full control
Allow or block integrations, assistants and models per workspace. Roles on every key, enforced on REST and MCP alike.
allow · block · per workspace
Access the best models — or none
Frontier models from your own accounts, or a bundled local model that never leaves the box.
Ship with confidence
Every write is a commit with checks. Review queues, contradiction detection and a log you can export.
key:legal-rw 7 minutes ago
retention 90d → 30d
All checks passed 3 successful
Policy check · residency
PII scan · none found
Contradiction check · supersedes 1
Trusted by teams that cannot leak.
Built with security and compliance as the base.
Expert guidance
We plan the rollout with you and stay reachable after it ships.
Premium support
A contract, an SLA and a direct line to the people who maintain the engine.
No data retention — by construction
Nothing leaves your network at runtime. There is no telemetry to turn off.
Identity and roles
Admin, read-write and read-only keys, per member, per workspace. SSO on request.
Workspaces, walled off
Every row is scoped to its workspace. One team’s key cannot see another’s memory.
Centralised controls
Allow-list integrations, assistants and models from one place.
Global compliance
Built for GDPR from the ground up; data residency is wherever the box is.
Signed, reviewable builds
A dedicated, signed build per deployment; source review under NDA.
Strong data protection
Encryption at rest on your disk, TLS on the LAN, a commit hash on every fact.
Frequently asked questions
Per seat, with unlimited workspaces and memories, plus a contract and SLA. Deployment help is included; there is no usage-based component.