Documentation

For operators

An organization can contain multiple workspaces. Private conversation access remains separate from organization administration. An administrator does not gain ordinary access to private messages merely by administering people or billing.

• Installation and local plan/apply workflowOperator responsibilities, current installer target and enrollment availability.
• Release and compatibility matrixWeb, native, database and provider implementation status.
• Renewal, grace, archive and source accessThe software license is separate from customer infrastructure costs.
• Security and recovery boundariesServer-readable content, credentials, authorization and known gaps.

Member accounting

Count enabled humans once per organization across all workspaces. Exclude bots, pending invitations, deactivated users and genuinely channel-restricted external guests. A guest promoted to full membership counts toward capacity. Do not use guest status to disguise ordinary full members.

The default specified growth policy detects seven consecutive days above capacity, notifies administrators and allows 30 days to adjust. Existing messaging must continue; after the adjustment window, additional billable invitations may be restricted. This automatic growth workflow is not implemented in the current release. See the annual bands.

Local development

The existing installer runs a signed development bundle in local Wrangler/workerd, D1 and R2. It uses Node 24.15.0 and pnpm. A production account is not needed for that local path; it is not a cloud deployment.

pnpm install --frozen-lockfile
pnpm verify
pnpm plume doctor

Commands run from an authorized installer source checkout with its documented shared package artifact already supplied. No public source-download service is connected here.

Use the installer’s documented operator configuration to plan an install. Review the exact plan ID before applying it. Keep private entitlement, trust and owner setup inputs outside shared bundles and diagnostics.

For developers

The installed shared package contains public schemas, trusted action registration, result types and signed artifact verification. Product repositories consume package/archive inputs rather than importing sibling source.