Pricing
Metered by the second. Capped by you.
Pay for the hours a preview is awake.
No seats and no fee per environment. A preview nobody is looking at goes to sleep, and a sleeping preview costs nothing.
21% off every preview-hour
-
Hobby
$0$0 up to 3 previews at once
Free for as long as you likeFree for as long as you like
For side projects and trying it on a real repo.
- 500 preview-hours a month
- Seeded Postgres and Redis
- Public GitHub and GitLab repos
- Hosted on Canary's runners
-
Team
Most teams$0.19$0.15 per preview-hour
Billed monthly, by the minuteWith a yearly commitment of hours
Unlimited reviewers. You pay for the minutes a preview is awake.
- Unlimited concurrent previews
- Masked production snapshots
- Spend caps, SSO and audit log
- Private repositories
- A runner in your AWS or GCP account
-
Enterprise
CustomCustom above 200 previews a day
Volume pricing on a yearly agreementVolume pricing on a yearly agreement
For platform teams running previews for the whole company.
- Everything in Team
- Dedicated runners in any US region
- SAML and SCIM provisioning
- A 1-hour support SLA
- Security review and a signed DPA
Every plan includes unlimited reviewers, the CLI and canary.yml. Prices are for Canary itself: on Team and Enterprise the machines run in your own cloud account.
What a month actually costs.
Halyard in September: 38 engineers, 214 pull requests and a preview for every one of them. Each preview was awake for about three hours of the two days it existed.
| Item | Usage | Amount |
|---|---|---|
| Previews built 214 pull requests | 214 pull requests | — |
| Awake 663 preview-hours × $0.19 | 663 preview-hours × $0.19 | $125.97 |
| Asleep 9,870 hours | 9,870 hours | $0.00 |
| Reviewers 61 people | 61 people | $0.00 |
84% of the $150 cap
Line by line.
Eight differences. How many people may open a preview is not one of them.
| Feature | Hobby | Team | Enterprise |
|---|---|---|---|
| Preview-hours | 500 a month | Pay per hour | Committed volume |
| Previews at once | 3 | Unlimited | Unlimited |
| Private repositories | Not included | Included | Included |
| Masked production snapshots | Not included | Included | Included |
| Spend caps and sleep rules | Sleep only | Included | Included |
| SSO and audit log | Not included | Included | SAML and SCIM |
| Where previews run | Canary's cloud | Your AWS or GCP | Dedicated runners |
| Support | Community | Email, 1 business day | Shared channel, 1 hour |
Questions about the bill.
How the meter runs, what the cap does, and who pays for the machines. Anything else, ask and a person answers.
Email salesWhat counts as a preview-hour?
An hour that one preview is awake, metered by the second and billed by the minute. A sleeping preview costs nothing, however long it exists.
Do reviewers need a seat?
There are no seats. Anyone you allow can open a preview, and inviting the whole company does not change the bill.
What happens when we reach the spend cap?
Admins hear at 80 percent. At the cap, running previews go to sleep and new ones wait. Nothing is torn down and nothing is lost.
Who pays for the machines?
On Team and Enterprise the runner is in your cloud, so the compute is on your AWS or GCP bill and the preview-hour covers Canary. On Hobby we host both.
How does the yearly commitment work?
You commit to a number of preview-hours for the year at $0.15 and draw them down as you go. Hours past the commitment bill at the same rate.
Can we start on Hobby and move up later?
Yes. Your canary.yml and build cache carry over, and private repositories and masked snapshots switch on the moment you upgrade.
The first 500 hours are free.
Connect a repository, open a pull request and watch the first preview build. No card until you outgrow Hobby.
