Business Architecture
Open source core, optional cloud control plane.
Free stays local. Pro, Team, and Enterprise add sync, history, sharing, governance, policy, audit, and optional self-hosting without bypassing Figma permissions or rate limits.
Free is for individual local usage: CLI, MCP, local cache, snapshots, asset export, evidence review, compare, mappings, logs, and debug bundles.
Pro is planned for personal continuity: cloud snapshot sync, saved implementation briefs, compare history, and convenience across machines.
Team is planned for shared handoff: shared snapshots, shared mappings, CI compare, team logs, and reusable design context across product teams.
Enterprise is planned for governance: SSO, RBAC, retention policy, audit logs, private artifact storage, self-hosting, and organization-managed MCP templates.
Paid plans improve workflow scale and reliability. They do not bypass Figma permissions, seat access, upstream rate limits, or file sharing rules.
Run Sequence
- Start with Free for local CLI, MCP, cache, snapshots, export, compare, and debug bundles.
- Add Pro only when personal sync and cross-machine continuity matter.
- Add Team when multiple developers need shared snapshots, mappings, and CI compare.
- Add Enterprise when platform teams need SSO, RBAC, audit, retention, private storage, or self-hosting.
Expected Output
The product boundary should be obvious: Free produces local artifacts; paid editions synchronize, share, govern, or retain those artifacts with explicit user or organization control.
Files And Artifacts
- Free: local
.beam/artifacts - Pro/Team: planned cloud-synced Beam artifacts
- Enterprise: planned private or self-hosted artifact storage
Next Step
Use the edition table to decide which business workflow the user is trying to solve before describing cloud features.
Recovery Paths
- If a user expects paid Beam to bypass Figma rate limits, explain the hard boundary and offer caching or team proxy options.
- If a team needs shared context, start with snapshot sharing rather than raw token sharing.
- If an enterprise needs control, keep credentials, retention, and audit requirements separate from the local core.
