Chapter I

Esment for Enterprise

Esment is designed from the ground up for organizations that need full control over their data. It runs entirely on your infrastructure — no SaaS, no cloud, no third-party servers involved in your operations.

Your team’s AI memory stays in your hands. Always.

Your data, your servers

Every piece of data in Esment — every memory, every search index, every knowledge graph entry — lives on hardware you control. Nothing is transmitted to NotasAI. Nothing passes through external cloud infrastructure.

You can audit exactly what’s stored, where it’s stored, and who has access to it. This makes Esment well-suited for organizations with strict data governance requirements — including healthcare, legal, finance, and government sectors.

Local-first means private by design, not private by policy. There’s no setting to turn off, no data sharing to opt out of. The architecture simply doesn’t route your data anywhere external.

Esment Note

Esment can run in fully air-gapped environments with no internet connection. Everything your AI needs — embeddings, search, knowledge graph — runs locally in a single binary.

Team workspaces

Enterprise deployments support multiple users sharing a common memory layer. Your whole team’s AI assistants can draw from shared organizational knowledge while each person maintains their own private memory space.

  • Organizational memory — shared context all team members and AI tools can access. Decisions, policies, project briefs, client preferences.
  • Personal memory spaces — private to each individual. Their preferences, their working style, their ongoing tasks.
  • Project-scoped memory — context tied to specific workgroups or clients. Keeps information organized and prevents cross-contamination between accounts.
  • Agent memory — dedicated memory for autonomous AI workflows that run independently of any user session.

The result: every person on your team has an AI that knows the organization, knows their role, and knows what’s happening right now — without anyone having to repeat themselves.

Access control

Every connection to Esment is authenticated. You create and manage API keys from the admin panel in your dashboard — one key per user, per AI tool, or per integration.

Keys can be scoped to specific memory spaces and operations. A team member’s AI gets full read/write access to shared organizational memory. A third-party integration gets read-only access to a single project space. An automated agent gets its own isolated space it can’t escape.

All access is logged. You can see exactly which AI tool accessed which memory, and when.

Chapter II

Getting started

Enterprise deployments run on your own servers. We work directly with your team to plan, deliver, and support your rollout.

Self-hosted setup

Esment is delivered as a self-contained server binary for enterprise deployments. Run it on any Linux server, VM, or container infrastructure your organization already uses.

Point your team’s AI tools at your server address, distribute API keys from the admin panel, and shared organizational memory is immediately available to everyone. Each team member connects their own AI assistant to the shared instance.

Esment Note

Esment can run in fully air-gapped environments with no outbound internet access. Enterprise delivery includes offline installation packages on request.

Speak with us

For enterprise licensing, deployment support, security reviews, volume pricing, or SLA agreements, get in touch with our team.

  • Email: enterprise@notas.ai
  • Schedule a call: notas.ai/enterprise
  • We’ll help you evaluate Esment for your organization and support your rollout from day one.

We work with organizations of all sizes, from small teams to large enterprises with complex deployment requirements.

How to run a company with Cofounder