HIPAA compliance,
built in.
Not bolted on.

A single signed BAA covers all 21 apps in the OS — HIPAA controls, evidence vault, password vault, backup, audit reports, and helpdesk are all tracked under one agreement, with one BAA attestation record per tenant. HIPAA is built in, not bolted on: the §164.308 / §164.310 / §164.312 control library ships pre-loaded, evidence uploads get SHA-256 verified at rest, and gap findings auto-create helpdesk tickets so nothing falls through. There are no per-module BAAs or subprocessor trails to chase during procurement. This is the locked beta posture for healthcare MSPs — same BAA footprint regardless of which tier you land on.

Yes — every row in the OS is tenant-scoped. Devices, tickets, vault secrets, audit log, custom dashboards, and credentials are all keyed off tenant_id and (where applicable) client_id, so there is no shared table where one client's PHI can bleed into another client's view. Per-client portals, per-client SLA policies, per-client patch approval workflows, and per-tenant RBAC ship out of the box; cross-tenant access requires an explicit owner-role grant that is itself written to the append-only audit log. Healthcare MSPs running multi-clinic practices (Scale tier) get white-label client portals with the same isolation guarantees.

One simple model: per tech per month, three tiers (Starter $149, Growth $229, Scale $299), one bill, no per-device or per-module fees, no add-on SKUs that surface after procurement. Every tier includes the full 21-app surface; HIPAA controls, BAA, password vault, backup, and audit reports are bundled into the Growth and Scale tiers inline, with a BAA add-on available on Starter. Active healthcare-MSP beta participants also get 30% off the first 3 months on an annual commit, locked to the cohort end date — early feedback on this pricing shape directly informs the post-launch annual-commit structure.

You don't have to. Cavaridge ships 21 first-party apps plus a 24-provider Integrations Hub catalog spanning PSA, RMM, EDR, Identity, Productivity, Communication, and Backup — ConnectWise, Datto, IT Glue, Auvik, SentinelOne, Okta, Microsoft 365, Mimecast, Veeam, and more. Connection is via OAuth or API-key forms inside the Integrations Hub; there is no custom middleware to maintain on your side. Most healthcare-MSP beta teams start by integrating Cavaridge alongside their existing PSA, then sunset tools as the OS covers the use case natively — your existing data flows in via the Hub, your techs work in one console.

Same business day for most teams. Tenant provisioning fires the moment Stripe checkout.session.completed lands, a one-time welcome activation link is emailed via the Polsia email proxy, and the first OS session is established in a single click — no manual seat keys, no waiting on a CSM to "activate your workspace." From there, import your client list, hook up the integrations you already pay for, and seed your helpdesk with the existing ticket backlog. Early feedback shapes the onboarding roadmap: the active 30-day healthcare-MSP cohort is intentionally persona-mixed (solo, multi-clinic, multi-state MSPs) so the onboarding flow keeps collapsing as the cohort runs.