Starting September 1, Netop Self-Hosted Portal gives organizations operating in critical, regulated, or air-gapped environments a way to maintain secure remote access while keeping control of their infrastructure, data, and access operations within their own environment.

A retailer operating within PCI DSS scope needs tightly governed remote access into its cardholder data environment. A healthcare organization subject to HIPAA must protect access to systems containing electronic protected health information. And organizations covered by NIS2 must address access control, supply-chain security, operational resilience, and risks introduced by external service providers. PCI DSS specifically addresses third-party service providers that can access or affect the security of a cardholder data environment; HIPAA requires safeguards including access and audit controls for ePHI; and NIS2 includes supply-chain security, business continuity, and access-control policies among its cybersecurity risk-management measures.

None of these frameworks mandates self-hosting, but all increase the importance of how remote access is architected, governed, audited, and operated.

Netop Self-Hosted Portal is designed to help organizations address these requirements without giving up a modern, portal-based remote access experience. The portal runs inside infrastructure they control, with access policies, audit data, keys, and operational dependencies kept within their chosen boundary.

At the far end of the same spectrum sit fully air-gapped networks: weapons platforms, industrial control systems, power-grid operations, and classified infrastructure, where external connectivity may be unacceptable or impossible by design.

The Access Gap External Dependency Creates

Most remote access tools assume a path to the public internet or externally hosted infrastructure.

For many organizations, that model works well. But for organizations operating under strict security, compliance, data-residency, or infrastructure-control requirements, external dependencies can introduce considerations that need to be carefully managed.

In fully air-gapped networks, the constraint is even clearer: external connectivity may simply not exist.

Yet these organizations still need to troubleshoot endpoints, support operational technology, provide controlled access to specialists and vendors, and recover systems when something goes wrong.

Relying exclusively on physical access can increase response times and operational costs. And introducing an external dependency simply to enable remote support can conflict with the infrastructure model the organization has deliberately put in place.

The challenge is not whether these systems need to be supported. It is how to provide that support while staying within the security and operational boundaries the organization has defined.

Digital Sovereignty Means Control, Not Isolation

Digital sovereignty is not simply the absence of connectivity.

It is the ability to decide where systems run, where data is stored, how access is governed, and which external dependencies an organization is prepared to accept.

Those requirements can arise from compliance obligations, security policies, data-residency requirements, customer requirements, critical infrastructure protections, or the architecture of a fully air-gapped network.

An isolated environment that can only be maintained through physical site visits may remove one form of dependency while creating another: dependence on people being able to reach the system in person.

Sovereign remote access provides another option — giving IT and security teams a way to reach, support, and recover systems using infrastructure that remains within the perimeter and governance model they are responsible for protecting.

Introducing Netop Self-Hosted Portal

Netop Self-Hosted Portal brings the Netop Portal experience into customer-controlled infrastructure.

It is designed for organizations where infrastructure control, data residency, operational independence, or restricted external connectivity are requirements rather than preferences.

The portal is deployed as a containerized instance within the customer’s infrastructure, with sessions kept out of Netop’s shared cloud environment.

No External Connectivity Required at Runtime

Once deployed, day-to-day operation does not depend on external internet connectivity.

For fully air-gapped networks, that means organizations can maintain the isolation of the network while still enabling controlled remote access within it.

For other regulated or security-sensitive environments, it gives organizations greater control over where their remote access infrastructure runs and which external dependencies form part of the architecture.

No Inbound Ports or Direct IP Exposure

Netop Self-Hosted Portal does not require inbound ports or direct IP exposure. Granular, least-privilege access controls are enforced at the architecture level, while session activity can be logged and audited.

This helps organizations maintain control over how remote connections are established and governed without unnecessarily exposing endpoints to external networks.

Organization-Controlled Data and Infrastructure

Organizations retain control over their certificates, keys, storage, and audit data, helping keep the remote access environment within the infrastructure and governance boundaries they define.

For organizations operating under stringent internal policies or external requirements, that control can make it easier to align remote access with their broader security architecture.

Support for Legacy and Embedded Systems

Many highly controlled environments also depend on systems with long operational lifecycles.

Netop Host and Netop OnDemand extend remote support to OT and industrial systems, retail devices such as POS terminals and ATMs, and other legacy or specialized endpoints where standard remote access tools may not be suitable.

Recovery Without Reintroducing External Dependency

Hardware failures inside isolated or tightly controlled environments carry the same operational consequences as failures anywhere else.

A failed POS terminal, an unresponsive kiosk, an industrial endpoint, or a device inside an air-gapped facility may require urgent intervention. Without remote recovery capabilities, sending a technician to the physical location can become the only available option.

Remote control access and One-Click Recovery for supported Intel AMT/vPro devices are native capabilities of Self-Hosted Portal, giving IT teams a way to power-cycle devices, boot into recovery environments, and diagnose supported systems below the operating-system level without introducing an external cloud dependency.

Built for Environments with Stringent Security Requirements

Netop Self-Hosted Portal is built for organizations operating under strict security, compliance, data-residency, and infrastructure-control requirements.

Those requirements differ by geography, industry, and organization. They may be influenced by regulatory regimes and security frameworks such as NIS2 in the European Union, PCI DSS for payment environments, NIST and CMMC requirements in the United States, and the globally recognized ISO/IEC 27001 information security standard. ISO/IEC 27001 defines requirements for an information security management system and is used internationally.

These frameworks do not universally require organizations to self-host remote access infrastructure.

What they do increase is the importance of understanding and controlling how access is granted, how activity is audited, how third-party dependencies are managed, how sensitive systems and data are protected, and how operational resilience is maintained. NIS2, for example, explicitly addresses business continuity, supply-chain security, supplier and service-provider relationships, and access-control policies.

PCI DSS likewise does not prohibit organizations from using third-party service providers. Instead, organizations using providers that support or can affect the cardholder data environment must manage those relationships and understand the responsibilities that remain with each party.

For organizations whose own architecture, policies, risk assessments, or compliance obligations call for greater infrastructure control, Netop Self-Hosted Portal provides an alternative to remote access models that depend on externally hosted infrastructure.

That makes it relevant across industries including retail, financial services, healthcare, defense, government, energy, critical infrastructure, and industrial operations.

The Operational Outcome

Organizations operating under strict security, data-residency, infrastructure-control, or isolation requirements should not have to choose between maintaining control and keeping systems operational.

From September 1, Netop Self-Hosted Portal enables organizations to run the Netop Portal within infrastructure they control — keeping remote access, policy enforcement, auditability, and operational governance aligned with their own security requirements.

For organizations that cannot — or choose not to — depend on Netop’s shared cloud environment, Self-Hosted Portal provides a modern remote access experience while giving them control over the infrastructure on which it operates.

Your infrastructure. Your access. Your control.

Netop Self-Hosted Portal launches September 1.

Explore the Self-Hosted Portal and see how Netop can support secure remote access within your infrastructure.