Compliance · 12 min read

Video wall software and Russian import substitution: the Минцифры registry, FZ-187, and КИИ compliance

Last updated: 2026-05-23

For a Russian control-room video wall in 2026, import substitution is not a slogan on a slide — it is a procurement gate. This article maps what actually qualifies: the Минцифры software registry, the FZ-187 critical-infrastructure law, КИИ obligations, and the registry-listed platforms a buyer can realistically choose from today.

What "import substitution" means here

Import substitution (импортозамещение) for software is the policy of replacing foreign products with Russian-developed equivalents in state and critical-infrastructure systems. For video wall software it works through three separate mechanisms, and confusing them is the most common procurement mistake:

  • The Минцифры software registry — the Единый реестр российского ПО. Listing makes software eligible for the procurement preference under 44-FZ and 223-FZ.
  • FZ-187 / КИИ — the critical-information-infrastructure law. It governs security architecture, not vendor nationality directly, though in practice the two overlap.
  • Organisational mandates — large SOEs and banks run their own import-substitution programmes that may be stricter than the federal baseline.

The Минцифры registry

The Единый реестр российского ПО (reestr.digital.gov.ru) is maintained by the Ministry of Digital Development. To be listed, software must be owned by a Russian-domiciled rights holder, with the source under Russian control and royalty outflow abroad below a threshold. Once listed, a product gains the procurement preference: a 44-FZ buyer must choose registry software when a registry equivalent of the needed class exists, and can justify foreign software only by documenting the absence of an equivalent.

For video wall software, registry equivalents now exist — which means the "no equivalent" justification no longer holds for a government buyer. The registry is searchable; the listing for any given product can be added, suspended, or have its declared class adjusted, so the registry entry must be re-checked at tender time rather than assumed from a vendor claim.

FZ-187 and КИИ obligations

FZ-187 — the 2017 law on the security of critical information infrastructure — applies when the video wall is part of a КИИ object: a telecom NOC, an energy dispatch centre, a transport control room, a banking operations centre. The wall does not get categorised on its own; it inherits the significance category of the object it serves, and with it the security requirements.

In practice that means the wall software must run fully on-premises, must not carry undocumented outbound network dependencies, must survive an internet disconnection without losing operator function, and must fit the object's incident-reporting integration with ГосСОПКА. A cloud-managed video wall fails this filter by construction — which is why the hybrid-cloud and pure-cloud architectures common in Western ProAV do not transfer cleanly into Russian КИИ deployments.

Registry-listed options today

As of 2026, the Russian-registry options for control-room visualization software:

  • Polywall (Polymedia) — video wall software with a long government channel, paired with the PolyWall controller hardware. Deep federal and regional installed base.
  • Forsite MWCC — Forsite M-Wall Control Center, software for Forsite's controller hardware, with explicit Astra Linux support and a 16K-canvas / 32-display ceiling.
  • BridgeWall — a registry-listed video wall management option positioned for КИИ procurements.
  • SmartPlayer — a registry-listed platform whose core is digital signage; it covers basic video-wall content display but is a different category from operator-driven control-room composition.

The честный read: Polywall and Forsite MWCC are the two genuine registry-listed control-room video wall platforms; BridgeWall is a third; SmartPlayer is registry-listed but solves the signage problem, not the operator-composition problem.

Where Craft Wall stands

Craft Wall is Russian-developed video wall software. Its Минцифры registry application is in preparation; until that listing is granted, a procurement that mandates a registry entry today should specify one of the already-listed platforms above, or confirm Craft Wall's current registry status directly before relying on it.

Architecturally Craft Wall fits the КИИ filter — it runs fully on-premises on commodity Linux, is air-gap-compatible, and carries no required outbound dependency. The distinguishing choices versus the registry incumbents are the same ones that decide any video wall bake-off: a published flat perpetual licence instead of quote-only pricing, IP-source-native ingestion instead of capture-card BOM growth, and hardware-agnostic deployment instead of being tied to one vendor's controllers.

How to choose

Decision order for a Russian control-room video wall procurement:

  • Is it a 44-FZ / КИИ procurement? If yes, the shortlist must be registry-listed platforms today — confirm each entry on reestr.digital.gov.ru.
  • Is it commercial / non-КИИ? The choice is open: registry status is a preference, not a gate, and the decision returns to TCO, source-mix, operator UX, and support continuity.
  • Then run the normal bake-off. Registry eligibility narrows the shortlist; it does not pick the winner. Score the survivors on the six standard criteria.

Frequently asked questions

Which video wall software is in the Минцифры registry?

As of 2026 the registry-listed options for control-room video wall and adjacent visualization software include Polywall (Polymedia), Forsite MWCC (M-Wall Control Center), BridgeWall, and the SmartPlayer digital-signage platform. The registry changes — always confirm the current entry on reestr.digital.gov.ru before relying on it in a tender, because listings can be added, suspended, or have their scope adjusted.

Is registry software mandatory for a government video wall procurement?

For procurements under 44-FZ and many under 223-FZ, Russian registry software gets a procurement preference and foreign software is restricted when a registry equivalent exists. It is less an absolute ban than a default: a buyer can justify foreign software only by documenting the absence of a registry equivalent. Since registry equivalents for video wall software now exist, a government buyer practically must choose from the registry.

What does FZ-187 require for a video wall on a КИИ facility?

FZ-187 governs critical information infrastructure (КИИ). If the video wall is part of a КИИ object's monitoring or dispatch loop, it inherits the object's significance category and the matching security requirements: controlled software supply chain, no undocumented outbound dependencies, ability to operate air-gapped, and incident-reporting integration with GosSOPKA. The practical filter: the wall software must run fully on-prem and survive a hard internet cut without losing operator function.

Can foreign video wall software still be used in Russia?

In the commercial (non-state, non-КИИ) sector, yes — there is no blanket ban, and foreign platforms like Userful, Hiperwall, Datapath or Barco are still deployed. The constraints bite in three places: government / 44-FZ procurement, КИИ objects under FZ-187, and organisations with their own import-substitution mandate (large SOEs, banks). Outside those, the choice is open — though sanctions have made support, licensing renewal, and updates from some foreign vendors practically difficult since 2022.

How does an import-substituted video wall differ technically from a foreign one?

Less than marketing implies. The strong Russian video wall platforms run the same architecture as Western ones — software on Linux (often Astra Linux for КИИ), web or desktop control UI, IP and capture-card sources, REST APIs. The real differences are organisational, not technical: a Russian-domiciled vendor, source control inside Russia, registry listing, and a support contract that cannot be severed by sanctions. The procurement chooses on those axes plus the usual ones — TCO, source-mix coverage, operator UX.

Related reading