Focus on building your product not on debugging your tools.
The best tools are intuitive. Simply working as expected. But no tool is perfect. There will be times when you'll need to troubleshoot, or ask a real person important questions. Premium Support gives your team a solution for all of your upgrading, scaling, and troubleshooting needs.
Premium Support is included in the GitLab Enterprise Edition Premium plan.
Tiered Support responses: Our team of highly skilled support engineers will help with all of your support needs, based on the priorities below.
Production Application Unavailable (Emergency)
24x7 emergency support: GitLab responds within 30 minutes to any emergency.
Support for High Availability (HA): A Support Engineer will help you identify your specific HA needs and map out an architecture.
Live upgrade assistance: Schedule an upgrade time with GitLab. We’ll host a live screen share session to help you through the process and ensure there aren't any surprises.
Fast: Our support priority levels makes sure that we are focusing on the right issues at the right time.
Technical: Our Support Engineers have strong technical backgrounds and are well-versed on GitLab. They'll work with you directly to understand your unique challenges and find the best solutions.
Reliable: Our support team is spread out across the world, with members on every continent. There will always be someone available to help, regardless of your time zone.
Definitions of Support Impact
Urgent - GitLab is unavailable or completely unusable (Emergency) If a GitLab server or cluster is not available, or otherwise unusable, an emergency ticket can be filed and our On-Call Support Engineer will respond within 30 minutes. Example: GitLab showing 502 errors for all users.
High - GitLab is Highly Degraded (4 hours) Significant Business Impact. Important GitLab features are unavailable, or extremely slowed, with no acceptable workaround. Implementation or production use of GitLab is continuing; however, there is a serious impact on productivity. Example: CI Builds are erroring and not completing successfully, and the software release process is significantly affected.
Normal - There appears to be a bug preventing normal GitLab operation (12 hours) Some Business Impact. Important GitLab features are unavailable, or somewhat slowed, but a workaround is available. GitLab use has a minor loss of operational functionality, regardless of the environment or usage. Example: A Known bug impacts the use of GitLab, but a workaround is successfully being used as a temporary solution.
Low - Questions or Clarifications around features or documentation or deployments (24 hours) Minimal Business Impact. Information, an enhancement, or documentation clarification is requested, but there is no impact on the operation of GitLab. Implementation or production use of GitLab is continuing and work is not impeded. Example: A question about enabling ElasticSearch.