The best way to ask general questions about particular use cases is to email our support team at email@example.com. Our support team is trying our best to respond ASAP, but there is no guarantee on a response time unless your organization enrolls in Priority Support.
If you have a feature request or noticed lack of some documentation please feel free to create a GitHub issue. Our support team will answer it by replying to the issue or by updating the documentation.
In addition to the general support we provide a Priority Support option with guaranteed response times. But most importantly we'll be doing regular checkins to make sure Cirrus CI roadmap is aligned with your company's needs. You'll be helping to shape the future of Cirrus CI/CD!
|Severity||Support Impact||First Response Time SLA||Hours||How to Submit|
|1||Emergency (Cirrus CI is unavailable or completely unusable).||30 minutes||24x7||Please use urgent email address.|
|2||Highly Degraded (Important features unavailable or extremely slow; No acceptable workaround).||4 hours||24x5||Please use priority email address.|
|3||Medium Impact.||8 hours||24x5||Please use priority email address.|
|4||Low Impact.||24 hours||24x5||Please use regular support email address. Make sure to send the email from your corporate email.|
24x5 means period of time from 9AM on Monday till 5PM on Friday in EST timezone.
Support Impact Definitions
- Severity 1 - Cirrus CI is unavailable or completely unusable. An urgent issue can be filed and our On-Call Support Engineer will respond within 30 minutes. Example: Cirrus CI showing 502 errors for all users.
- Severity 2 - Cirrus CI is Highly Degraded Significant Business Impact. Important Cirrus CI features are unavailable or extremely slowed, with no acceptable workaround.
- Severity 3 - Something is preventing normal Cirrus CI operation Some Business Impact. Important Cirrus CI features are unavailable or somewhat slowed, but a workaround is available. Cirrus CI use has a minor loss of operational functionality.
- Severity 4 - Questions or Clarifications around features or documentation Minimal or no Business Impact. Information, an enhancement, or documentation clarification is requested, but there is no impact on the operation of Cirrus CI.
How to submit a priority or an urgent issue
Once your organization signs the Priority Support Subscription contract, members of your organization will get access to separate support emails specified in your subscription contract.
Priority Support Pricing¶
As a company grows, engineering team tend to accumulate knowledge operating and working with Cirrus CI, therefore there is less effort needed to support each new seat from our side. On the other hand, Cirrus CI allows to bring your own infrastructure which increases complexity of the support. As a result we reflected the above challenges in a tiered pricing model based on a seat amount and a type of infrastructure used:
|Seat Amount||Only managed by us instance types||Bring your own infrastructure|
Note that Priority Support Subscription requires a purchase of a minimum of 20 seats even if some of them will be unused.
What is a seat?
A seat is a user that initiates CI builds by pushing commits and/or creating pull requests in a private repository. It can be a real person or a bot. If you are using Cron Builds or creating builds through Cirrus's API it will be counted as an additional seat (like a bot).
If you'd like to get a priority support for your public repositories then the amount of seats will be equal to the amount of members in your organization.
How to purchase Priority Support Subscription¶
Please email firstname.lastname@example.org, so we can get a support contract in addition to TOC. The contract will contain a special priority email address for your organization and other helpful information. Sales team will also schedule a check-in meeting to make sure your engineering team is set for success and Cirrus CI roadmap aligns with your needs.