Pipeline minutes are the execution time for your pipelines on our shared runners. Execution on your own runners will not increase your pipeline minutes count and is unlimited.

If you reach your limits, you simply won’t be able to use our shared runners to execute pipelines until the end of your current billing cycle, or until you upgrade your account to Silver or Gold. Your own runners can still be used even if you reach your limits.

The minutes limit only applies to private projects. Public projects include projects set to “Internal” as they are visible to everyone on GitLab.com.

No. We will only restrict your minutes for our shared runners. If you have a specific runner setup for your projects, there is no limit to your build time on GitLab.com.

There is no catch. Part of our strategy sequence is to make GitLab.com the most popular SaaS solution for private and public repositories. To achieve this goal you get unlimited public and private projects, and there is no limit to the number of collaborators on a project.

No, all users in the group need to be on the same plan.

Absolutely, GitLab Pages will remain free for everyone.

Head over to https://customers.gitlab.com, choose the plan that is right for you. After purchase, we’ll take care of upgrading your account to the plan you’ve chosen.

Yes. You can import your projects from most of the existing providers, including GitHub and Bitbucket. See our documentation for all your import options.

Head over to https://customers.gitlab.com, choose the plan that is right for you.

GitLab.com is monitored 24/7. Our servers are hosted on Amazon Web Services (AWS), Digital Ocean, and Azure, we use configuration management, and we patch our servers at least once a week. Our runbooks are public as is our operational issue tracker. GitLab offers Two-Factor Authentication (2FA) via a mobile application or a U2F device, rate limiting, audit logs, and passwords are one-way encrypted. Answers to other common security questions are available on our security page.

You can export most of your data at any time. Your data belongs to you. You are never stuck on GitLab.com, you can always export and import your project to a self hosted version of GitLab.

No. The limit will be applied to a group, no matter the number of users in that group.

The project and wiki repository, Git LFS files, attachments, build artifacts, and images in the container registry.

Where possible, GitLab.com uses the standard package defaults. A list of all customized settings like the SSH host keys, Runners and Pages settings is available on the GitLab.com settings page.

For more information see our status page at status.gitlab.com and follow @gitlabstatus on twitter.

Not yet, but we are working on it, you will soon be able to track your storage usage across all features and buy additional storage space for GitLab.com.

• Fast page load
• Allow edits from upstream maintainers in branch
• GitLab server monitoring
• 4-hour support response time
• Drag and drop tasks
• SUPPORT file link
• Access to the server
• Runs on metal
• Run your own software on your instance
• Use your configuration management software
• Use standard Unix tools for maintenance and monitoring
• Single package installation
• Single configuration file
• Basic backup and restore mechanism without additional software
• IPv6 ready
• AD / LDAP integration
• Access to and ability to modify source code
• Advanced Global Search
• Advanced Syntax Search
• Create and remove admins based on an LDAP group
• Kerberos user authentication
• Integrate with Atlassian Crowd
• Multiple LDAP server support (compatible with AD)
• PostgreSQL HA
• Import from GitLab.com
• Email all users of a project, group, or entire server
• Limit project size at a global, group, and project level
• Omnibus package supports log forwarding
• Admin Control
• Restrict SSH Keys
• LDAP group sync
• LDAP group sync filters
• Live upgrade assistance
• Auditor users
• Disaster Recovery (Alpha)
• Database load balancing for PostgreSQL
• Code Owners
• Mattermost integration
• Object storage for artifacts
• Object storage for LFS
• Globally distributed cloning with GitLab Geo (Beta)
• Support for High Availability
• Easy upgrade process
• Configurable issue closing pattern
• Navigate to method/function in a merge request diff
• Custom Git Hooks
• Various authentication mechanisms