Pricing
How Cloudback pricing works for GitHub repositories, including unit costs, what's included in backups, and where to subscribe.
Last updated
Was this helpful?
How Cloudback pricing works for GitHub repositories, including unit costs, what's included in backups, and where to subscribe.
Cloudback uses a per-repository pricing model for GitHub. You pay based on the number of repositories you protect, not the number of users or seats in your organization.
Each GitHub repository with backups enabled consumes 1 unit from your subscription pool.
1 GitHub repository
1 unit
10 GitHub repositories
10 units
100 GitHub repositories
100 units
Units are shared across all connected accounts and platforms.
For full plan details, pricing tables, and billing cycle options, see Pricing.
Every GitHub backup includes the full repository plus metadata:
Git repository (bare clone with all branches, tags, and refs)
Git LFS objects
Issues (including sub-issues and issue types)
Pull requests
Wiki pages
Releases and release assets
Labels, milestones, and topics
Projects V2
Commit comments
Collaborators
Webhooks (excluding secrets)
For a complete breakdown, see GitHub Backup Contents.
The recommended way to purchase Cloudback for GitHub is through the GitHub Marketplace:
Select your preferred plan on the Cloudback page on GitHub Marketplace
Follow GitHub instructions to complete the purchase
Cloudback will automatically activate for the selected account
For alternative payment methods (credit card, bank transfer, invoice), see Payment Methods.
Pricing - Full plan comparison with pricing tables
Subscription Management - Manage subscriptions and account assignments
Last updated
Was this helpful?
Was this helpful?