Stage 1
1. Survey and estimate
We review documents and countries, the number of checks and parallel sessions, information security requirements and how closed the environment is. The result — a configuration for your load.
On-premises installation and private cloud
The NeuroVision platform is installed in your infrastructure: data stays on your servers, and isolated environments without internet access are supported. NeuroVision specialists carry out the installation together with your IT team, updates are agreed with you, and the capabilities are the same as in the cloud.
Your perimeter on-premise
- Documents and anti-fraud runs locally
- Liveness and face matching runs locally
- Customer data inside the perimeter on your servers
- Platform update awaits your approval
- Installation in your infrastructure by NeuroVision and your IT team
- An isolated environment without internet access is supported
- The same capabilities as in the NeuroVision cloud
Data — on your servers Russian Software Registry No. 19972 Working without the internet
What on-premises installation includes: platform modules inside your perimeter
The same platform runs in your infrastructure as in the NeuroVision cloud: the capabilities of the cloud and on-premises are identical. Suitable for banks, government bodies and medical organisations. The scope and parameters of the installation are specified during design.
- OCR API and SDK
Document recognition and anti-fraud
16 000+ document types from 195+ countries and territories: document fields and image checks for editing, photos of a screen and printouts. Images are processed on your servers.
- Liveness
Liveness and face matching
Liveness check and matching a selfie with the photo in the document. The capabilities are the same as in the cloud; images are processed on your servers.
- Catalogue of checks
Database and list checks
The catalogue of AML checks — 24 checks, as in the cloud. How access to external sources is organised in a closed environment is determined during design.
- Documentation
Check scenarios
Steps, documents and data retention period are configured in the scenario: which checks the customer goes through and how long the results are stored — you decide.
- More about the SDK
Web SDK for websites and mobile browsers
The widget is connected with a script or the npm package kyc-widget-nv. In mobile apps — via WebView or the system browser: there are no separate SDKs for iOS and Android.
- API methods
REST API and webhooks
The same capabilities as in the cloud: KYC sessions, AML checks by runId, webhooks. How exactly the integration is moved from the cloud into your environment is agreed during design. Connection to CRM, ERP and 1C — on the page about the KYC module for CRM and ERP.
Your own servers or a private cloud: where to deploy the platform
Both options — inside your perimeter: the platform is installed in the customer's infrastructure. The deployment format, hardware and virtualisation requirements are agreed during design.
Servers in your data centre
the platform is installed by NeuroVision specialists together with your IT team; data stays only on your servers. Hardware is selected for the number of checks and parallel sessions.
Configuration — based on the survey
Your private cloud
the platform can be deployed in an organisation's private cloud: the deployment format, resources and virtualisation requirements are agreed during design with your IT and information security teams.
An isolated environment without internet access is supported
The same capabilities as in the cloud
In the cloud, servers, updates and support are on the NeuroVision side. With on-premises installation, data is only on your servers, and the capabilities of the cloud and on-premises are identical.
What works without the internet and what needs an outbound channel
After installation, checks run locally, and an external network is needed only for updates. How access to external sources for database checks is organised in a closed environment is determined during design together with your information security team.
- Working without the internet
- Checks after installation
- Data
- External network
- Procedure
- Channel
- After the update
- Catalogue
- Access to sources
- Watchlists and sanctions lists
- NeuroVision cloud
- On-premise
- Capabilities
- The scope of database checks is in the catalogue of checks. Which scheme suits your environment is decided during the survey — the first stage of the implementation below.
Who is responsible for what: your team and NeuroVision engineers
In the cloud, NeuroVision runs the infrastructure. In your environment, responsibility is shared: hardware, network and protection are on your side, while installation and platform updates are done together with NeuroVision specialists. The way of working together is set out during design and in the contract.
-
Hardware and environment
Your team. Prepares hardware, network and storage to the parameters agreed during design.
NeuroVision. Selects a configuration for the load — the number of checks and parallel sessions. -
Installation
Your team. The IT team takes part in the installation and accepts the result.
NeuroVision. NeuroVision specialists install the platform and check that it works. If you have an integrator, we involve them: for partner integrators. -
Network and access
Your team. Defines the procedure for access to the servers and decides whether outbound network access is needed.
NeuroVision. Connects over a secure channel at the agreed time. -
Updates
Your team. Agrees the update time and checks the result on its side.
NeuroVision. Notifies you of a new update, agrees the time, connects over a secure channel and checks key functions. -
Data protection
Your team. The personal data operator is you: threat model, protection measures, security level.
NeuroVision. The architecture and components of the platform are described in the documentation. -
Support
Your team. First line within the organisation and monitoring of your own infrastructure.
NeuroVision. The mode and channels of support are set out in the contract; round-the-clock support is added separately. We carry out diagnostics together with your IT team.
How on-premises implementation works: from survey to production
Timelines depend on the readiness of the infrastructure, information security requirements and the number of scenarios — we give them after the survey. The order of stages is the same for own servers and a private cloud.
Stage 2
2. Deployment design
We agree the deployment format — own servers or a private cloud — the update scheme and the procedure for specialist access. We fix the parameters with your IT and information security teams.
Stage 3
3. Infrastructure preparation
Your IT team prepares hardware, network and access according to the agreed procedure. Parameters are selected for the load.
Stage 4
4. Installation
NeuroVision specialists, together with your IT team, install the platform and configure the environment.
Stage 5
5. Acceptance testing
We check that the components work and run the scenarios on your documents. Your information security team checks network interactions.
Stage 6
6. Launch and updates
You put the platform into operation. After that, NeuroVision notifies you of updates, agrees the time, installs them over a secure channel and checks key functions. What has changed — in the changelog.
152-FZ, critical information infrastructure and FSTEC orders: what your information security team should take into account
Installation in your environment does not remove the requirements for your system — it gives you control over how to meet them: where the data is stored, when an update is installed and how a contractor gets access.
Below are the rules that come up most often when a project is agreed with an information security team. The summary is simplified and is not legal advice. Why companies choose local storage — in the article “Cloud vs on-premises KYC”.
- KYC service in Russia
Personal and biometric data
152‑FZ, Art. 11, Part 5 of Art. 18, Art. 19; Government Resolution No. 1119; FSTEC Order No. 21; 572‑FZ, cl. 1 of Part 1 of Art. 15.
What the rule requires
- Databases of Russian citizens' data — in Russia
- The threat model, security level and protection measures — the responsibility of the operator, that is, you
- Face images — only with written consent
- Organisations may not collect and store biometrics for identification outside the Unified Biometric System
What installation in your environment gives you
- Data is processed on your servers
- The retention period is set in the scenario
- The architecture and components of the platform are described in the documentation — for the threat model
- For the public sector
Significant CII facilities
187‑FZ; Presidential Decree No. 166, subpara. “a”, “b” of cl. 1; FSTEC Order No. 239.
What the rule requires
- Since 31 March 2022, customers may not buy foreign software for significant CII facilities without approval
- Since 1 January 2025, public authorities and customers are prohibited from using foreign software at their significant CII facilities
- Application software of a significant facility — subject to the requirements of FSTEC Order No. 239
What to take into account
- The NeuroVision platform is in the Russian software registry, entry No. 19972
- You determine the significance category of the facility
- Installation is carried out in your infrastructure, inside a perimeter that you define
- How implementation proceeds
State information systems and government agency systems
FSTEC Order No. 117 of 11.04.2025, cl. 39, 46, 58, 65 — in force from 1 March 2026 in place of Order No. 17.
Updates
- Only authenticity-verified and tested software, with permission — “uncontrolled installation” is not allowed
- NeuroVision's procedure is as follows: it notifies you of an update, agrees the time, connects over a secure channel and checks key functions
Contractor
- Does not develop or test software in a live system
- Remote access — over channels within Russia, with multi-factor authentication
- The procedure for NeuroVision specialists' access is agreed with you in advance
Certification
- For state information systems — before information processing begins
- For other government agency systems — at the operator's discretion
Load and fault tolerance: how hardware is selected
Hardware for your load
We do not state specific parameters on the page: we select them for the number of checks and parallel sessions during design.
- 01
Sized by load
Hardware is selected for the number of checks and parallel sessions. We calculate the configuration during design.
- 02
Redundancy
Redundancy is recommended for production. We determine the scheme and the make-up of the reserve together with your IT team.
- 03
Load growth
If the load grows, we review the configuration together with your IT team — for the new number of checks and sessions.
- 04
Backups and data
Backups — according to your organisation's rules. The retention period for data and check results is set in the scenario.
- Checks the number of checks is the basis of the estimate
- Sessions parallel sessions determine resources
- Reserve recommended for production
How much on-premises costs: licence, installation and support
We calculate the cost per project: which modules are needed and what load the infrastructure has to handle. Terms are set out in the contract.
Calculate a project- 01
A licence for local installation — by module scope and load
- 02
The mode and channels of support are set out in the contract; round-the-clock support is added separately
- 03
Cloud pricing — per check or as a package: price matrix, KYC session — from 16 ₽
Licences and certificates
The project «Development of a multimodal system using artificial intelligence "Neuromed" for managing the diagnostic processes of a clinic on the basis of the "Neurovision" computer vision platform» is supported by the Innovation Promotion Foundation within the federal project «Domestic Solutions»
The Neurovision computer vision platform is registered with Rospatent (certificate No. 2023661508) and included in the Russian Software Registry (entry No. 19972 of 13.11.2023)
The right to use the Platform is granted under a licence agreement concluded by Neurovision with its customers
Glossary: on-premises, private cloud, CII and certification
- On-premises installation
- The platform runs on the customer's servers, not the vendor's; data and processing stay in the customer's infrastructure.
- On-premises
- Private cloud
- The cloud infrastructure of a single organisation — its own or a dedicated segment at a provider; only the owner has access to the resources.
- Private cloud
- Cloud version
- The platform runs on NeuroVision servers: NeuroVision runs the infrastructure, updates and support.
- Cloud (SaaS)
- Isolated environment
- A network with no internet connection; updates reach it through an agreed procedure.
- Air-gapped network
- Significant CII facility
- A critical information infrastructure facility that has been assigned a significance category under 187‑FZ; FSTEC requirements and restrictions on foreign software apply to it.
- Significant CII object
- The system
- A state information system; information protection requirements for it are set by FSTEC Order No. 117.
- State information system
- Personal data security level
- One of four levels under Government Resolution No. 1119; it determines the set of protection measures for an information system with personal data.
- PII protection level
- Certification
- A check that an information system meets information protection requirements; for state information systems it is mandatory before information processing begins.
- Certification of information system
Read also
Cloud and on-premises KYC, personal data protection, requirements for a KYC provider and customer verification policy — on our blog.
380 23
KYC, AML and Digital Identification
Local or cloud KYC: how to choose a biometric data storage model
384 16
KYC, AML and Digital Identification
How to ensure the protection of personal and biometric data in KYC processes
383 13
KYC, AML and Digital Identification
How to build a KYC policy compliant with Federal Law 115-FZ, Federal Law 152-FZ, FATF and GDPR
114 29
KYC, AML and Digital Identification
115-FZ: What Businesses Are Required to Do and How to Meet the Law’s Requirements
Frequently asked questions about on-premises installation and private cloud
The capabilities of the cloud and on-premises are identical: document recognition, liveness and face matching, database and list checks, KYC scenarios and Web SDK. The exact scope of the installation is specified during design.
In the cloud, the platform runs on NeuroVision servers, data is on the NeuroVision side, and so are updates and support. With on-premises installation, the platform is installed in your infrastructure and data is only on your servers; you prepare the resources for installation and maintenance together with NeuroVision specialists.
No: isolated environments without internet access are supported. After installation, checks run locally, and an external network is needed only for updates. How access to external sources for database checks is organised is determined during design.
Installation is carried out by NeuroVision specialists together with the customer's IT team. For an update, NeuroVision notifies you, agrees the time, connects over a secure channel and checks key functions after the update.
For the load: the number of checks and parallel sessions. Redundancy is recommended for production. Specific parameters are determined during design.
The platform is installed in the customer's infrastructure. The format of private cloud deployment, resources and virtualisation requirements are agreed during design with your IT and information security teams.
For banks, government bodies and medical organisations that need to keep data only on their own servers. You determine the CII facility category and the system class; the rules worth considering are collected on the public sector page.
On your servers. The retention period is set in the scenario, and a session's personal data can be destroyed with the kyc/session/erase method. Processing face images requires the customer's written consent — agree the scenario with your legal team.
The platform's capabilities are identical in the cloud and on-premises. How the integration is moved is agreed during design; the methods are described on the API and SDK page. Connection to CRM, ERP and 1C — on the page about the KYC module for CRM and ERP.
The cost is calculated per project: the scope of modules and the load. The mode and channels of support are set out in the contract, and round-the-clock support is added separately. Cloud pricing is in the price matrix.
Let's discuss installation in your environment
Tell us which checks you need, how many checks and parallel sessions you expect and how closed your environment is. We will propose a deployment scheme and an installation procedure.
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.
