Rōvn: Competitive Landscape

Canonical comp map. Originally locked 2026-05-14; reviewed against canon generation 8 on 2026-07-22, with funding figures kept at their own transaction dates. Each entry: layer, primary buyer, verification depth, pricing model, AI posture, why Rōvn is NOT them, and how Rōvn could become the source-backed readiness layer other tools read from over time.

The category, the operating network for the healthcare workforce (the Workforce OS), is not yet owned by any single incumbent. Credentialing vendors center on facility workflow. Staffing platforms center on placement. Identity platforms lack healthcare source depth. Every layer has a real company on it, and Rōvn concedes each one below; the bet is composing all three into a single operating network for the verified clinician, with Axuall as the closest strategic overlap (see 2.17). AI operates the workflow. Source systems prove the facts. Humans make every regulated decision.

0. Competitive Map: Worker Ownership × Facility-Operator Depth

Two axes, worker-side ownership (does the worker own their record?) on X, facility-operator depth (does the tool actually operate facility workflow?) on Y. The top-right quadrant, the operating network for the healthcare workforce (the Workforce OS), is the category Rōvn is defining. No incumbent occupies it as a composed whole today; Axuall is the closest overlap and is moving in that direction (see 2.17).

How to read this map. Top-left (credentialing-only) gets facility workflow but the data lives in a per-customer silo, when the worker leaves, the record stays. Bottom-right (worker-side / identity) is portable but does not operate facility workflow. Bottom-left (HRIS) handles post-hire, not pre-hire clinical verification. Top-right composes all three: worker-owned credential record + facility workflow depth + a governed developer surface. That's the operating network for the healthcare workforce, and no incumbent owns it as a composed whole yet.

1. The Map

Three layers. Rōvn starts as the facility OperatorProduct surface04.3 Facility Workflow Memo · the facility-side AI workforce Operator and compounds into an evidence rail; competitors are mostly apps inside, on top of, or adjacent to facility silos.

                    ┌──────────────────────────────────────────┐
   APP LAYER        │ Vivian · Trusted · Indeed · Workday HCM  │
                    │ symplr · Modio · Medallion · CertifyOS   │
                    │ MedTrainer · ProviderTrust               │
                    └────────────────┬─────────────────────────┘
                                     │ reads from
                    ┌────────────────▼─────────────────────────┐
   CORE LAYER       │       Rōvn: verified credential core     │
                    └────────────────┬─────────────────────────┘
                                     │ queries
                    ┌────────────────▼─────────────────────────┐
   SOURCE LAYER     │ NPDB · DEA · ABMS · AMA · state boards   │
                    │ OIG · SAM.gov · NAMSS · CMS              │
                    └──────────────────────────────────────────┘

KYC ANALOG          Persona · Plaid · Stripe Identity: same pattern, different domain

2. Competitor Cards

2.1 symplr

• Layer: Credentialing software (facility silo)
• Primary buyer: Hospital MSO directors, CVO leaders
• Verification depth: Tier-1 facility-side workflow software; relies on facility staff to run primary source verifications
• Pricing: Enterprise contracts $50K-$2M+/yr per health system
• AI posture: Recent press releases about AI features; mostly automation veneer over legacy workflow product
• Why Rōvn is NOT symplr: symplr is facility-owned data in facility-owned silos. Rōvn is worker-owned data in a shared network. When a worker moves Facility A → B, symplr's record stays at A. Rōvn's Passport moves with the worker.
• How they eventually read from Rōvn: Large IDNs running symplr will plug Verified API into symplr to skip the redundant verification step on every new hire from the Rōvn network. symplr keeps the committee workflow; Rōvn provides the verified inputs.
• Scale / ownership: The category incumbent, deployed in "9 of 10 U.S. hospitals" and 400+ U.S. health plans (company-stated), backed by Clearlake Capital + Charlesbank Capital Partners; serial acquirer (Midas 2022, AMN Smart Square scheduling 2025). Private; specific valuation not disclosed.
• Source: symplr.com (company-stated 9-of-10 hospitals + 400 health plans); PE backing per Clearlake/Charlesbank announcements.

2.2 Modio Health

• Layer: Credentialing software (facility silo, smaller systems + medical groups)
• Primary buyer: Medical group operations, mid-size health systems
• Verification depth: Facility-side workflow + some integrated PSV automation
• Pricing: $5K-$50K/yr per group
• AI posture: Limited
• Why Rōvn is NOT Modio: Same structural inversion, Modio is per-customer silo; Rōvn is shared network. Modio's data doesn't compound across customers; Rōvn's does.
• How they eventually read from Rōvn: CHG Healthcare (Modio's parent) can integrate Verified API to make Modio outputs network-grade vs single-customer-grade.
• Exit comp: Acquired by CHG Healthcare in October 2019 (terms undisclosed), a strategic-acquirer data point for the credentialing-software category. (Sources: CHG Healthcare announcement; Crunchbase. There is no public "$168M / HealthStream / 2022" Modio transaction, do not reintroduce.)

2.3 Medallion

• Layer: Credentialing software + payer enrollment (provider-side)
• Primary buyer: Digital health providers, telehealth networks, group practices
• Verification depth: PSV automation + payer enrollment workflow
• Pricing: $5K-$30K/yr per provider org
• AI posture: Marketing AI; underlying workflow remains legacy
• Why Rōvn is NOT Medallion: Medallion serves the provider org; Rōvn serves the worker, the facility, and the developer. Medallion's data dies when the provider org churns; Rōvn's Passport persists with the worker.
• How they eventually read from Rōvn: Medallion can call Verified API for verified credentials when onboarding a clinician, skip 60-90% of their PSV workload.
• Funding / scale: ~$130M raised total, $43M (Acrew Capital, Aug 2025) on top of an $85M base (incl. $35M Series C co-led by Spark Capital + GV, 2022; backers Sequoia, Optum Ventures, Salesforce Ventures). The best-capitalized credentialing-software pure-play.
• Source: Medallion, $43M raise / $130M total, Aug 2025.

2.4 CertifyOS

• Layer: Credentialing software + provider data API
• Primary buyer: Payers, digital health, large clinician networks
• Verification depth: PSV automation + API-first delivery (closest structural comp to Rōvn)
• Pricing: Per-provider per-month + API usage; enterprise tiers
• AI posture: Stated AI-first
• Why Rōvn is NOT CertifyOS: Two differences. (1) CertifyOS is payer- and provider-org centric; Rōvn anchors on the worker-owned Passport + facility workflow layer, with API as the third surface. (2) CertifyOS does not have Rōvn's depth-label receipt model, no tiered truth ladder visible to auditors.
• How they overlap: This is the closest direct overlap. Differentiation is product surface (worker Passport doesn't exist in CertifyOS) + receipt model.
• Funding / scale: ~$69M raised total (company-stated), $40M Series B led by Transformation Capital (June 2025), prior $14.5M Series A (2022); backers General Catalyst, Upfront Ventures. Launched the "Provider Hub" data platform after the raise.
• Source: Certify $40M Series B / $69M total, Jun 2025.

2.5 MedTrainer

• Layer: Compliance training + credentialing add-on
• Primary buyer: Ambulatory + medical groups
• Verification depth: Compliance training first, credentialing second (light)
• Pricing: SMB subscription tiers from roughly $1K/yr; larger orgs quoted
• AI posture: Minimal
• Why Rōvn is NOT MedTrainer: MedTrainer is a training compliance platform with a credentialing module. Rōvn operates the full readiness workflow with source-backed evidence and receipts. Different product.
• How they read from Rōvn: MedTrainer can pull verified credentials from Verified API to populate its compliance dashboard.

2.6 Workday HCM

• Layer: General HR/HCM
• Primary buyer: Enterprise CIO, CHRO
• Verification depth: None, Workday assumes the credential is verified elsewhere
• Pricing: $100/employee/year + implementation
• AI posture: Strong AI roadmap; completed its acquisition of Paradox (agentic hiring) on 2025-10-01 and announced Agent Passport for AI agents in June 2026; not healthcare-credentialing-specific
• Why Rōvn is NOT Workday: Workday administers one employer's workforce record and post-hire HR (payroll, benefits, time-off). Rōvn handles cross-employer verification + clinical credentialing + privileging + ongoing monitoring, and its Passport is for people, not AI agents. Different layer.
• How they read from Rōvn: Workday's healthcare customers will plug Verified API to pre-populate verified clinical credentials into employee records.

2.7 ProviderTrust

• Layer: Continuous monitoring (exclusion lists, sanctions, license status)
• Primary buyer: Compliance officers, MSO leaders
• Verification depth: Monitoring only, they don't do the initial PSV
• Pricing: Per-provider per-year subscription
• AI posture: Modest
• Why Rōvn is NOT ProviderTrust: ProviderTrust is monitoring-only. Rōvn is intake + verification + privileging + monitoring + audit, with the worker-owned Passport as the spine.
• How they could interact with Rōvn over time: ProviderTrust-like monitoring can sit beside Rōvn at first. As Rōvn accumulates source-backed readiness evidence, monitoring-only tools could consume that evidence instead of forcing another siloed check.

2.8 Vivian Health

• Layer: Travel nursing marketplace
• Primary buyer: Travel nurses (consumer) + staffing agencies + facilities
• Verification depth: None, they aggregate job listings and credentials are verified by the staffing agency, not Vivian
• Pricing: Marketplace take-rate from staffing agencies
• AI posture: Job matching AI
• Why Rōvn is NOT Vivian: Vivian is a job board with marketplace mechanics. Rōvn is a verified trust rail. Vivian doesn't verify; Rōvn does.
• How they read from Rōvn: Vivian can integrate Verified API so listings show "Rōvn-verified" badge; staffing agencies skip re-verification when reading from Rōvn.
• Funding: a ~$60M raise is reported in secondary coverage (2022); valuation undisclosed

2.9 Trusted Health

• Layer: Nursing staffing marketplace
• Primary buyer: Nurses + facilities
• Verification depth: They run their own internal credentialing for nurses on their roster, fragmented, per-platform
• Pricing: Marketplace + staffing markup
• AI posture: Matching AI
• Why Rōvn is NOT Trusted: Trusted is a vertically-integrated staffing platform. Rōvn is the horizontal verified rail that staffing platforms (including Trusted) eventually read from.
• How they read from Rōvn: Trusted's credentialing team can stop doing redundant PSV; pull verified credential from Rōvn API.

2.10 Verifiable

• Layer: Provider credentialing API
• Primary buyer: Digital health, telehealth, payers
• Verification depth: API-first PSV (similar pattern to Rōvn's Verified API)
• Pricing: API usage-based
• AI posture: Stated
• Why Rōvn is NOT Verifiable: Two structural differences. (1) Verifiable does not have a worker-owned Passport surface, verifications are per-customer requests, not portable worker records. (2) No multi-tier depth-label receipt model.
• How they overlap: Closest API-layer comp besides CertifyOS.
• Funding / scale: Y-Combinator company; ~$47M raised total since 2020, $27M Series B led by Craft Ventures (July 2023), prior $17M Series A (2021). Capital flowing into API-first credentialing validates the category. (Correction: an earlier draft of this card claimed Stripe acquired Verifiable in 2023, that did not happen; the 2023 event was the Craft Ventures Series B. Do not reintroduce the acquisition claim.)
• Source: TechCrunch, Jul 2023; company funding announcements.

2.11 Persona

• Layer: KYC / identity verification infrastructure (consumer + business)
• Primary buyer: Developers, fintech, marketplaces
• Verification depth: Identity, address, document verification
• Pricing: Usage-based API + enterprise
• AI posture: Strong
• Why Rōvn is NOT Persona: Persona verifies "is this person who they say they are." Rōvn verifies "is this clinical credential real, current, monitored, tier-labeled, source-receipted." Healthcare source connectivity (NPDB, DEA, ABMS, AMA, state boards) is the moat KYC infra doesn't have.
• Relevance: Pattern comp, Persona is what Rōvn looks like 4 years from now if execution holds. $2.0B valuation ($200M Series D, April 2025; prior $1.5B Series C, September 2021).

2.12 Plaid

• Layer: Financial data infrastructure (bank account verification, transaction data)
• Primary buyer: Fintech developers
• Verification depth: Bank-source-verified financial data
• Pricing: Usage-based API
• AI posture: Building
• Why Rōvn is NOT Plaid: Different domain, financial data vs clinical credentials. Same structural pattern: time-locked source connectivity + cached inventory + developer rail.
• Relevance: Pattern comp. $8.0B valuation (tender offer, February 2026; down from the $13.4B 2021 peak). Closest single-comp for the Rōvn thesis: a source-connected data network with a compounding moat.

2.13 Stripe Identity

• Layer: Identity verification (consumer + business)
• Primary buyer: Stripe customers needing KYC
• Verification depth: Identity + document
• Pricing: Per-verification
• AI posture: Strong
• Why Rōvn is NOT Stripe Identity: Stripe Identity is general-purpose ("is this person who they say they are"). Rōvn is healthcare-credential-specific, different sources (NPDB, DEA, ABMS, state boards), different regulatory regime, different buyers. Generic identity infra has never built the healthcare source rail.
• Relevance: The pattern comp. Identity-verification infra is a real, venture-scale category; the clinical-credential network is the adjacent, separately-moated category Rōvn is building. (Note: an earlier draft asserted Stripe acquired Verifiable in 2023, that is not accurate; see 2.10.)

2.14 Verisys

• Layer: PE-consolidated CVO / primary source verification (facility silo)
• Primary buyer: Hospital MSOs, large health-system CVOs, payer credentialing teams
• Verification depth: Largest single PSV/CVO operator in the US by transaction volume; deep facility workflow integration
• Pricing: Enterprise + per-verification; RFP-driven enterprise contracts; mid-7-figure on big IDN accounts. Approx. $50-100M revenue (private; PE-backed).
• AI posture: Light, workflow automation, not foundation-model native
• 2x2 position: Top-left, high facility-operator depth, low worker-side ownership
• Why they're not Workforce OS: Verisys is the verification layer for the facility. The credential record lives in Verisys' silo on behalf of the customer, not the worker. When a clinician moves Facility A → Facility B, Verisys re-runs PSV for Facility B from scratch. No portable worker record, no developer rail, no audit-chain receipt model.
• How they read from Rōvn: Verisys's facility customers will plug Verified API to skip redundant PSV on every new hire originating from the Rōvn network; Verisys keeps the committee + monitoring workflow.
• Source: Public PE coverage (Riverside / Vestar history); Becker's Hospital Review credentialing market sizing.

2.15 MD-Staff (HealthStream)

• Layer: Legacy medical staff office software (facility silo)
• Primary buyer: Mid-market hospitals, MSO directors; strong incumbent install base
• Verification depth: Facility-side workflow; on-prem heritage, slow modernization since HealthStream (NASDAQ: HSTM) acquired the platform
• Pricing: up to ~$300K/yr depending on hospital size; perpetual + maintenance carryover on older installs
• AI posture: Minimal, product modernization roadmap, not AI-native
• 2x2 position: Top-left, moderate facility-operator depth, zero worker-side ownership
• Why they're not Workforce OS: MD-Staff is medical staff office software, facility-owned data in facility-owned databases, often on-prem. No worker layer, no API rail, no audit chain. Modernization velocity is constrained by HealthStream's broader product portfolio priorities.
• How they read from Rōvn: HealthStream's MD-Staff can integrate Verified API; MD-Staff stays the system of record for committee workflow, Rōvn supplies the verified inputs. (Note: Modio is not a HealthStream property, it belongs to CHG Healthcare.)
• Source: HealthStream public filings (HSTM); MD-Staff is part of HealthStream's credentialing portfolio.

2.16 Andros

• Layer: Health-plan-side credentialing automation (payer ICP, not hospital)
• Primary buyer: Health plans, ACOs, payer credentialing/network operations
• Verification depth: Payer-side credentialing + delegated credentialing automation; different stack from hospital MSO workflow
• Pricing / funding: Enterprise SaaS; founded 2013 as CredSimple (rebranded Andros 2021); ~$48M raised total across rounds (Crunchbase/PitchBook ~$47.9M; CB Insights ~$52M); payer-network growth focus
• AI posture: Stated AI/automation
• 2x2 position: Top-left, facility-adjacent (payer) workflow depth, low worker ownership. Adjacent ICP, not direct hospital competitor.
• Why they're not Workforce OS: Andros sells to payers, not hospitals; the buyer, the data model, and the regulatory regime are different. They don't operate hospital privileging, they don't own a worker-portable record, and they don't serve facility committees.
• How they read from Rōvn: Payer customers running Andros can pull Rōvn-verified clinical credentials for participation applications, reducing redundant PSV for clinicians already verified on the Rōvn network.
• Source: PitchBook / Crunchbase (Andros, ~$48M total); CredSimple→Andros rebrand (2021).

2.17 Axuall

• Layer: Workforce intelligence / clinician data platform (facility-side, expanding)
• Primary buyer: Hospital MSOs + health systems; expanding to clinician-network use cases
• Verification depth: Workforce data layer + credentialing data; lighter on hands-on facility workflow than symplr/MD-Staff
• Pricing / funding: Enterprise SaaS; founded 2018, Cleveland; ~$41M raised total, $20M Series B led by Noro-Moseley Partners (2023), prior $10.4M Series A led by Flare Capital (2021), with health-system strategic investors (Intermountain, University Hospitals, Hartford HealthCare).
• AI posture: Data + analytics framing; not foundation-model native
• 2x2 position: Top-left, moving right, facility-side workforce data, light worker-side ownership. The vendor most actively trying to bridge into a worker layer, but still customer-controlled records.
• Honest read: Axuall is the closest strategic overlap and we treat it that way in diligence. It already spans a clinician wallet, practitioner data, recruiting, and enterprise integration. The difference is the unit of work: in Rōvn, worker-controlled evidence enters each organization's own policy, one Resolution Case does the missing work, a named human decides, a signed receipt proves the basis, and the system keeps operating after the hire, with no placement fee and no shift book.
• Structural note on CAQH: CAQH/DataSpring converted for-profit in January 2026 and is payer-owned. That ownership is the structural reason the worker-owned corner of this market stays open.
• How they read from Rōvn: Health systems running Axuall as their workforce intelligence layer can ingest Rōvn-verified credentials as a higher-trust source; Axuall handles analytics, Rōvn handles the verified spine.
• Source: Axuall $20M Series B (Noro-Moseley, 2023); Crunchbase/Tracxn (~$41M total).

2.18 CredSimple / Andros (note: same entity)

• Status: CredSimple rebranded to Andros in 2021. They are the same company, not two competitors. Listed separately here only because legacy investor materials and analyst reports still cite CredSimple, they refer to today's Andros (see 2.16).
• Why this matters: Investors familiar with the older CredSimple brand should be told directly that the entity is Andros today; do not double-count.
• 2x2 position: Same as 2.16, top-left, payer-adjacent.
• Source: Andros press release on rebrand (2021); SEC and Crunchbase records consolidated under Andros.

3. The "We're Not Them" Cheat Sheet (for the deck)

4. Network Endgame

In the long-term network vision, apps in the App Layer could read from Rōvn's source-backed evidence rail. Specifically:

• symplr / Modio / Medallion → integrate Verified API to skip PSV redundancy
• Workday / UKG / Oracle HCM → pull verified clinical credentials from Verified API into employee records
• Vivian / Trusted / Aya → display "Rōvn-verified" badge; skip in-house re-verification
• Telehealth platforms (Teladoc, Amwell, etc.) → call Verified API on every clinician onboarding
• Payer enrollment platforms → pull verified credentials for participation applications
• EHR vendors (Epic, Cerner) → optional Verified API integration for credentialing modules

The network wins if every system that reads governed state from it gets faster, cheaper, and more defensible than rebuilding the work itself. The structural inversion (worker-owned, network-shared, depth-labeled, source-receipted) is the intended moat; sections 5 and 6 state it in falsifiable form.

5. Why Rōvn is different

None of the individual components is new, and this page concedes every one of them to a real company. The differentiation is the complete operating system around one transaction, the Work Activation: approved to start, with proof.

• Work Activation as the transaction. The system binds one person, one organization, one work context, exact evidence and policy versions, a named approver, a validity window, and a signed receipt. Competitors sell components; the Work Activation is the unit Rōvn is building the company around.
• One Ask resolution. One worker-facing request can resolve impacts across multiple facilities, files, payers, and assignments without duplicate outreach. Every alert-driven competitor generates one message per consequence.
• Worker-controlled Passport. The worker controls sharing, correction, revocation, and reuse. Marketplace wallets (ShiftKey, Nursa, Clipboard) reuse credentials inside their own economics; agency wallets (Kamana, now Triage) follow the agency. Portability that survives leaving the platform is the difference.
• Organization-specific authority. Each facility applies its own requirements and owns its own decision. Evidence can travel; decisions do not. This is why the same evidence can clear differently at two facilities, by design.
• Work Relationship continuity. Rōvn keeps operating after the hire: monitoring, expirations, coverage risk, recredentialing. Hiring networks disappear at the offer letter.
• Neutral economics. No placement fee, no shift take rate, ever. Rōvn can sit across every hiring channel because it is not paid to steer any of them.
• Governed bilateral agents. Worker and organization agents coordinate under explicit, asymmetric authority. AI compresses the work; source systems prove the facts; humans make every regulated decision.
• Receipt-grade operation. Source checks, outreach, extraction, policy application, decisions, disputes, and invalidations all produce auditable records a General Counsel can replay.
• Coverage-aware compliance. A readiness change propagates into the specific starts, shifts, privileges, and bills it threatens, not into a generic alert queue.
• Measured reuse economics. The network claim is tested through rework, time, and cost reduction, not asserted through member counts.

6. The moat, stated defensibly

The honest current state first: pre-launch, zero measured pilots, so today every moat claim is prospective. What follows is the structure the moat compounds through, and the tests that would falsify it.

Five compounding assets:

• Consented cross-employer evidence: the only evidence pool the worker can carry between organizations, because the worker owns it.
• Versioned organization policy: each facility's requirements as living, versioned objects, accumulated per jurisdiction and role.
• Resolution Case histories: the exception-resolution and outcome-labeled dataset generated only by operating the work, not by storing documents.
• Work Relationship and Work Activation graphs: who worked where, under what basis, with what proof, across employers.
• Delegation, source access, and legally reusable verification rights: the Checkr lesson, product portability dies if every downstream user must legally redo the work; NCQA delegated credentialing is the legal-reuse gate, which is why the CVO clock starts in Phase 0.

These reinforce each other: evidence without policy is insufficient, policy without operations is another checklist, operations without receipts are untrustworthy services, receipts without repeated use are not a network.

The neutrality firewall keeps the moat from being captured: no resale of worker evidence, no transfer of one organization's approval to another, no hidden ranking, no placement-fee dependency, tenant-isolated policy and decisions. Every neutral credential asset in this market eventually got captured (CAQH by payers, Kamana by Triage, Modio by CHG, Verisys by Stone Point). The defense is structural: an asset the worker owns cannot be captured without the workers leaving.

Falsifiable tests, stated on purpose. The moat is not established until: the second Work Activation costs materially less than the first; duplicate outreach approaches zero on the routine path; a worker can leave a marketplace or employer and retain useful proof; a new organization can decide independently without restarting the evidence work; post-hire monitoring prevents measurable coverage loss; and source and delegation relationships make reuse legally durable. If the second Work Activation is not materially faster and cheaper than the first, the network thesis is wrong. That is a kill criterion, not a vanity metric.