Governed memory for humans and agents

Connect Slack, preserve identity and source permissions, and serve authorized shared memory through MCP, the API, or the CLI—using the memory provider you choose.

Product direction

Slack → governed memory → MCP is the launch path. Labeled nodes are roadmap concepts.

Source Evidence

Nimbase Company Memory

Captured evidence

Preserved Slack source:

Preserves a decision thread with its channel identity and access policy.
Serving surface
Agent deployment
Through governed MCPCentral memory
Identity, permissions, provenance, and canonical checks protect the flow
Serving Surfaces
Selected memory route

Capture Slack evidence for Agent

Nimbase preserves source provenance and mirrored access. Retrieval verifies canonical state and current authorization before returning provider results.

Policy checked
A New Operating Paradigm

Capture → Compile → Serve

01

Capture

Synchronize Slack conversations, identities, and channel membership, or add shared memory directly.

02

Compile

Record canonical Sources, immutable revisions, provenance, and mirrored access before provider indexing.

03

Serve

Retrieve permission-checked context through the web app, API, SDK, CLI, and remote MCP deployments.

Protected end to end. Verified identity, mirrored source permissions, provenance, and canonical read-time checks protect every retrieval.

Open Source at the Core

Inspect it. Run it. Build on it.

Nimbase Community Edition is the complete public core, licensed under AGPL-3.0-only. Self-host the control plane that ingests, governs, and distributes memory—or choose Nimbase Cloud when you want us to operate it.

Explore the source

Community Edition

AGPL-3.0-only · Public repository

  • Provider-agnostic memory control plane
  • Source, identity, and permission sync
  • Web app, API, remote MCP, and workers
  • Bring your own memory provider

Nimbase Cloud adds managed hosting, upgrades, team governance, and enterprise identity integrations.

Roadmap Concept

One governed core for many serving surfaces.

Explore the broader product direction across sources and serving surfaces. Slack ingestion and governed MCP, API, SDK, CLI, and web retrieval are the launch slice available first.

N
Nimbase Console

Company memory workspace

Company WorkspacePRO ENTERPRISE

Acme Corporation

Company Memory Overview
Compiled Company Memory3 NotesDurable OKF memory
Captured Evidence28 SourcesSlack, GitHub, Jira, Gmail, Drive
Held for Evals2 SourcesProvider-managed evidence
Recently Compiled Memory
Recent Serving Activity
2m agoAllowed

Claude (coding agent) queried architectural rules Project Apollo Architecture

14m agoRedacted

Support Agent Bot requested contract values Enterprise SLA Notes

1h agoAllowed

Barry Tran (AE) previewed strategic client notes Customer Promise SSO

Serving Architecture Preview

Serve memory through the tools your company already uses.

Deployments are interfaces over one centralized company memory. Nimbase resolves identity, checks source-derived access, retrieves relevant memory, and keeps the supporting evidence attached.

Example Serving Surfaces

Target Guarantees
Identity-bound
Permission-filtered
Source-linked
Eval-gated

Coding Agent retrieval

Authorized company memory

01

Identity resolved

Coding Agent

02

Policy checked

2 sources excluded

03

Context returned

2 memories · 3 sources

Retrieved context
Project Apollo architecture

Apollo uses an event-driven ingestion pipeline. New source events are normalized before compilation, then promoted into durable memory only after provenance and access checks pass.

GitHub · ADR-012Slack · #eng thread 84Q2 roadmap
2 sources excluded by provider policy
Access checked before ranking · evidence remains source-linked
Company Memory in Use

One memory. Many company surfaces.

Search it directly or serve it through the web app, API, CLI, SDK, and MCP without duplicating the underlying knowledge.

Support Agents

Give support agents permission-checked shared context through MCP, with a path back to the underlying Slack evidence.

OutcomeFaster answers with inspectable evidence
Knowledge as a Service

Your company doesn't need another generic wiki.

We build custom knowledge and memory workspaces for companies with valuable context trapped across tools, teams, and systems. Start with Nimbase, then shape it around your operating model.

Discuss your workspace
  1. 01

    Map the knowledge flow

    We identify the sources, decisions, permissions, and retrieval moments that matter to your company.

  2. 02

    Build the workspace

    We design and implement the capture, memory, search, and agent workflows around the way your team already works.

  3. 03

    Put it into operation

    We deploy the system, connect it to your tools, and leave your team with infrastructure it can understand and extend.

A working system, not a strategy deck

  • Custom memory architecture
  • Source and agent integrations
  • Permission-aware retrieval
  • Operational handover
Infrastructure Grade Trust

Trust belongs in the memory system, not in a prompt.

Verified identity, mirrored source permissions, provenance, and canonical state checks protect each retrieval.

Stable Company Identity

Resolve verified email aliases and provider subjects to one UserProfile without fuzzy name matching.

Source Evidence Preserved

Keep the original, normalized markdown, provenance, and provider policy together at capture time.

Provider-Derived Access

Mirror source permissions and fail closed when identity or policy information is incomplete.

Canonical Verification

Drop superseded, forgotten, disabled, or newly unauthorized results even when a memory provider still returns them.

Choose your foundation

Start free. Pay when memory becomes multiplayer.

Self-host the open-source core for free. Managed Team pricing counts account-backed humans with active access—not agents, bots, stale users, or identities merely discovered through Slack.

Open source

Community

Freeforever

For individuals and builders who want to own their memory control plane and bring their preferred provider.

  • Self-hosted Community Edition
  • Personal memory and source management
  • CLI, API, and MCP access
  • Community-led support
View on GitHub
Managed cloud

Team

A$20per active human / month

Managed shared memory for teams that need source permissions preserved everywhere people and agents work.

  • Managed hosting and upgrades
  • Slack identity and access sync
  • Governed remote MCP deployments
  • Agents and imported identities are free
Get started
Cloud + partnership

Enterprise

Let’s talktailored to your team

For organizations that need a designed rollout, deeper integrations, and operational support.

  • Everything in Team
  • SAML SSO, SCIM, and directory sync
  • Advanced audit, retention, and policy controls
  • Dedicated onboarding and support
Discuss your workspace

Own your knowledge distribution before your agents need it.

Nimbase gives modern companies the secure knowledge distribution layer required for humans, customers, applications, and agents to work from shared context.