> For the complete documentation index, see [llms.txt](https://docs.cloudback.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudback.it/account-and-billing-management/pricing.md).

# Pricing

Cloudback pricing plans, billing cycles, and pay-as-you-go options. Per-unit pricing across all supported platforms - all features included on every plan.

Cloudback charges **per repository, not per user**. All plans include every feature - there are no feature gates or enterprise-only restrictions.

## How Units Work

Each backup consumes units from your subscription pool. Units are shared across all connected accounts and platforms.

| Platform     | Unit Cost                                                                                              |
| ------------ | ------------------------------------------------------------------------------------------------------ |
| GitHub       | 1 unit per repository                                                                                  |
| Azure DevOps | 1 unit per repository                                                                                  |
| GitLab       | 1 unit per project                                                                                     |
| Linear       | Tiered per active workspace member: 2 units for members 1-25, 1 unit for members 26+ (minimum 2 units) |

For platform-specific details, see: [GitHub](/github/pricing.md) | [Azure DevOps](/azure-devops/pricing.md) | [GitLab](/gitlab/pricing.md) | [Linear](/linear/pricing.md)

## Fixed Plans

Fixed plans include a set number of units. Monthly fixed plans include a **free first month**.

| Plan           | Included Units                                    | Monthly | Annual | 2-Year  | 3-Year  |
| -------------- | ------------------------------------------------- | ------- | ------ | ------- | ------- |
| **Free**       | 1 repository per connected account (100 MB limit) | $0      | -      | -       | -       |
| **Basic**      | 10                                                | $10     | $114   | $216    | $306    |
| **Team**       | 100                                               | $75     | $855   | $1,620  | $2,295  |
| **Enterprise** | 1,000                                             | $500    | $5,700 | $10,800 | $15,300 |

You can purchase multiple units of each plan to increase coverage (e.g., 2x Basic = 20 units).

## Pay-as-you-go Plans

Pay-as-you-go (metered) plans include the same base units as fixed plans, plus the ability to add repositories beyond the included amount at a per-unit rate. Billing adjusts automatically based on usage.

| Plan                         | Included Units | Additional Units | Monthly | Annual | 2-Year  | 3-Year  |
| ---------------------------- | -------------- | ---------------- | ------- | ------ | ------- | ------- |
| **Basic Pay-as-you-go**      | 10             | $1.00/unit       | $10     | $114   | $216    | $306    |
| **Team Pay-as-you-go**       | 100            | $0.75/unit       | $75     | $855   | $1,620  | $2,295  |
| **Enterprise Pay-as-you-go** | 1,000          | $0.50/unit       | $500    | $5,700 | $10,800 | $15,300 |

Cloudback supports up to 10,000 repositories per account. Need more? [Contact us](/troubleshooting-and-support/contact-us.md).

## Free Plan

Every connected account gets 1 free backup slot independently - no subscription assignment required. This allows you to back up one repository or project per account at no cost.

The free slot covers repositories only. Linear has no free plan - every Linear workspace is billed using the member tiers above. See [Linear Pricing](/linear/pricing.md).

## How to Subscribe

All paid plans include a **free trial** so you can test the service before committing.

* **Credit Card (direct checkout)**: Buy a subscription with a credit card directly from the **Subscriptions** page in the Cloudback dashboard, paid through [Paddle](https://paddle.com). See [Payment Methods](/account-and-billing-management/payment-methods.md) for details.
* **GitHub Marketplace**: Purchase from the [GitHub Marketplace listing](https://github.com/marketplace/cloudback) - billing through your GitHub account.
* **Azure Marketplace**: Purchase from the [Microsoft Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/myrtlelabs-sas.cloudback) - billing through your Azure account.
* **Azure DevOps Marketplace**: Install via the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=MYRTLELABSSAS.cloudback-backup-azure-devops).
* **Coupa Supplier Portal**: Procurement-friendly purchasing via [Coupa](https://supplier.coupahost.com/suppliers/public/myrtlelabs-sas-GmZw0) - [contact us](/troubleshooting-and-support/contact-us.md) to coordinate.
* **Bank Transfer / Invoice**: Available for quarterly plans and enterprise customers - [contact us](/troubleshooting-and-support/contact-us.md).

After purchase, you can assign your subscription to multiple accounts across all platforms. See [Subscription Management](/account-and-billing-management/subscription-management.md) for details.

## Learn More

* [Subscription Management](/account-and-billing-management/subscription-management.md) - Manage subscriptions and account assignments
* [Payment Methods](/account-and-billing-management/payment-methods.md) - All supported payment options
* [Invoiced Customers](/account-and-billing-management/invoiced-customers.md) - Enterprise billing options


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudback.it/account-and-billing-management/pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
