A category definition · originated by Caryfy AI

Autonomous Care OS ®

/ noun / · a category for systems that deliver the work of running care, rather than tools people must operate

1.An operating system that delivers the work of running a care agency — scheduling resolved, claims submitted clean, compliance files audit-ready — rather than tools an owner must operate to produce those results herself.

2.A Work as Services architecture: routine and high-volume work is executed by the system, authority boundaries are explicit, and human judgment remains named and accountable where required.

Caryfy AI's first commercial implementation of the category is CareBravo®.

Why the category exists

28,000 agencies, one compressing envelope.

Roughly 28,000 Medicaid home and community-based services agencies operate in the United States, most of them single-location independents founded by former caregivers. Their margins are compressed from every direction at once — rate pressure, state implementation clocks, and workforce arithmetic. All 50 states reported HCBS workforce shortages in 2025 (KFF 2025 50-state Medicaid HCBS survey), and the first OBBBA implementation wave arrives state-by-state between October 2026 and Q1 2027. OBBBA is one episode of a universal pattern: every payer compresses the administrative envelope over time — by mandate, by rate cut, by demographics.

The incumbent answer is what we call Tangleware™ — a stack of disconnected software whose seams the owner fills with her own evenings. Documentation-related administrative work alone consumes up to 8 hours per week per nurse inside those tools (BMC Geriatrics, Ausserhofer et al., 2023). An agency inside a compressing envelope cannot afford that drag, and cannot afford a vendor whose fees are indifferent to her outcomes.

The distinction that defines it

Relocating screen work is not removing it.

A cheaper offshore person doing the screen work is still the screen work.

A different platform doing it is still the screen work.

An AI agent that hands output back for line-by-line approval is still the screen work.

Review is production relocated, not removed. An Autonomous Care OS crosses the line the rest of the market stops at: the work itself is taken — inside one compliant boundary, with accountability held where the outcome is delivered. That is what separates a category from a feature set, and it is why we publish no agent counts: a count is a scoreboard that goes stale on every release. The boundary is the claim.

The economics of the category

Aligned by construction.

Priced on work, not seats

An Autonomous Care OS aligns economics to completed work, outcomes or care throughput — not to the number of people operating software. Commercial implementations can put fees at risk against defined outcomes.

Authority explicit

What the system may do, what must be confirmed, what must be signed, and where a named human owns the exception — written down before the work runs.

Accountability native

Human in Presence, by design: append-only records, auditable actions, and the human signature where care and law require it.

Where to go from here

The category. Caryfy's first implementation. The company behind it.