How Sentra works
The questions buyers ask us most, answered with how the product actually behaves.
- How Sentra keeps company memory current
Every fact in Sentra keeps the source it came from and the time it happened. Newer evidence wins over older evidence, corrections are kept as dated facts, and edits people make are never overwritten by a later sync.
- How Sentra knows who said what and who owns what
The same person, customer or project shows up under different names in every tool. Sentra resolves them to one entity, keeps new ones as proposals until someone confirms them, and lets anyone correct it in chat.
- How Sentra raises problems before anyone asks
Every AI tool waits for a question. The costly problems in a company are the ones nobody knows to ask about. Sentra looks for them, checks they are still open and tells the person who needs to know, and stays silent when there is nothing worth saying.
- Sentra for agents: the MCP server and API
Claude, ChatGPT, Cursor and internal agents reach the same company memory as people do, through the Sentra MCP server and REST API, with the same permissions applied to every call.
- How Sentra turns meetings into company memory
Meeting notes stay in the meeting. Sentra turns what was decided into facts about the people, accounts and projects involved, so a decision made on a call is connected to the email, chat and records that follow it.
- How Sentra enforces permissions on every fact
A fact in Sentra inherits the permissions of the system it came from, checked when someone asks, not when the data was loaded. If Sentra cannot confirm access, the answer is no access.