Manage BIMP Subscription

Manage your subscription from Settings → Organization → Billing and usage. This page shows the active organization’s subscription status, billing cadence, renewal or paid-through date, licensed capacity, and current usage.

Billing is managed by organization

Each BIMP organization has its own subscription, billing details, and usage quotas. Repository and artifact capacity cannot be shared between organizations.

If you belong to more than one organization, use the organization switcher before opening Billing and usage. Upgrading, downgrading, or canceling affects only the selected organization.

Only an organization Owner can manage the subscription. Other users with billing access can view its status and usage.

Upgrade your subscription

To upgrade:

1. Open Settings → Organization → Billing and usage.
2. Select an available edition.
3. Choose monthly or annual billing.
4. Enter the number of licensed repository slots you need.
5. Select Continue to Stripe.
6. Review and confirm the change in Stripe.

Downgrade or reduce capacity

To downgrade or change your licensed capacity:

1. Open Settings → Organization → Billing and usage.
2. Choose the required edition or select Change capacity.
3. Select the billing cadence and number of repository slots.
4. Review the effective date and confirm the change in Stripe.

You cannot reduce the licensed repository capacity below the number of repositories currently tracked by BIMP. Remove repositories you no longer need before selecting a lower capacity.

Because artifact capacity is calculated from repository slots, also check your artifact usage before reducing capacity. Stripe shows when the subscription change will take effect.

Cancel your subscription

To cancel an active subscription:

1. Open Settings → Organization → Billing and usage.
2. Select Payment details and invoices.
3. Cancel the subscription in the Stripe billing portal.
4. Review the cancellation date before confirming.

Cancellation is scheduled for the end of the current billing period. The organization retains its paid access until the displayed paid-through date. After paid access ends, the organization enters read-only offboarding.

Canceling one organization does not affect subscriptions belonging to other BIMP organizations.

Understand repository capacity

A licensed repository slot allows BIMP to track one repository. Tracking several branches from the same repository does not consume additional repository slots.

The repository meter on Billing and usage shows the number of tracked repositories against the licensed capacity. When the quota is reached, BIMP cannot add another repository until you either:

• increase the licensed repository capacity; or
• remove a repository that BIMP no longer needs to track.

Understand artifact capacity

An artifact is a supported file containing container image references, such as a Dockerfile, Compose file, devcontainer configuration, or supported Helm values file.

Each licensed repository slot contributes ten artifact slots to a shared organization pool. For example, a subscription with 10 repository slots includes capacity for 100 artifacts. If you use a monorepo with 100 artifacts, you need to purchase 10 repository slots to increase the organization’s artifact capacity to 100.

Artifact capacity is pooled rather than reserved per repository. One repository can use more than ten artifact slots provided the organization’s total usage remains within its allowance.

A file counts as one artifact even when it contains several image references. The same file path in one tracked repository counts once when it appears across multiple tracked branches.

The artifact meter on Billing and usage shows current usage against the pooled allowance. If your organization exceeds that allowance, increase its licensed repository capacity or remove artifacts and repositories that BIMP no longer needs to track. Resolve an artifact overage before the displayed renewal date to avoid restrictions on new scans, policy publication, and remediation.