0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SSH Communications Security Oyj · ssh.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
PrivX at a glance
- Vendor
- SSH Communications Security Oyj
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates PrivX 2.5/5, the mean of 6 judges. PrivX, a just-in-time privileged access product from SSH Communications Security Oyj, scores best where access follows identity: identity and policy runs 5 to 7 — the only criterion to reach 7 — crediting zero-standing-privilege certificate access granted per task, per-user multi-factor with one-time passwords, biometrics and security keys, and conditional access on location and device type. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
PrivX, a just-in-time privileged access product from SSH Communications Security Oyj, scores best where access follows identity: identity and policy runs 5 to 7 — the only criterion to reach 7 — crediting zero-standing-privilege certificate access granted per task, per-user multi-factor with one-time passwords, biometrics and security keys, and conditional access on location and device type. Visibility and audit follows at 5 to 6 on session recordings, audit trails and real-time RFC-3164 syslog forwarding to a SIEM. The real split is access and connectivity, 4 to 6: judges crediting the per-resource, just-in-time model scored it high, while those weighing undocumented client platforms, gateways and split tunnelling held it at 4. Architecture and assurance splits 4 to 6 the same way — the FIPS 140-3 certificate (SSH Communications Security Cryptographic Module #5020) satisfies some judges; others note no status page, SLA or penetration-test reports. Sovereignty spans 0 to 3, with two judges recording no public information to score on. Deployment and administration holds at 4 to 4. No prices are public — only a free trial, a demo and a subscription note.
Speaks for it
- Just-in-time, certificate-based access granted per task to vendors and contractors, eliminating standing credentials and shared accounts.
- Per-user multi-factor authentication with one-time passwords, biometrics, security keys and authenticator apps, assigned in the PrivX Management Console.
- Session recordings, access logs, audit trails and real-time forwarding to a SIEM over RFC-3164 syslog and SNMP, with HIPAA, PCI DSS and SOX cited.
- FIPS 140-3 certification of the cryptographic module (SSH Communications Security Cryptographic Module #5020) through the CMVP programme, aligned with ISO/IEC 19790.
- Containerized deployment at a reported 100,000-server customer scale and an on-premises option on Nokia Industrial Edge (MXIE).
Held against it
- No public information on client applications per platform, gateway or relay locations, or split tunnelling.
- No public information on named identity providers, SCIM or directory-based deprovisioning, or device posture checks from EDR or MDM tools.
- No public information on log retention periods, an administrator audit log of configuration changes, or what traffic content is recorded.
- No public information on a documented REST API, MDM-based client rollout, administrator roles, or support response times.
- No public information on where account data, identities and connection logs are stored or processed, on subprocessors, or on a published data processing agreement.
Best for
- You grant vendors and third-party contractors temporary access to operational technology — per-task just-in-time access, protocol-agnostic connections and site-specific approvals are the core of the pitch.
- You need audit evidence for compliance regimes — session recordings, audit trails and real-time RFC-3164 syslog forwarding, with HIPAA, PCI DSS and SOX cited.
- You are a managed service provider — the vendor names MSPs among its target audiences and industries.
- You require independently validated cryptography — the FIPS 140-3 certificate SSH Communications Security Cryptographic Module #5020 through CMVP, aligned with ISO/IEC 19790.
Avoid if
- You need to budget from public prices — the captured pages show only a free trial, a demo booking and a note that a valid subscription is required for full functionality.
- You need whole-network access rather than per-task grants — the pages describe access granted per host and per task, with no public information on client platforms or split tunnelling.
- Your procurement must verify data residency, subprocessors and a data processing agreement before shortlisting — the captured pages give no hosting or processing facts for PrivX itself.
- You expect site-to-site quantum-safe encryption inside the same purchase — the pages list NQX as a separate product line.
The scores
| Criterion | Panel median |
|---|---|
| Access model & connectivity | 2 of 5 |
| Identity, access policy & device posture | 3 of 5 |
| Logs, audit trail & incident response | 3 of 5 |
| Deployment, API & administration | 2 of 5 |
| Architecture, reliability & security assurance | 2.5 of 5 |
| European sovereignty | 1.5 of 5 |
Access model & connectivity
Show reasoningHide reasoning
How this is scored
What the product connects and how: a managed gateway VPN with shared or dedicated gateways and dedicated static IPs, a peer-to-peer mesh between devices and servers, access per application or resource (ZTNA), site-to-site links between offices and cloud networks (AWS, Azure, Google Cloud), connectors behind a firewall without inbound ports, the protocols (WireGuard, IPsec, OpenVPN, a vendor protocol), split tunnelling and full tunnelling, always-on and auto-connect, clients for Windows, macOS, Linux, iOS, Android and ChromeOS, the gateway and relay locations, NAT traversal and relays, and access for contractors without a managed device.
0 — Gives no remote access of its own; a browser extension, a consumer VPN for anonymous browsing or a security tool that only filters traffic.
3 — A VPN client that connects users to one gateway or network; site-to-site, per-resource access, the clients per platform and the locations are basic or not described.
5 — Clients for Windows, macOS, Linux, iOS and Android, a modern protocol (WireGuard or IPsec), access to private networks through a gateway or connector without inbound firewall rules, split tunnelling, dedicated static IPs or self-run gateways, site-to-site or cloud network links, and the gateway or relay locations named.
8 — Access per application or resource rather than whole networks, peer-to-peer connections with relays as fallback, always-on and auto-connect, connectors for the major clouds and Kubernetes, gateways in many named regions, private DNS and split DNS, clientless browser access for contractors, and the protocol and encryption choices documented.
10 — Connectivity a distributed company runs on: every access model above in one product, high-availability gateways and connectors with failover documented, performance and throughput published per gateway type, post-quantum or equivalent key exchange documented, and an exit path to run the same network on self-hosted components.
The IT Lead
The pages describe just-in-time, protocol-agnostic remote access for vendors and contractors with granular per-task controls, a browser-based sign-on experience, and encrypted connectivity between sites. For a fleet of managed laptops I would need client platforms, split tunnelling, a dedicated static IP for the supplier portal and gateway locations, and we found no public information on any of these. 1 4 6
The DevOps Engineer
What the pages document is a just-in-time privileged access broker: ephemeral certificate-based access to infrastructure, protocol-agnostic OT connections, secure file transfers, quantum-safe encrypted connectivity between sites, and a browser-based experience with single sign-on for vendors and contractors. We found no public information on a peer-to-peer mesh, gateway or relay locations, client platforms, split tunnelling, or connectors that reach servers without inbound firewall rules, so I cannot treat it as a full connectivity layer for my Hetzner fleet and Kubernetes cluster. As a per-target access path with approvals it sits above a single-gateway VPN client but well short of the mesh model I would run on. 1 4 6
The MSP Technician
Just-in-time certificate access to infrastructure, protocol-agnostic OT connections, vendor remote access and site connectivity through PrivX and NQX are documented, so this is a genuine access product rather than a filter. But we found no public information on per-platform clients, the access protocol, gateway or relay locations, or split tunnelling, which is the plumbing I would need before quoting a client. 1 3 4
The Operations Manager
The captured pages show just-in-time remote access aimed squarely at vendors and third-party contractors, with granular per-task controls, protocol-agnostic connections and a browser-based single sign-on experience — the right shape for letting a freelancer reach one project system. We found no public information on client applications per platform, gateway or relay locations, split tunnelling, or site-to-site and cloud network links. 1 3 4 6
The Information Security Officer
The captured pages show access granted per task and per resource rather than per network: just-in-time vendor and contractor access with granular controls, protocol-agnostic connections into operational technology with site-specific approvals, and a browser-based single sign-on experience. We found no public information on client platforms per operating system, the tunnelling protocol, gateway or relay locations, or links into cloud networks, so the connectivity plumbing cannot be assessed beyond the access model itself. 4 6 1
The Skeptic
Access is granted per host and per task rather than to a whole network: just-in-time, certificate-based, browser-based sessions with protocol-agnostic connections, secure file transfers, and contractor access tailored to a specific task. We found no public information on client platforms, gateway or relay locations, split tunnelling, or site-to-site links — the site-to-site quantum-safe story on these pages belongs to a separate product, NQX. A real per-resource model with the network fabric undocumented. 1 3 4 6
Identity, access policy & device posture
Show reasoningHide reasoning
How this is scored
Whether access follows identity and the state of the device rather than the network: single sign-on with Microsoft Entra ID, Google Workspace, Okta or any OIDC/SAML provider, SCIM or directory sync so a leaver loses access, multi-factor authentication, groups and per-resource access policies, least-privilege defaults, device posture checks (operating system version, disk encryption, EDR or MDM status, managed device certificates), just-in-time or time-limited access with approval, session lifetimes and re-authentication, and access revoked when a device is lost.
0 — No user identity at all; a shared key or configuration file grants access to the whole network.
3 — User accounts with a password or one identity provider; groups, per-resource policies and device checks are basic or not described.
5 — Single sign-on with Entra ID, Google Workspace and Okta, multi-factor authentication, user groups, access policies that restrict groups to named networks, resources or ports, automatic or SCIM-based deprovisioning, and basic device posture checks such as operating system version.
8 — SCIM provisioning from the major identity providers, per-resource policies with least privilege by default, device posture from EDR or MDM tools (for example CrowdStrike, SentinelOne, Intune, Jamf), just-in-time access with approval and expiry, session re-authentication, policies kept as code, and the policy model documented.
10 — Access control a security team can audit and trust: continuous evaluation of identity and device state during a session, policies tested before they apply, emergency revocation documented, device identity bound to hardware, and the decision for every connection explainable from the logs.
The IT Lead
Multi-factor authentication is well documented — per-user assignment, console configuration, methods from one-time passwords to NFC security keys — alongside conditional access on location and device type and identity-based just-in-time access with least privilege. Single sign-on is mentioned but the identity providers are not named, so I cannot confirm Entra sign-in, and we found no public information on SCIM or directory-based deprovisioning that would cut a leaver off the same day. 4 5 6
The DevOps Engineer
This is where the evidence is strongest: least-privilege, identity-based, policy-driven access granted only when needed with standing credentials eliminated, certificate-based authentication, single sign-on, and MFA spanning OTP, biometrics, security keys and authenticator apps, plus conditional access on location and device type. We found no public information on named identity providers or SCIM deprovisioning, device posture from EDR or MDM tools, or policies kept as code — and policies in Git applied with Terraform is my deciding question, so it stays below the top band. 4 5 6
The MSP Technician
Multi-factor authentication is documented in detail — OTP, biometrics, security keys, per-user assignment in the management console, recovery codes — alongside policy-driven just-in-time access, least privilege and conditional access on location and device type. Single sign-on is mentioned, but we found no public information on named identity providers, SCIM or directory-based deprovisioning, or device posture from EDR or MDM tools. 4 5 6
The Operations Manager
Access follows identity rather than the network: multi-factor with OTP, biometrics and security keys assigned per user, conditional access on location and device type, and ephemeral just-in-time certificates that exist only for the task at hand — the pattern I need so a contractor's access ends with the contract. We found no public information on which single sign-on providers are supported, directory sync for removing leavers automatically, or device posture checks from EDR or MDM tools. 4 5 6
The Information Security Officer
Identity-based, policy-driven just-in-time access with zero standing privileges, certificate-based authentication, least privilege for vendors and contractors, and site-specific approvals are documented, along with MFA assigned per user in the console using one-time passwords, biometrics and security keys. The only device evidence is conditional access on location or device type; we found no public information on posture checks from EDR or MDM tools, SCIM-based deprovisioning, or named single sign-on providers, which is what I would require before an endpoint touches the control network. 6 5 4
The Skeptic
Identity clearly drives access: single sign-on with a browser-based experience, multi-factor authentication with a long list of methods assigned per user, identity-based just-in-time grants that eliminate standing credentials, site-specific access approvals, and conditional access on location or device type. We found no public information on which identity providers are supported, on SCIM or directory sync so a leaver actually loses access, or on device posture beyond device type. The approval and zero-standing-privilege model is genuinely above mid-level; provisioning sync and posture depth are a blank. 4 5 6
Logs, audit trail & incident response
Show reasoningHide reasoning
How this is scored
What can be seen and proven afterwards: connection and access logs (who reached which resource from which device, when), admin and configuration audit logs, how long logs are kept per plan, log export and streaming to a SIEM (Splunk, Microsoft Sentinel, Datadog, an S3 bucket), alerts on unusual access, a view of active sessions and the ability to end them, DNS logs where DNS filtering is part of the product, and what the vendor states it does not log, such as the content of traffic.
0 — No logs of any kind; the admin cannot see who connected.
3 — A list of connected users or devices; access logs, admin audit logs, retention and export are basic or not described.
5 — Connection or access logs per user and device, an admin audit log of configuration changes, the retention period stated, log export by CSV or API, a view of active sessions or devices with the option to disconnect or revoke them, and a statement of what traffic data is and is not logged.
8 — Log streaming to named SIEM tools, network flow logs per resource, retention of a year or more stated per plan, alerts or webhooks on security events, logs filterable by user, device and resource, and the log schema documented.
10 — An audit trail that holds up in an investigation: every access decision and admin action recorded with its policy and reason, logs signed or tamper-evident, evidence suitable for ISO 27001, NIS2 or DORA audits, full export in an open format, and the customer able to keep logs entirely on its own infrastructure.
The IT Lead
Session logs, access logs, audit trails and session recordings with real-time monitoring are described, and logs can be forwarded in real time to a SIEM over RFC-3164 syslog, which suits our audits. We found no public information on retention periods, an admin audit log of configuration changes, or a statement of what traffic data is not logged. 3 4 7
The DevOps Engineer
Session logs, access logs, audit trails and session recordings are documented, with real-time session monitoring and forwarding of these logs to SIEM over RFC-3164 syslog and SNMP trap messaging for correlation against HIPAA, PCI DSS and SOX requirements. We found no public information on retention periods per plan, an admin audit log of configuration changes, or a documented log schema, so it reads as strong monitoring rather than an investigation-grade trail. 7 8
The MSP Technician
Audit trails, session recordings, real-time session monitoring and real-time forwarding to a SIEM over RFC-3164 syslog and SNMP are documented, which is the evidence I want to show a client after an incident. We found no public information on retention periods, an admin configuration audit log, a documented log schema, or what traffic data is not logged. 3 4 7 8
The Operations Manager
Session recordings, access logs and audit trails with real-time session monitoring are described, and logs can be forwarded to a SIEM in real time over RFC-3164 syslog — enough to prove afterwards which freelancer touched which system. We found no public information on retention periods, an admin audit log of configuration changes, or export formats beyond syslog. 4 7 8
The Information Security Officer
Session recordings, access and session logs, audit trails and continuous session monitoring are documented, with real-time forwarding to a SIEM over RFC-3164-compliant syslog, and the vendor cites SIEM-driven compliance with HIPAA, PCI DSS and SOX — the kind of evidence trail my auditor asks for. We found no public information on retention periods, a separate audit log of administrator configuration changes, or a statement of what traffic content is and is not recorded. 7 4
The Skeptic
Session logs, access logs, audit trails, session recordings, continuous session monitoring, and real-time forwarding to a SIEM over RFC-3164 syslog are all on the record. We found no public information on retention periods, named SIEM destinations, an admin audit log of configuration changes, a live view of sessions an operator can terminate, or any statement of what traffic data the product does not log. For a vendor claiming complete auditability, how long the evidence survives is the question these pages never answer. 4 7 8
Deployment, API & administration
Show reasoningHide reasoning
How this is scored
How the product is rolled out and run by a small IT team or a service provider: time to the first connection, deployment of clients through MDM (Intune, Jamf, Kandji) with preconfigured settings, a central admin console, a documented REST API, a Terraform provider or configuration as code, roles for administrators, several teams, sites or customer tenants in one account, a multi-tenant console for managed service providers, a self-hosted or on-premises edition, the update process for clients and gateways, and support channels and hours.
0 — No central administration; every client is configured by hand with no console.
3 — A web console to add users and gateways; the API, MDM deployment, admin roles and multi-tenant set-up are basic or not described.
5 — A central admin console, a documented REST API, client deployment through MDM with preconfigured settings, admin roles, several networks or sites in one account, client updates managed centrally, and support channels and response times stated per plan.
8 — A Terraform provider or configuration as code, a multi-tenant console for service providers or several organisations, granular admin roles, a self-hosted or on-premises edition documented for production, gateways deployable as containers or cloud images, and webhooks or integrations with ticketing and chat tools.
10 — Administration that scales across many sites and tenants: every setting reachable by API and code with parity stated, staged rollouts of client and gateway updates, a self-hosted edition with feature parity stated, reseller or MSP billing per tenant, and an exit path for configuration and users documented.
The IT Lead
There is a PrivX Management Console for user management and security settings, containerized deployments at very large scale, an on-premises option through the Nokia Industrial Edge platform, and clear positioning for managed service providers. For a three-person team the gaps matter: we found no public information on client deployment through Intune or other MDM, a documented REST API, admin roles, or support response times. 5 6 9 10
The DevOps Engineer
There is a PrivX Management Console with a user management section and security settings for MFA, container-based deployments are announced with a customer managing 100,000 servers in a containerized environment, an on-premises option exists via the Nokia Industrial Edge platform, and managed service providers are a named audience. We found no public information on a REST API, a Terraform provider or other configuration-as-code, MDM rollout of clients, or granular admin roles, and for my team the Terraform question decides this. 5 10
The MSP Technician
A management console with user management, containerized deployments, an on-premises option on the Nokia Industrial Edge platform and explicit managed-service-provider positioning are all documented, which speaks to my shop directly. But we found no public information on a documented REST API, MDM-based client rollout, admin roles, or a per-client tenant structure, so I cannot yet see thirty customers living in one console. 5 6 9 10
The Operations Manager
A management console handles per-user administration, deployment is offered in containers and on an on-premises compute platform (Nokia Industrial Edge), and the product is pitched at managed service providers — the sort of external partner I depend on. We found no public information on a documented REST API, client rollout through MDM with preconfigured settings, administrator roles, or support channels with response times. 5 6 9 10
The Information Security Officer
A PrivX Management Console with user management and security settings is documented, an on-premises deployment on the Nokia Industrial Edge compute platform exists for operational technology, and a free trial, demo booking, support site and product documentation are offered. We found no public information on a documented REST API, client deployment through MDM, administrator roles, multi-tenant operation for service providers in practice, or support response times. 5 10 4
The Skeptic
There is a management console for users and security settings, containerized deployment at scale — one customer reportedly runs 100,000 servers — availability on the Nokia Industrial Edge on-premises compute platform, and a free trial with product documentation and a support site. We found no public information on a documented API, configuration as code, MDM client rollout, administrator roles, or support response times. An MSP-targeted product whose multi-tenant administration is never described is a gap a buyer will pay for. 5 6 9 10
Architecture, reliability & security assurance
Show reasoningHide reasoning
How this is scored
How the product is built and how its claims are proven: a published architecture showing what the coordination servers, relays and gateways see, whether traffic passes through the vendor or end to end between devices, encryption and key management, open-source clients or servers, independent security audits and penetration tests with reports or summaries published, a vulnerability disclosure or bug bounty programme, high availability and failover of the vendor's control plane, what happens to existing connections when the vendor's service is down, the vendor's own public status page and incident history, and an SLA.
0 — Nothing is published about how the product works or is secured.
3 — Encryption is mentioned in marketing terms; architecture, audits, availability and the vendor's status page are basic or not described.
5 — An architecture overview of clients, gateways and the control plane, the encryption protocol and key handling named, an independent security audit or penetration test stated, a vulnerability disclosure contact, the vendor's public status page, and an availability SLA on the business plans.
8 — A security whitepaper with the data flow and what the vendor can see, open-source clients or core components, audit or pentest reports or summaries published by the auditor, a bug bounty, high availability of the control plane documented, existing connections kept alive when the control plane is down, and the incident history public with post-mortems.
10 — Assurance a regulated buyer can verify: fully open-source and reproducible components, recurring independent audits published in full, the control plane self-hostable with no call home, a documented failure mode for every vendor component, and several years of availability published.
The IT Lead
The cryptographic module carries a FIPS 140-3 certificate through the CMVP programme, quantum readiness runs through the product claims, and a scalable microservices architecture is described. We found no public information on a published architecture with data flows, a vendor status page, an availability SLA, or independent product-level audit reports. 1 3 11
The DevOps Engineer
The FIPS 140-3 certification (Cryptographic Module #5020 through CMVP, aligned with ISO/IEC 19790) is concrete, independently validated assurance on the cryptography, beyond marketing terms, and quantum-safe claims recur across the pages alongside a scalable microservices architecture. We found no public information on a published architecture showing what the vendor's coordination components can see, control-plane high availability or failover, a public status page with incident history, an SLA, or a vulnerability disclosure route — which is exactly the architecture disclosure I ask a vendor for. 11 6 1
The MSP Technician
A FIPS 140-3 certification of the cryptographic module through the US-Canadian CMVP programme is a genuinely independent validation, and quantum-safe cryptography, a microservices architecture and an immutable architecture are stated. We found no public information on a published architecture with data flow, product security audits, a bug bounty, a status page or an availability SLA, so reliability claims are not evidenced. 1 3 11
The Operations Manager
The cryptography carries genuine independent validation — FIPS 140-3, certificate number 5020, through the US-Canadian Cryptographic Module Validation Program — alongside named quantum-safe key handling and a scalable microservices architecture. We found no public information on a published data-flow architecture, the vendor's status page and incident history, an availability SLA, or a vulnerability disclosure programme. 1 3 11
The Information Security Officer
The cryptographic module carries a FIPS 140-3 certificate (SSH Communications Security Cryptographic Module #5020) validated through the joint US NIST and Canadian CMVP programme, which is an independent validation of the cryptography, and quantum-safe encryption, a scalable microservices architecture and an immutable architecture are claimed. We found no public information on a security whitepaper showing data flow and what the vendor can see, published penetration test reports, a vulnerability disclosure contact, a public status page with incident history, or an availability SLA. 11 1 6
The Skeptic
The one hard, checkable claim is FIPS 140-3 certification of the cryptographic module through the joint US NIST and Canadian CMVP program, certificate number 5020 — independent, published validation, alongside quantum-ready cryptographic claims and an immutable microservices architecture. We found no public information on a published architecture showing what the coordination components can see, on audit or penetration test reports, a bug bounty, a status page, an SLA, or what happens to existing sessions if the vendor's own service is down. One real certificate does not substitute for the rest of the assurance chain. 3 6 11
European sovereignty
panel opinion
n/r
n/r
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, user and device identities, connection logs and configuration are stored and processed, which party runs the coordination servers, relays and gateways the traffic passes through, and who the subprocessors are (hosting, identity, email, support and payment tools). Independently sourced by the sovereignty pipeline. Gateway and exit locations outside Europe are part of what the product does and are not counted against it; where the logs and identities are stored and who processes them is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting of the control plane and logs unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but the location of the control plane and logs is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting of logs and account data available and an EU contracting entity or EU representative, but parts of the chain (relays, support, identity, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure for the control plane and logs, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record and connection on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The IT Lead
Press releases are issued from Helsinki and the vendor announces a partnership to bolster European data sovereignty, which gives a European seat. We found no public information on where account data, identities and connection logs are stored and processed, the subprocessors involved, or a data processing agreement. 10 11
The DevOps Engineer not rated — no public information
Every sovereignty dimension is recorded as unknown — legal entity jurisdiction, data residency, hosting options, open source, data processing agreement — and the pages I read state nothing about where PrivX's control plane, identities or connection logs are stored or who processes them. A Helsinki dateline on a press release and a partner announcement about European data sovereignty are not statements about PrivX's own chain, so I found no public information to score here. 10 11
The MSP Technician not rated — no public information
We found no public information on where PrivX account data, identities, connection logs and configuration are stored or processed, on the contracting entity's jurisdiction, hosting options, subprocessors or a data processing agreement. The captured pages offer only a Helsinki press-release dateline and a partnership described as bolstering European data sovereignty, with no hosting or processing facts for PrivX itself. 1 2 10 11
The Operations Manager
The press release is issued from Helsinki under the Finnish public-company form, and an on-premises option exists on Nokia Industrial Edge, which would keep records on our own European servers. We found no public information on where account data, identities and logs are hosted in the standard edition, the subprocessors involved, or a published data processing agreement. 10 11
The Information Security Officer
The press release is datelined Helsinki, Finland and the vendor is a Finnish public company, an on-premises option on Nokia Industrial Edge would keep operational records on our own servers, and a partnership with Intragen is announced to bolster European data sovereignty. Beyond that we found no public information on where account data, user identities, connection logs and configuration are stored and processed, on a published data processing agreement, or on the subprocessors and their locations — for an energy supplier under NIS2 that silence is the deciding fact. 11 10
The Skeptic
Press releases are datelined Helsinki, Finland, the vendor announces a partnership it says will bolster European data sovereignty, and a sibling product line claims full data sovereignty — but these are words, not locations. We found no public information on where account data, user identities or connection logs are stored and processed, who runs the servers the traffic passes through, or a published data processing agreement and subprocessor list. A European dateline is not a European data chain. 4 10 11
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or per device and tier, minimum seats, what dedicated gateways, static IPs, extra networks or sites cost, which features (SSO, SCIM, device posture, log streaming, longer retention, site-to-site) need a higher tier, the free tier and its limits, the price of a self-hosted or on-premises licence, monthly versus annual billing, minimum term and VAT.
0 — No public prices at all; every customer is a sales call or a partner quote.
3 — A starting price or a free tier exists, but how cost scales with users, devices, gateways or features is unclear.
5 — Tiers are public with a price per user and their main inclusions, but at least one commonly needed piece (dedicated gateways or IPs, extra sites, SSO or SCIM, log retention, the self-hosted licence) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (users, devices, gateways, networks), dedicated IPs and gateways priced, add-ons priced, minimum seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given team size, number of sites, gateways and devices, with every add-on, overage and support fee and the cancellation and data-return terms published.
The IT Lead
The only public entry points are a free trial and a demo booking, with a subscription required for full functionality. We found no public information on price per user, tiers, minimum seats or billing terms — nothing I could defend in the next budget round. 5 6 7
The DevOps Engineer
The only price-adjacent facts are a free trial offered as "Try it Free", a demo booking link, and a note that a valid subscription is required for full functionality. The captured pages give no tier prices, per-user or per-device costs, seat minimums, gateway or connector pricing, or self-hosted licence terms, so a buyer cannot compute an annual cost from public pages. 5 6 7
The MSP Technician
No prices appear anywhere: a free trial, a demo booking and the note that a valid subscription is required for full multi-factor authentication functionality are all the buyer gets. How cost scales with users, features or gateways is not described, so every quote starts with a call to the vendor. 5 6 7
The Operations Manager
The captured pages show only a free trial, a demo booking, and a note that a valid subscription is required for full functionality. We found no public information on per-user prices, tiers, seat minimums or the subscription cost, so an annual cost for a fifty-person team with freelancers coming and going cannot be computed from these pages. 5 6 7
The Information Security Officer
The only pricing-related facts are a free trial, a statement that a valid subscription is required for full multi-factor authentication functionality, and an invitation to book a demo; no per-user or per-device prices, tiers, minimum seats or scaling rules appear on the captured pages. A buyer cannot begin to compute an annual cost from public information alone. 6 5 7
The Skeptic
No price appears on the captured pages — only a free trial, a note that "a valid subscription to PrivX is also required for full functionality" for the multi-factor feature, and a demo to book. We found no public information on per-user cost, tiers, minimum seats, or what a subscription includes. Every real number is behind a conversation with sales. 5 6 7
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about PrivX
Is PrivX European?
Not determined: the vendor’s pages as captured do not say where PrivX is based.
Where does PrivX store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does PrivX have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to PrivX?
As of 19 Nov 2026, the panel rates Defguard (3.5/5), Firezone (3.5/5) and Tailscale (3.5/5) highest among the other 19 Business VPN & Zero Trust Access products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Defguard (EU-Made, Poland). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PrivX alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (ssh.com, ssh.com/legal/terms, ssh.com/ssh-zero-trust-access-key-and-secrets-management, ssh.com/solutions/secure-vendor-third-party-remote-access, ssh.com/academy/pam/how-to-enable-multi-factor-authentication-mfa-with-privx, ssh.com/just-in-time-passwordless-privileged-access-management and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page ssh.com Checked 10 Nov 2026 Details →
- 2 Terms of service — found from the homepage www.ssh.com Checked 10 Nov 2026 Details →
- 3 Access model & connectivity — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 4 Access model & connectivity — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 5 Identity, access policy & device posture — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 6 Identity, access policy & device posture — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 7 Logs, audit trail & incident response — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 8 Logs, audit trail & incident response — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 9 Deployment, API & administration — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 10 Deployment, API & administration — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →
- 11 Architecture, reliability & security assurance — found from sitemap www.ssh.com Checked 10 Nov 2026 Details →