> 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/linear/pricing.md).

# Pricing

How Cloudback pricing works for Linear workspaces, including the tiered per-member unit model, what's included in backups, and where to subscribe.

Cloudback uses a **per-workspace pricing model** for Linear, with units calculated from the number of active workspace members. Pricing is tiered so that small teams stay inexpensive and large teams scale gradually.

## How Units Work for Linear

Each Linear workspace with backups enabled consumes units based on the number of **active, non-app members** in the workspace. The tiers are progressive - each member is billed against the band they fall in:

| Member position in workspace | Units per member |
| ---------------------------- | ---------------- |
| Members 1-25                 | 2 units each     |
| Members 26 and above         | 1 unit each      |

The minimum is **2 units per workspace**. App users (bots/integrations) and suspended members are excluded from the count.

### Examples

| Workspace size     | Units consumed | Calculation      |
| ------------------ | -------------- | ---------------- |
| 1 active member    | 2              | 1 × 2            |
| 5 active members   | 10             | 5 × 2            |
| 6 active members   | 12             | 6 × 2            |
| 10 active members  | 20             | 10 × 2           |
| 25 active members  | 50             | 25 × 2           |
| 26 active members  | 51             | 25 × 2 + 1 × 1   |
| 50 active members  | 75             | 25 × 2 + 25 × 1  |
| 100 active members | 125            | 25 × 2 + 75 × 1  |
| 250 active members | 275            | 25 × 2 + 225 × 1 |

If you back up multiple workspaces, units add up across all of them. Units are also shared across all connected accounts and platforms.

The unit count is **recalculated automatically** after each successful backup (and on reconnect) using the current member count returned by the Linear API.

### No Free Plan for Linear

Linear has **no free plan or free tier**. The free backup slot included with every connected account covers repositories only (GitHub, GitLab, and Azure DevOps) - it does not extend to Linear workspaces.

Every Linear workspace is billed using the member tiers above. All paid plans include a **free trial**, so you can evaluate Linear backups before committing.

For full plan details, pricing tables, and billing cycle options, see [Pricing](/account-and-billing-management/pricing.md).

## What's Included

Every Linear backup includes workspace data:

* Workspace metadata and settings
* Users and external users
* Teams
* Issues and comments
* Projects and project updates
* Cycles
* Documents
* Initiatives and initiative updates
* Templates (issue, project, document)
* Custom views
* Workflow states
* Issue labels and project labels
* Project statuses and milestones
* Attachments and embedded files
* Issue relations
* Initiative-to-project links

For a complete breakdown, see [Linear Backup Contents](/linear/backup-contents.md).

## How to Subscribe for Linear

* **Credit Card (direct checkout)**: Buy a subscription 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.
* **Bank Transfer / Invoice**: Available for quarterly plans and enterprise customers - [contact us](/troubleshooting-and-support/contact-us.md).

For all payment options, see [Payment Methods](/account-and-billing-management/payment-methods.md).

## Learn More

* [Pricing](/account-and-billing-management/pricing.md) - Full plan comparison with pricing tables
* [Subscription Management](/account-and-billing-management/subscription-management.md) - Manage subscriptions and account assignments


---

# 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/linear/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.