# Sentra: Permission-aware organization memory

Canonical: https://mudpie.ai/companies/sentra/
Breadcrumb: [Home](https://mudpie.ai/) / [Companies](https://mudpie.ai/companies/) / [Sentra: Permission-aware organization memory](https://mudpie.ai/companies/sentra/)
Author: Ali Abouelatta (https://mudpie.ai/authors/ali-abouelatta/)
Published: 2026-09-20
Updated: 2026-09-20
Research type: Company profile
Method: Public-source research. Official Speedrun and company pages checked September 20, 2026. Product claims are attributed to their sources.

Sentra’s memory product only works if permission survives the merge.

## What it does

Sentra describes managed organization memory: meetings, messages, documents, code and deals become one queryable context for people and agents. The trust page says access controls inherit from connected tools such as Slack, GitHub, Linear and Google Workspace, and that private meetings can stay out of shared memory.

The Lenskart case study shows the company’s preferred proof point. Sentra says it compiled 19 billion tokens of operating history into a world model, went live in eight days, reduced stalled dependencies by 58% in four weeks and cut root-cause investigations from three or four days to about 30 minutes. These are company-published case-study claims, not an independent result.

## Buyer and task

The buyer is an organization with decisions scattered across meetings, messages, documents and code. The first task is a permission-sensitive question: find the decision, show its source, and prove that a person who could not open the original cannot retrieve it from memory.

The product’s advantage is also its risk. A shared memory can prevent the same decision from being rediscovered every week. It can also turn a forgotten permission boundary into a new data-exposure path. The trust page says Sentra mirrors source permissions; a procurement review should verify how revocation, private meetings and stale copies behave.

## The first test

Connect one small workspace and create three cases: a public decision, a restricted decision and a decision later revoked. Ask the same question as users with different source permissions. Check the citation, deletion behavior and audit trail. Then test whether the memory keeps the old answer after the source document changes.

The acceptance criterion is not “the agent remembers.” It is “the right person remembers the right thing, with the right source, and nobody else does.”

## Sources checked

[official Speedrun profile](https://speedrun.a16z.com/companies/sentra) · [company homepage](https://www.sentra.app/) · [Lenskart case study](https://www.sentra.app/customers/lenskart) · [trust and security](https://www.sentra.app/trust)

Sources checked — September 20, 2026.


## Author disclosure

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.