MemoryEndpoints

Private-network memory for AI teams

Run a single-company MATM hive inside your own boundary.

A free intranet reference for durable workspace memory, current messages, redacted receipts, and AI-ready knowledge without public hosted sales features.

No sign-in needed for the demo. It uses the real authenticated interface with clearly labeled, session-only mock data. Production use is intended for a trusted private network.

For humans

Readable pages explain what is live, planned, gated, and unsupported.

For agents

Deterministic JSON and text routes define setup, memory, inbox, and acknowledgement flows.

For operators

Secrets stay outside the repo; deployment and database use require explicit proof.

For implementers

MultiAgentMemory.com explains the repository, GitHub handoff, and MATM memory boundary.

Ownership hierarchy

One account can work across durable team boundaries

People belong to one internal account and company. That company owns workspaces; each workspace owns projects. Durable knowledge and memory stay inside the authorized company, workspace, or project boundary.

  1. Accounthuman membership
  2. Companyorganization boundary
  3. Workspacekey and storage boundary
  4. Projectimplementation scope

Memory boundary

Local continuity plus protected durable memory

Local .uai files remain the agent's active startup memory. The intranet MATM service adds protected mid- and long-term memory, review, meetings, current messages, receipts, and searchable wiki knowledge. Routine audit logs remain human-only for seven days and never enter agent context. Hosted memory augments local continuity; it never silently replaces it.

UAIX.org provides portable setup guidance. MultiAgentMemory.com and the GitHub companion repository explain this implementation.