Organization Pro
Pro adds a shared organization layer on top of pumaDB personal accounts. Your company gets common tables for team memory, and each user still keeps their own private personal tables.
How storage works
The important distinction is scope: organization tables belong to the organization, while personal tables stay attached to the individual user. A team can share company records without taking away anyone's private workspace.
Use organization tables for customer context, support playbooks, product notes, research, handoff state, and other memory that should be available to the team.
Each person still has their existing personal pumaDB account limits for private agent memory, experiments, drafts, and workflows that do not belong in company-wide tables.
Team capacity
company-level tables shared by the organization
private personal tables available across 100 users
total possible table slots across shared and private scopes
The shared organization quota and each user's personal quota are enforced separately. Pro increases organization-owned storage; it does not pool, consume, or reduce private personal table limits.
What else is included
Admins manage billing, membership, roles, and organization settings. Members can read and write organization tables.
Keep using pumaDB from agent clients over hosted MCP or from trusted backend services over REST.
Rate limits, batch size, query limits, version retention, and idempotency behavior stay the same on Personal and Pro.
Organization records get the same recovery trail, viewer links, and download workflows that make personal tables easy to inspect.
Upgrade path
If your agents should remember the same customer facts, project decisions, research notes, or operational context across a team, Organization Pro gives those records a shared home while private user memory remains private.