Skip to content
PLUR Docs

PLUR Enterprise

PLUR Enterprise is the multi-user hosted-product surface around @plur-ai/core. Same engine, same engram model, same recall math — wrapped in the things a team needs: authentication, permission enforcement, audit trail, admin tooling, and a server that survives more than one developer using it.

When to pick Enterprise over local PLUR

Section titled “When to pick Enterprise over local PLUR”
QuestionLocal PLUREnterprise
Single human, multiple machines?✓ (sync via git)overkill
Team sharing scoped knowledge?painful (file shuffling)✓
Need server-side permission checks?–✓
Compliance — audit log, retention?–✓
SSO with corporate IdP (OIDC, SAML)?–✓
Automated user provisioning (SCIM)?–✓
Webhooks to internal systems?–✓
Mobile / non-MCP clients via REST?–✓
Lives at https://plur.your-org.com?–✓

A team installs @plur-ai/mcp locally on each developer’s machine. PLUR Enterprise runs centrally and gets registered as a remote store via plur_stores_add. Engrams flow into shared scopes (group:org/team/...) and back out to every team member’s local PLUR seamlessly.

What’s in the box

Section titled “What’s in the box”
  • Multi-user MCP/SSE server — same protocol as local @plur-ai/mcp, but with JWT/API-key auth, per-user scope resolution, and audit logging.
  • Public REST API at /api/v1 — same data + permission model over HTTP for non-MCP clients (CI, automation, custom integrations).
  • Admin dashboard at /admin — overview, users, teams, engrams, audit log, OIDC/SAML providers, SCIM tokens, settings.
  • End-user portal at /me — your engrams, team scopes, API keys, webhook subscriptions, recent activity.
  • Auth: GitHub OAuth, GitLab OAuth, OIDC SSO (any RFC-compliant provider), SAML 2.0, long-lived API keys, SCIM 2.0 provisioning.
  • Webhooks with HMAC-SHA256 signing, retry, auto-disable.
  • Operational tooling: status page, daily backups, off-host backup push, role-tightened Postgres, structured audit log.

Status

Section titled “Status”

Pilot — running at https://plur.datafund.io with the Datafund team. Production-readiness for external customers is tracked on the enterprise GitHub issue tracker. The Apache-2.0 core is stable; integrations and admin surfaces are still iterating.

License & pricing

Section titled “License & pricing”

Apache-2.0 — same as @plur-ai/core. The code is open source; you can self-host any time. The PLUR team offers commercial support, hosted deployment, and pilot engagements — see plur.ai for current offers.

Where to go next

Section titled “Where to go next”