Skip to main content

​
Plans and limits

Every workspace has an active plan. The plan controls the capacity and product capabilities available to that workspace. It is not assigned globally to the developer account.
When an account belongs to multiple workspaces, each workspace can have a different plan, subscription, usage level, and set of add-ons.

​
Workspace-scoped limits

Plans can define limits for: The exact values shown on the Subscription page are the source of truth.

​
Capacity limits and feature entitlements

Launcher Forge uses two kinds of plan rules.

Capacity limits

Numeric limits such as games, members, storage, bandwidth, and branches.

Feature entitlements

Features enabled or disabled by the plan, such as private branches, custom templates, analytics, API access, or commerce integrations.

​
Current plan

The active plan is displayed in the top navigation bar and on the Subscription page. The dashboard can show:
  • Plan name.
  • Billing interval.
  • Current status.
  • Included limits.
  • Included features.
  • Current subscription period.
  • Available upgrades or downgrades.

​
When a limit is reached

Depending on the resource, Launcher Forge can prevent a new action, such as:
  • Creating another game.
  • Inviting another member.
  • Creating another branch.
  • Uploading a build that exceeds storage capacity.
  • Using a feature not included in the plan.
Existing resources are not described as becoming part of another workspace. They remain associated with the workspace that created them.
Before changing to a lower plan, review current usage. A workspace above the new limits may need to reduce usage or upgrade before new resource-creating actions become available.

​
Add-ons and overrides

Add-ons can increase specific capacity without changing the base plan. Examples include:
  • Additional storage.
  • Additional bandwidth.
Add-ons:
  • Belong to the workspace.
  • Are billed separately from the base subscription.
  • Have their own active or expiration period.
  • Can be managed only by the Owner.
Administrative overrides can also adjust entitlements for testing, support, or custom agreements when available.

​
Plan comparison

When comparing plans, review both numbers and features. A higher plan can provide:
  • More games.
  • More team members.
  • More storage.
  • More bandwidth.
  • More branches.
  • Private branches.
  • Custom templates.
  • Analytics.
  • API or commerce capabilities.
Do not select a plan only by storage. Review the complete feature set required by the project.

​
Role access

Before selecting a plan, estimate:
  • Number of games.
  • Number of collaborators.
  • Packaged build sizes.
  • Number of active versions and branches.
  • Expected downloads and update traffic.
  • Need for private branches.
  • Need for custom templates, analytics, API, or commerce tools.
The correct plan is the one that supports the project’s current resources and next release cycle without relying on permissions or capacity that are not included.

Subscription

Manage the base workspace plan and billing period.

Usage

Understand how current resource consumption is measured.

Team members

Review member limits and workspace roles.