Repository archiving in Bitbucket Cloud 8.12: evaluating storage‑cost impact for low‑traffic workloads

Goal: Assess whether enabling the automatic repository archiving feature (introduced in Bitbucket Cloud 8.12) will lower storage expenses for repositories with infrequent activity while preserving required read‑only access.

• Archived repositories become read‑only, blocking pushes, pull requests and Pipelines execution.
• Storage is billed at a reduced rate, but the exact discount varies by region and subscription plan.
• Some integrations that depend on webhooks or merge checks may be disabled, potentially affecting automation.

What is the precise percentage reduction in storage cost for archived repositories across different regions and plans?

How does the read‑only state affect webhook‑driven workflows and merge‑check integrations?

Are there any hidden costs or operational overhead when periodically reviewing and unarchiving repositories?