A real phone number
for GitLab.

How GitLab verification works

GitLab.com may ask for a phone number and a one-time password by SMS during identity verification, for example before free-plan CI jobs run on hosted runners. Some countries are unsupported.

Because SMSCreation numbers are real mobile numbers, GitLab treats them like any other phone: the code is delivered to your number and shows up in your dashboard inbox straight away.

Why it works with WhatsApp, Facebook, Telegram & Google

Apps check more than the digits: they look up the line type, the country format and whether the number can actually receive their code. Every SMSCreation number is a real mobile number in its country's official format — not a VoIP line — so it passes those checks the same way a SIM in your pocket does.

And we stand behind it with a 7-day replacement guarantee: if your number doesn't work with WhatsApp, Facebook, Telegram, Google or any app you need, we replace it free with a new number in the same country — or refund 100% if you prefer.

• Non-VoIP, real mobile line type — line-type checks see an ordinary SIM number, not a VoIP line
• Official country format with the right country code, prefix and digit count
• Unlimited incoming SMS and calls — codes arrive by text or through the “call me” option
• Private to you — never listed on public SMS sites, so it isn't flagged or rate-limited
• Yours for as long as you want — re-verification and account recovery keep working

GitLab phone verification details

On GitLab.com the phone number is part of identity verification, not two-factor sign-in. Every new account verifies an email. Depending on GitLab's risk score, medium-risk users are also asked for a valid phone number and a one-time password (OTP) code, and high-risk users may need a credit card. You'll most often meet this when you use GitLab-hosted runners on the free plan and a pipeline fails with "Identity verification is required in order to run CI jobs". Select Verify my account in the banner, follow the steps, then create a new commit or re-run the pipeline.

GitLab won't verify an account with a phone number tied to a banned user. It also publishes a country table. Phone verification is unsupported for numbers from places such as China, Russia, Pakistan, Bangladesh, Indonesia, Malaysia, Saudi Arabia, the UAE and Vietnam. It has only partial support in others, including Mexico, Nigeria, the Philippines, Turkey, South Africa and Ukraine. If phone verification isn't available, GitLab suggests credit card verification or a support ticket. GitLab's own 2FA doesn't use SMS: it offers passkeys, OTP authenticator apps, WebAuthn devices and email codes.

Code

One-time password (OTP) by SMS during identity verification

When it's asked

Medium-risk sign-ups, and free-plan users running CI on GitLab-hosted runners

Countries

Unsupported or partial in some countries; see GitLab's table

Numbers refused

Numbers associated with a banned user

2FA

No SMS option; passkeys, OTP apps, WebAuthn or email OTP

Common GitLab problems and fixes

• "Identity verification is required in order to run CI jobs" → GitLab needs to verify you before free hosted runners run → select Verify my account and complete the phone step, then re-run the pipeline.
• Your country is marked Unsupported → GitLab can't verify numbers there → use a number from a supported country, or try credit card verification.
• The OTP doesn't arrive → partial-support countries can fail due to local rules → try a number from a fully supported country. Our guide "Verification code not received" covers the phone side.
• You want SMS login codes → GitLab doesn't offer SMS 2FA → set up an authenticator app or passkey instead.

When GitLab.com asks for a phone number

GitLab's phone step isn't a login method. It's identity verification, scaled to a risk score assigned at sign-up: every account confirms an email, medium-risk accounts also confirm a phone number with a one-time password, and high-risk accounts may be asked for a credit card. Many developers only meet it later, on a free-plan project, when the first pipeline on a GitLab-hosted runner fails with "Identity verification is required in order to run CI jobs".

Clearing that is a short loop: select Verify my account in the banner, enter the number, type the OTP, then push a new commit or re-run the pipeline. GitLab won't accept a number already associated with a banned user.

Country support for GitLab phone verification

GitLab publishes a per-country table, and it decides which number you should pick. Numbers from China, Russia, Pakistan, Bangladesh, Indonesia, Malaysia, Saudi Arabia, the UAE and Vietnam are listed as unsupported. Mexico, Nigeria, the Philippines, Turkey, South Africa and Ukraine are partial, where local rules can stop the OTP. Choose a country that has full support. If none works for you, GitLab offers credit card verification or a support ticket.

• Your sign-in second factor on GitLab is separate: passkeys, OTP authenticator apps, WebAuthn devices or email codes, never SMS.

Verify GitLab with your number in 4 steps

1. 01Choose a country and pick a mobile number.
2. 02Pay in crypto or from your wallet — from $1.80 a month on the yearly plan.
3. 03Enter the number in GitLab with its country code and request the code.
4. 04Open your SMSCreation inbox, copy the code and you're verified.

Tips for GitLab

• Choose a number from a country GitLab doesn't mark Unsupported.
• Select Verify my account in the banner, then re-run the pipeline.
• Use an authenticator app for 2FA; GitLab has no SMS 2FA.

Included with every number

• Unlimited incoming SMS — every verification code and message, no cap
• 500 outgoing SMS every month
• 1,000 outgoing call minutes every month
• Unlimited incoming calls
• Keep the number for as long as you want — auto-renew keeps it yours
• Works with WhatsApp, Facebook, Telegram, Google & Instagram — guaranteed: free replacement or 100% refund within 7 days
• 7-day replacement guarantee — if the number doesn't work with WhatsApp, Facebook, Telegram or Google, we replace it free or refund 100%; plus a no-questions-asked refund if you haven't used it for any call or SMS

Private by design — keep GitLab separate from your identity

A SMSCreation number keeps your personal SIM, name and bank card out of your GitLab account. No KYC, no ID, no card — crypto only.

• No KYC — no ID, passport, selfie or proof of address, ever
• No real name required — sign up with an email and a password
• No card, no bank account — crypto only, so no payment details are linked to you
• No phone number needed to sign up

Popular countries for GitLab numbers

USUnited States+1CACanada+1BRBrazil+55GBUnited Kingdom+44DEGermany+49FRFrance+33NLNetherlands+31ESSpain+34AEUnited Arab Emirates+971INIndia+91SGSingapore+65AUAustralia+61

Keep it as long as you want

GitLab may ask for your number again — on a new phone, after a reinstall or for account recovery. Keep your number renewed and it stays yours, so you can always receive the code.

Not what you needed? Our 7-day replacement guarantee — if the number doesn't work with WhatsApp, Facebook, Telegram or Google, we replace it free or refund 100%; plus a no-questions-asked refund if you haven't used it for any call or SMS.