Pipeline minutes are the execution time for your pipelines on our shared runners.
If you reach your limits, you simply won’t be able to run any more pipelines until the end of your current billing cycle, or until you upgrade your account.
The minutes limit only applies to private projects.
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.
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.
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.
Please refer to GitLab.com settings for information about SSH host keys, Runners and Pages settings.
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.
Features that are more relevant to self hosted instances: LDAP (although we might add this), Audit user, Geo, Log forwarding, Limit project size, Pivotal Tile, and MySQL support.