Imprivata Virtual Desktop Access

Name: Imprivata Virtual Desktop Access
Brand: Imprivata
Rating: 4.5 (118 reviews)

Simple and secure access management for mission-critical industries

Est 2000|Valuation $492.5M|Raised $2.6B

LinkedIn 28K|Website|Web traffic 466K|FTEs 833|HQ Waltham, Massachusetts, US

MarketsIdentity Provider (IdP) & SSO Identity Provider (IdP) & Single Sign-On (SSO)

01Competitive Landscape

Narrative analysis

- Areas of relative strength: - Badge/biometric-driven shared workstation flows and session roaming are core capabilities described by the vendor and reported as valuable by multiple practitioners. - Established presence in healthcare and ecosystem partnerships with major VDI and endpoint vendors. - Areas where alternatives may be preferable: - For primarily SAML/OIDC SSO and MFA across SaaS applications, specialist identity providers are often simpler and more SaaS-native. - If the primary concern is VDI brokering and infrastructure cost, the choice of VDI platform and cloud provider will strongly influence the solution architecture; Imprivata functions as an additive workflow/security layer rather than a VDI platform itself. - Pricing comparison reality: - AVD pricing is publicly documented at a high level as cloud consumption-based; the vendor provides cost-estimation guidance and tools. - Horizon/Citrix pricing is often discussed in community forums as complex; reliable public price lists can be hard to obtain. - Imprivata pricing is largely opaque publicly; expect enterprise quote processes and the need to validate total deployment costs during procurement.

	Imprivata Virtual Desktop Access (EAM VDA)	Microsoft Azure Virtual Desktop + Entra ID	Omnissa Horizon (including True SSO patterns)
Starting Price	Quote-based; limited public pricing (some non-standard third-party artifacts may exist but are not authoritative)	AVD access rights depend on Microsoft licensing; infrastructure consumption-based (cloud resource consumption)	Quote-based (channel/enterprise licensing; not consistently public)
Primary fit	Healthcare/shared endpoints needing badge/biometric tap-and-go, roaming, and audit	Microsoft-centric organizations deploying cloud VDI with integrated identity/conditional access controls	Organizations standardized on Horizon needing integrated brokering and SSO mechanisms
Key strength	Support for shared workstation workflows and roaming; healthcare-focused integrations	Cloud scalability and conditional access/device posture integration	Tight integration with Horizon brokering and VDI operational stack
Key weakness	Agent dependency and potential complexity/price in some deployments	Not purpose-built for badge-tap roaming workflows; may need additional components for shared workstation UX	May require additional tooling for shared endpoint badge workflows and application SSO

01Competitive Landscape

Narrative analysis

Areas of relative strength:
- Badge/biometric-driven shared workstation flows and session roaming are core capabilities described by the vendor and reported as valuable by multiple practitioners.
- Established presence in healthcare and ecosystem partnerships with major VDI and endpoint vendors.
Areas where alternatives may be preferable:
- For primarily SAML/OIDC SSO and MFA across SaaS applications, specialist identity providers are often simpler and more SaaS-native.
- If the primary concern is VDI brokering and infrastructure cost, the choice of VDI platform and cloud provider will strongly influence the solution architecture; Imprivata functions as an additive workflow/security layer rather than a VDI platform itself.
Pricing comparison reality:
- AVD pricing is publicly documented at a high level as cloud consumption-based; the vendor provides cost-estimation guidance and tools.
- Horizon/Citrix pricing is often discussed in community forums as complex; reliable public price lists can be hard to obtain.
- Imprivata pricing is largely opaque publicly; expect enterprise quote processes and the need to validate total deployment costs during procurement.

	Imprivata Virtual Desktop Access (EAM VDA)	Microsoft Azure Virtual Desktop + Entra ID	Omnissa Horizon (including True SSO patterns)
Starting Price	Quote-based; limited public pricing (some non-standard third-party artifacts may exist but are not authoritative)	AVD access rights depend on Microsoft licensing; infrastructure consumption-based (cloud resource consumption)	Quote-based (channel/enterprise licensing; not consistently public)
Primary fit	Healthcare/shared endpoints needing badge/biometric tap-and-go, roaming, and audit	Microsoft-centric organizations deploying cloud VDI with integrated identity/conditional access controls	Organizations standardized on Horizon needing integrated brokering and SSO mechanisms
Key strength	Support for shared workstation workflows and roaming; healthcare-focused integrations	Cloud scalability and conditional access/device posture integration	Tight integration with Horizon brokering and VDI operational stack
Key weakness	Agent dependency and potential complexity/price in some deployments	Not purpose-built for badge-tap roaming workflows; may need additional components for shared workstation UX	May require additional tooling for shared endpoint badge workflows and application SSO