Beam logoBeam

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

  1. Start with Free for local CLI, MCP, cache, snapshots, export, compare, and debug bundles.
  2. Add Pro only when personal sync and cross-machine continuity matter.
  3. Add Team when multiple developers need shared snapshots, mappings, and CI compare.
  4. 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

  1. Free: local .beam/ artifacts
  2. Pro/Team: planned cloud-synced Beam artifacts
  3. 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

  1. If a user expects paid Beam to bypass Figma rate limits, explain the hard boundary and offer caching or team proxy options.
  2. If a team needs shared context, start with snapshot sharing rather than raw token sharing.
  3. If an enterprise needs control, keep credentials, retention, and audit requirements separate from the local core.
FreeLocal CLI, MCP server, cache, snapshots, assets, evidence review, mappings, logs, debug bundles, and basic compare.
ProPlanned personal snapshot sync, saved briefs, persistent compare history, and cross-machine workflow continuity.
TeamPlanned shared snapshots, shared mappings, CI compare, team handoff history, and centralized operational logs.
EnterprisePlanned SSO, RBAC, policy, audit logs, retention controls, private artifact storage, and self-hosting.