...

Identifying customers of hosting providers and clouds: passport, company and anti-fraud before a server is issued

A hosting provider may give out computing capacity only after identifying the customer. NeuroVision is built into registration and billing: a passport without manual entry and with a forgery check, Liveness, company by INN, sanctions and lists — for the first order, GPU and large limits.

Hosting customer check before a server is issued: a method from the Rules, passport, Liveness and sanctions lists
from 16 ₽ a passport without manual entry, with anti-fraud
195+ countries and territories — customer documents
24 database checks in the API catalogue
5 ₽ check of a company or a person against one register
Passport without entry Document anti-fraud Liveness Foreign documents Company by tax number Sanctions and watchlists

Russian software register No. 19972 · 152‑FZ

Register, identification and a ban for violators: what the law requires of a hosting provider

All three obligations are in one article of the Information Law. A provider that does not identify customers violates Part 5 of this article — and an uncorrected violation leads to removal from the register, without which it cannot operate.

  • Register of hosting providers

    149‑FZ, Art. 10.2‑1, Parts 1, 6, 8–11 (as amended by 406‑FZ of 31.07.2023).

    Provider checklist

    Notification

    • The provider notifies Roskomnadzor of the start of its activity and is entered in the register
    • As of 8 July 2026 the register contains 584 providers

    Outside the register — not allowed

    • Providing computing capacity to a provider that is not in the register is not permitted

    Removal

    • A violation of Parts 1–5 of the article — a requirement to correct it within up to 10 working days
    • If not corrected — grounds for removal from the register
  • Identification before capacity is issued

    149‑FZ, Art. 10.2‑1, Part 5; Rules approved by Government Resolution of 29.11.2023 No. 2011. In force since 1 December 2023.

    Ten methods

    When

    • Computing capacity — only after identification and/or authentication of the customer
    • Applies to shared hosting, VPS, dedicated servers and cloud

    How

    • One or several of ten methods: Gosuslugi, the Unified Biometric System, an electronic signature, documents in a personal visit, a payment, a card, a phone, the Faster Payments System, the information system of the provider or of a Russian company

    What to store

    • Information on the identification method of each customer
    • For a payment and the Faster Payments System — the date, amount and operation number
  • Whom you must not serve

    149‑FZ, Art. 10.2‑1, Part 5.1 (law of 26.06.2026 No. 210‑FZ), Part 4.1 (law of 01.04.2025 No. 41‑FZ).

    Circumvention schemes

    Ban

    • Capacity must not be provided to owners of networks and resources that have not met the requirements of Art. 15.8 on restricting access to prohibited resources

    What this means

    • A provider must know to whom it gives a server: an anonymous account does not show who owns the resource

    The «Antifrod» state system

    • The provider interacts with the state information system for combating offences in the cases and under the procedure to be set by the Government

VPS, shared hosting, clouds and GPU, resellers, CDN: whom to verify and when

The law requires identification from everyone who provides computing capacity. But the depth of the check depends on what the customer receives: a site on a shared server, root access to a machine or hundreds of GPUs on deferred payment.

  • VPS, VDS and dedicated servers

    • Root access and your own IP address are the main resource for mailings, scanning and DDoS
    • A method from the Rules at registration, passport and Liveness — before the first server or when paying with a new card
    • Re-verification — on an abuse complaint
  • Shared hosting and website builders

    • Mass-market plans, thousands of registrations a day — the check must not break the funnel
    • The basic method is Gosuslugi or phone, a document — when there is risk: a phishing page, someone else's card
    • A company customer — by INN before an invoice with deferred payment
  • Public clouds and GPU

    • Deferred payment, grants and trial credits are a reason to create accounts in batches
    • Passport, Liveness and sanctions — before access to GPU and before raising limits
    • A corporate account — company by INN and a representative under a power of attorney
  • Resellers and partner programmes

    • The end customer is seen by the reseller, not the cloud — identification must be carried out on the reseller's side
    • Reseller — company by tax number, a nominal head and blocked accounts
    • A verification link for the reseller's end customers — without your own development
  • CDN and object storage

    • Storage and CDN distribute files — from malicious builds to phishing kits
    • A method from the Rules — at registration, a document — before public distribution or heavy traffic
    • The resource owner — to respond to regulator requirements
  • Hosting and cloud infrastructure: VPS, clouds, GPU, CDN

Gosuslugi, the Unified Biometric System, signature, payment, phone: ten ways to identify a hosting customer

Rules No. 2011 permit ten methods, and a provider may combine several. Some establish identity, others confirm only the channel — a number or a card. For expensive and risky services, a weak method is worth strengthening with a document check.
Whichever method you choose, information about it is stored for each customer (para. 13 of the Rules). Customers identified no earlier than 1 January 2023 do not have to be re-verified (para. 14).

  • Gosuslugi and the Unified Biometric System

    The customer signs in through Gosuslugi and can pass on their full name, date of birth, passport and registration address. Biometrics — through the Unified Biometric System under Law No. 572‑FZ. A foreigner without an account cannot use this method — they need another method from the Rules.

    • sub-paras. “a”, “b” of para. 2
  • Qualified electronic signature

    The customer sends data signed with a qualified electronic signature: an individual — full name and passport, a sole proprietor — also INN and OGRNIP, a company — name, OGRN and INN. Company by INN NeuroVision checks before the contract.

    • sub-para. “c” of para. 2, para. 6
  • Documents in a personal visit

    An individual — a passport or another document, a sole proprietor — also an entry in the Unified State Register of Individual Entrepreneurs, a company representative — a power of attorney and an entry in the Unified State Register of Legal Entities. A passport at an office or partner point is recognised without manual entry and checked for forgery.

    • sub-para. “d” of para. 2, para. 7
  • Transfer, card and Faster Payments System

    A transfer from an account in a bank of Russia or the EAEU, a one-off card operation (except a prepaid card), a payment through the Faster Payments System. The provider stores the date, amount and operation number. It confirms the payer, not the person who works on the server.

    • sub-paras. “e”, “h”, “k” of para. 2, paras. 8, 10, 12
  • Subscriber number

    A code by SMS or a call to the number of a Russian operator. The most widespread and the weakest method: a SIM card in a front person's name is easier to buy than a passport.

    • sub-para. “i” of para. 2, para. 11
  • Information system of the provider or of a Russian company

    A personal account in the provider's own system, its group's system or the system of a Russian owner. The data set is determined by the system owner. NeuroVision's document and face check is built into your registration system through the Web SDK and API.

    • sub-paras. “f”, “g” of para. 2, para. 9

From registration to the first server: how a provider verifies a customer with NeuroVision

The basic method from the Rules — at registration, without extra steps for an honest customer. The document, Liveness and company check are enabled where risk grows: the first server, a new card, GPU, a large limit.

Step 1

A method from the Rules at registration

The customer registers through Gosuslugi, phone, card or the Faster Payments System — as configured by the provider. The method and the operation data are recorded in the customer card: para. 13 of the Rules requires this.

Registering a hosting customer by a method from Rules No. 2011 and recording the method
Step 2

Document and Liveness by risk

Before the first VPS, GPU access or a limit increase, the customer photographs the passport in the widget and goes through Liveness. Fields arrive without manual entry, and anti-fraud flags a photo of a screen and a printout. A company customer — a check by INN and a representative's session.

Passport and Liveness check before GPU access
Step 3

The decision and the log

The provider sees the result of each check and decides itself whether to issue the resource. The passport number, INN and identification method are stored to respond to requests and to find repeat registrations.

Log of hosting customer checks for the decision to issue resources

Phishing, mailings, DDoS and mining: why a phone and a card are not enough

An anonymous server is a cheap tool of attack

An SMS code and a one-off card operation confirm that the customer has a number and a card. They do not show who will work on the server — which is why abuse comes from accounts that passed formal identification.

  • 01

    Phishing and fraudulent sites

    A “bank” or “marketplace” page lives on shared hosting for a few hours. When a complaint arrives, the account owner turns out to be a front and the payment came from someone else's card.

  • 02

    Mailings and scanning

    A VPS with a clean IP address sends spam and brute-forces passwords. The address ends up on blacklists, and honest customers from the same subnet suffer along with it.

  • 03

    DDoS and botnets

    Dozens of servers for a trial period are created by a batch of accounts from different numbers. A passport and Liveness make the “batch” expensive: every account needs a live person with a document.

  • 04

    Mining on stolen cards

    A GPU is rented with a stolen card, and a month later a chargeback arrives. A document and sanctions list check before a GPU is issued weeds out such orders before the capacity is charged.

  • 10 identification methods in Rules No. 2011
  • 584 providers in the Roskomnadzor register as of 8 July 2026
  • 5–15 % share of foreigners among providers' customers

Hosting customer identification checklist: eight steps before computing capacity is issued

The order in which a provider verifies a new customer. Each line shows who performs the step: NeuroVision, the provider itself or a government system.

  • Choose methods for your plans: Gosuslugi, the Unified Biometric System, signature, payment, card, phone, the Faster Payments System or your own system Provider
  • Sign-in through Gosuslugi and transfer of data with the customer's consent Government system
  • Record the method and, for a payment and the Faster Payments System, the date, amount and operation number Provider

  • A Russian passport or a foreigner's document — a photo in the widget, fields without manual entry NeuroVision
  • Document anti-fraud: a photo of a screen, a printout, a pasted-in photo, traces of editing NeuroVision
  • Validity of a Russian passport against the Ministry of Internal Affairs database NeuroVision

  • Liveness and matching the face against the photo in the document — before GPU, a large limit and a dedicated server NeuroVision
  • Biometrics through the Unified Biometric System — if the provider has connected this method Government system

  • Compare the passport number and INN from the response with the customer database and the list of those blocked for abuse Provider

  • Company by tax number: status, signs of a shell company, courts and debts NeuroVision
  • Nominal head and blocked account operations NeuroVision
  • Representative — their own session with a passport, and a power of attorney to conclude the contract Provider

  • Do not provide capacity to resource owners that have not met the requirements of Art. 15.8 Provider
  • Regulator requirements on resources on your servers — a response based on the data of the identified customer Provider

  • Whether to issue the resource, request the document again or refuse is decided by the provider's employee Provider
  • The data retention period is set in the scenario settings; if refused — delete the data NeuroVision
  • NeuroVision — the step is covered by NeuroVision: document recognition, anti-fraud, Liveness, database checks and company by INN
  • Provider — the provider's own step: choosing the method, comparison with the customer database, the decision to issue the resource
  • Government system — a government system step: sign-in through Gosuslugi and biometrics through the Unified Biometric System

A foreign hosting customer: passport, payment and what happens if only Gosuslugi is left

  • No Gosuslugi account

    Risk. A foreign company or a foreign individual usually has no verified account — the simplest method from the Rules is unavailable to them.

    NeuroVision. Recognises passports and ID cards from 195+ countries and territories, 16,000+ document types, without manual entry of Latin script.

    Provider. Chooses another method from the Rules for foreigners and stores information about it.

  • Payment from a bank outside Russia and the EAEU

    Risk. A transfer and a card count only if the bank is Russian or from the EAEU; a payment from another country is not identification under the Rules.

    NeuroVision. A document and Liveness show who is behind the account; sanctions lists and compliance screening — whether the customer is on any lists.

    Provider. Decides which method from the Rules suits a foreigner and whether prepayment is needed.

  • A personal visit to the office

    Risk. If the rules are cut down to Gosuslugi, the Unified Biometric System and a visit, a foreigner will have only to come with a passport — to the provider's office or to a partner.

    NeuroVision. The passport at the counter is recognised from a photo and checked for forgery, and the fields go into the contract without retyping.

    Provider. Opens reception points or agrees with partners in the required countries.

  • A foreign company

    Risk. A corporate customer from abroad — a representative with a passport and a power of attorney, the company is not in the Unified State Register of Legal Entities.

    NeuroVision. The representative's session with a document and Liveness, OFAC, EU, UK and UN sanctions lists by company name and by individuals.

    Provider. Requests the company's registration documents and confirmation of authority.

In July 2026 the Ministry of Digital Development discussed three methods with providers — Gosuslugi, the Unified Biometric System and a personal visit; no decision had been taken at the date of publication. Follow changes to Rules No. 2011 — we will update this page.

Re-verifying a cloud customer: GPU, limit growth, an abuse complaint and a change of owner

Identification at registration is the minimum required by law. It is worth repeating the check when the cost of a mistake changes: the customer asks for more resources, is the subject of complaints or the account passes to another person.

  • Access to GPU and dedicated servers

    The most expensive resources are most often taken with other people's data. A document, Liveness and sanctions lists — before the first GPU, even if the customer has long been on shared hosting.

  • Limit growth and deferred payment

    The customer asks to raise a limit or switch to pay-as-you-go. A company — by INN, a representative — by passport, before you extend credit.

  • Abuse complaint

    Phishing, a mailing or an attack from the customer's server. Re-checking the document shows whether the account owner exists — the data will be useful for responding to the regulator.

  • Change of account owner

    The account is handed over to another person or company. The new owner goes through identification again, and the method is recorded in the customer card.

Hosting customer checks: catalogue and prices

Each check is enabled separately — by plan and risk. You pay for completed requests; a check for which there was not enough data is not charged. All database checks — in general catalogue.

Individual customer

Passport without manual entry, anti-fraud and live presence.

  • OCR · anti-fraud

    Russian passport recognition

    A Russian passport is recognised from a photo: the fields arrive as a JSON response to the platform.

    from 16 ₽

    Learn more
  • OCR · anti-fraud

    Foreigners' documents: 195+ countries and territories

    A foreign citizen's document is recognised from a photo; the name in Latin script is taken from the machine-readable zone.

    from 16 ₽

    Learn more
  • KYC

    Liveness and matching the face against the document

    A check that a live person is in front of the camera, and matching their face against the photo in the document.

    from 29 ₽ per session

    Learn more
  • Police · SMEV

    Validity of a Russian passport

    The authenticity and validity of a Russian passport through the interagency interaction system. It catches expired, replaced, lost and invalid documents and verifies that the passport was issued to this particular person.

    5 ₽ / check

    Learn more

How much it costs to identify a hosting customer

A fixed price per check, no subscription fee. A mass-market shared hosting plan and a GPU cloud are checked differently — you pay only for the steps you enable.

  • Document

    from 16 ₽ per session

    Calculate

    A Russian passport or a foreigner's document without manual entry, anti-fraud: a photo of a screen, a printout, a pasted-in photo, editing. An additional document in the same session — 10 ₽.

  • Most popular choice

    Document + Liveness

    from 29 ₽ per session

    Enable

    Everything in “Document”, plus Liveness and matching the face against the photo in the document. For VPS, dedicated servers and GPU.

  • Company customer and sanctions

    5 ₽ per check

    Build a set

    Nominal head, blocked accounts, the Rosfinmonitoring list and sanctions — 5 ₽ each. Company by INN — by calculation, compliance screening — 36 ₽.

One session — one person: the company representative goes through their own. The session price falls with volume: at 10,000 checks a year — 18 ₽ by the calculator. A check for which there was not enough data is not charged. Calculator on the pricing page.

Connecting to registration and billing: Web SDK, API or a verification link

The check is built in where the customer already works: registration, the personal account and server ordering. Steps are enabled by scenario rules — a document for the first server, Liveness for GPU.

SDK and widget

The Web SDK is embedded in registration and the personal account with one script or an npm package and works in a mobile browser and WebView — including in the control panel's mobile app. Documentation

  • Web SDK
  • WebView
  • REST API
  • Verification link

Test scenario in the personal account

Payment for completed checks, the data retention period is set in the scenario, support through a ticket system.

Why hosting providers and clouds choose NeuroVision

A provider needs a check that does not drop the conversion of mass-market plans and holds back abuse on expensive resources — and that can be shown to the regulator.

Document, face and company — on one platform

The passport is recognised without manual entry and checked for forgery, Liveness tells a live person from a photo and a screen, and the company is checked by INN. Steps are enabled by risk — an honest customer completes registration without extra screens.

There is no need to assemble a solution from several vendors and reconcile their responses.

Passport Liveness Tax number API

One platform

Document, Liveness, company by INN and lists — through the Web SDK and REST API, without several vendors.

Foreign nationals

Documents from 195+ countries and territories without manual entry of Latin script.

A Russian developer

Register of Russian software No. 19972; personal data — under 152‑FZ.

Liveness

A check that a live person is in front of the camera, and not a photo or a screen.

Hosting provider glossary: computing capacity, register, identification method

A short guide to the concepts found in the law on hosting providers and in the Identification Rules.

Hosting provider
A company or person that provides computing capacity for placing information in a system permanently connected to the internet.
Hosting provider
Computing capacity
Server resources on which a customer hosts sites, services and data: shared hosting, VPS, a dedicated server, cloud.
Computing capacity
Register of hosting providers
A Roskomnadzor list that a provider enters on notification. Operating outside the register is not allowed.
Hosting provider register
Hosting customer identification
Establishing the customer by one of the methods of Rules No. 2011 before they are given computing capacity.
Hosting customer identification
Identification method
One of the ten options in the Rules: Gosuslugi, the Unified Biometric System, an electronic signature, a personal visit, a transfer, a card, a phone, the Faster Payments System, the information system of the provider or of a Russian company.
Identification method
ESIA
The “Gosuslugi” state system, through which the customer confirms identity and, with consent, passes data to the provider.
Gosuslugi (ESIA)
UBS
Unified Biometric System: identification by face and voice under Law No. 572‑FZ.
Unified Biometric System
Identifying operation
A one-off payment from the customer's card, after which the provider considers the information about the payer confirmed.
Identifying transaction
Abuse
Use of the provider's resources for phishing, mailings, attacks and other illegal activity.
Abuse
Liveness
A check that a live person is in front of the camera, and not a photo, a screen, a mask or a deepfake.
Liveness detection

Frequently asked questions about identifying hosting and cloud customers

Yes. Under Part 5 of Art. 10.2-1 of the Information Law, computing capacity may be provided only after the customer is identified and/or authenticated. The procedure is set by the Rules approved by Government Resolution of 29.11.2023 No. 2011; they have been in force since 1 December 2023.

Ten: Gosuslugi, the Unified Biometric System, a qualified electronic signature, documents in a personal visit, a transfer from an account in a bank of Russia or the EAEU, the information system of the provider or of a Russian company, a payment card (except a prepaid one), a subscriber number and the Faster Payments System. Several can be combined.

Roskomnadzor will send a requirement to correct the violation within up to 10 working days. If it is not corrected, the provider may be removed from the register, and operating outside the register is not allowed.

For formal compliance with the Rules — these are permitted methods. But they confirm a number and a card, not a person: for VPS, GPU and large limits, providers add a passport and Liveness check.

Foreigners usually have no Gosuslugi account, and a payment counts only from a bank of Russia or the EAEU. The provider chooses a suitable method from the Rules; NeuroVision recognises documents from 195+ countries and territories and checks the customer against sanctions lists.

NeuroVision works on top of a method from the Rules and strengthens it. How to classify a NeuroVision check under the Rules is for your lawyer to decide.

By INN — status, signs of a shell company, courts, debts, nominal head and blocked accounts. The representative goes through their own check with a passport and confirms authority with a power of attorney.

If the customer was identified by one of the methods of the Rules no earlier than 1 January 2023 — no. Re-verification is still justified for GPU access, limit growth and an abuse complaint.

The Web SDK for the website and personal account works in a mobile browser and in a WebView inside the app; for server-side integration there is the REST API. You can also send the customer a unique verification link.

The retention period is set in the scenario settings, and data can be deleted. Where the servers are located and how personal data is processed is defined by the contract. The provider stores the information about the identification method itself.

No, these are different rules. Here — hosting providers and Art. 10.2‑1; administrators of .ru and .рф domains are identified by registrars under their own rules.

A passport with anti-fraud — from 16 ₽ per session, with Liveness — from 29 ₽, database and sanctions list checks — 5 ₽ each, a company check by INN — by calculation. No subscription fee. A test is available in the test scenario of the personal account.

We will select checks for your hosting or cloud

Tell us which services you sell, how many customers register per month, which methods from the Rules you already use and whether you have foreign customers. We will propose a scenario by risk and set up test access.

Can't put your request into words? Book a call and our team will contact you at a convenient time

Book a call

The company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.

Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.