Medigate no longer exists as a standalone product. Claroty folded it into Claroty xDome in June 2024. The rest of the healthcare IoT security market consolidated right behind it. This guide compares the platforms security teams evaluate today and verifies the data behind each one.
Here's what this guide covers:
- Why the Medigate name disappeared, and what replaced it
- How today's leading alternatives compare
- What to verify before you switch vendors
- What a vendor migration actually involves
- Where ORDR fits if you're evaluating a move
Why the Medigate Name Disappeared
Claroty acquired Medigate in January 2022 for roughly $400 million. The deal combined Medigate with Claroty's industrial cybersecurity platform. Medigate operated as a distinct brand until June 2024. Then Claroty renamed the product Claroty xDome for Healthcare. Existing Medigate customers kept their deployments, but the product now runs fully under the Claroty brand.
The rest of the category moved through the same pattern.
Year | Acquirer | Target | Deal Value |
2022 | Forescout | CyberMDX | ~$80 million |
2022 | Claroty | Medigate | ~$400 million |
2025 | Axonius | Cynerio | $100M+ (up to $250M with earnout) |
2026 | ServiceNow | Armis | $7.75 billion |
Four of the category's best-known healthcare IoT brands now run as product lines inside larger companies. That consolidation is the main reason security teams look for alternatives. Any of these three events can push a team to look elsewhere. The technology itself may not have changed at all:
- A rename
- A change of ownership
- A new roadmap
How Today's Leading Alternatives Compare
Six platforms dominate the healthcare IoT security market today. The table below shows each vendor's current owner. We checked ratings and deployment models against Gartner Peer Insights and KLAS Research.
Platform | Ownership | Deployment | Device Coverage | Enforcement | 2026 KLAS Score |
ORDR | Independent | Agentless; cloud or on-premises | IT, IoT, OT & IoMT | Direct policy enforcement | 89.4/100 |
Claroty xDome | Claroty | Cloud or on-premises | OT, IoT & IoMT | Through integrated security controls | 92.1/100 |
Asimily | Independent | Cloud | IoT & IoMT | Primarily integrations | 96.6/100 |
Armis Centrix | ServiceNow | Cloud | IT, IoT, OT & IoMT | Through integrations | 91.1/100 |
Axonius for Healthcare (Cynerio) | Axonius | Cloud | Healthcare IoT/IoMT | Through integrations | Limited KLAS data |
Forescout Medical Device Security | Forescout | On-premises or cloud | IT, IoT & medical devices | Network access control | Limited KLAS data |
Gartner review volume is a signal worth reading carefully. It is not the whole picture.
- Claroty holds the most Gartner reviews by a wide margin. That reflects its multi-year run as the incumbent. KLAS scores tell a tighter story.
- Asimily's winning score is just 7.2 points ahead of ORDR's fourth-place finish.
- ORDR relaunched its current AI Protect platform in March 2025. Axonius added healthcare coverage only after acquiring Cynerio.
What to Verify Before You Switch Vendors
A rebrand or an acquisition is not a reason to switch platforms by itself. It is a reason to check that your current vendor still fits your environment. These four questions apply to any platform on your shortlist.
Question | Why It Matters |
Does the platform install agents on medical devices? | Agent-based tools can create compatibility risks for legacy devices that weren't designed to run third-party software. |
What's the realistic time to full deployment? | Deployment can range from a few days to well over a year. Architecture is a major factor. |
Who owns the product roadmap after the acquisition? | Direction can change when a broader platform absorbs a healthcare-focused vendor. |
Does pricing scale with device count or site count? | Multi-site health systems can see major cost differences between per-device and per-site licensing models. |
What a Vendor Migration Actually Involves
Switching platforms is not a single cutover event. It happens in stages, and each stage carries its own risk to clinical operations.
Most migrations start with a parallel discovery run. The new platform monitors the same network segments as the incumbent platform, without altering device settings. This step lets your team compare device counts and classification results side by side. No one changes a live policy yet.
Segmentation policy comes next. A platform that generates policy from observed traffic needs real production data first. Only then can it propose enforcement rules. Copying policy straight from the old platform defeats the purpose of switching. It carries over the same gaps that prompted the search for alternatives in the first place.
Retiring the old platform is the final stage. It is often the slowest one. Every integration point references the old platform by name. That includes SIEM and NAC connections, as well as internal runbooks. Budget time for each one, not just the network sensors.
Migration Stage | What Happens | Typical Focus |
Parallel Discovery | The new platform monitors alongside the incumbent. | Compare device counts and classification accuracy. |
Policy Generation | The new platform builds segmentation rules from live traffic. | Validate rules before enforcement. |
Cutover | Traffic and alerting move to the new platform. | Confirm clinical workflows stay uninterrupted. |
Decommission | The old platform is shut down, along with its integrations and runbooks. | Remove references from security tools and ITSM systems. |
None of these stages has to run on the vendor's default timeline. Ask any platform on your shortlist to show you each stage with your own device inventory before you sign. A vendor that resists a parallel run before signing is telling you something. A confident platform welcomes the comparison. It will point you to reference customers who completed the same move.
Where ORDR Fits
ORDR takes an agentless approach. It uses passive network analysis instead of installing software on medical devices. AI Protect for Security handles continuous discovery and threat detection. AI Protect for Segmentation builds and enforces policies based on observed traffic patterns, not on static templates. ORDR added ORDR IQ in November 2025. It gives security teams a conversational interface for asset queries.
ORDR at a Glance | Details |
Deployment Model | Agentless, passive network monitoring |
Core Products | AI Protect for Security; AI Protect for Segmentation; ORDR IQ |
Segmentation Approach | Builds policy from observed traffic and simulates rules before enforcement |
Best Fit | Teams that want device discovery without installing software on clinical devices |
Moving off Medigate because of the ownership change? Ask ORDR about migration timelines and side-by-side discovery runs before you commit. A parallel deployment lets you compare device counts and classification accuracy against your current platform before you cut over.