About careos

We believe care deserves a real operating system.

careos is built by ITLOX — a UK cybersecurity, data, and healthcare technology company. We think the frontline of care deserves better than fragmented tools, spreadsheets, and AI chat windows bolted onto legacy record systems.

Why careos exists

Care delivery happens in fragments.

Referrals live in one system. Tasks in another. Messages in a third. Medications and observations arrive through different pipes. Compliance is a quarterly scramble through spreadsheets and shared drives. AI tools promise automation and deliver a chat window that needs its own supervisor.

The result is what every operator already knows: missed handoffs, overdue work, unresolved messages, slow prior authorisation, and a compliance posture nobody can prove under pressure. Good clinicians and good operators carry the weight that the software should have carried. The industry calls this "the cost of care." We call it a missing operating layer.

careos is the platform that holds all of it — intake, execution, coordination, communication, compliance, and AI — on a single substrate. A Care Graph underneath, a governed AI workforce in the middle, and an Evidence Ledger proving every action above. Not another tool in the stack. The operating layer every other tool can talk to.

The company

Built by ITLOX.

ITLOX is a UK cybersecurity, data, and healthcare technology company based in London. We build long-lived platforms for regulated environments — the kind of software where correctness, auditability, and independence of evidence are non-negotiable.

careos is the third platform from the same engineering organisation that built SynthLabTech and AegisWire. One team. One standard for reliability, security, and documentation. Three domains.

2025
Founded
London
Headquarters
3
Platforms
Europe · USA
Markets
Healthcare
Primary domain
Regulated
Build posture

What careos isn't

We are explicit about the boundary.

Product scope is a promise. Here are six things careos deliberately does not try to be.

Non-goal 01

Not an acute-hospital EPR replacement

careos does not try to replace acute-hospital EPRs on day one. It sits above or beside them, coordinating work and evidence across teams that already depend on source-of-truth clinical systems.

Non-goal 02

No uncontrolled customer forks

We do not permit uncontrolled customer-specific code forks for core workflows. Extensibility happens through configuration, packs, and governed extensions — not branches that drift from the product spine.

Non-goal 03

AI never silently mutates the record

AI does not autonomously diagnose, prescribe, or silently mutate the legal clinical record. Every AI output is drafted, reviewed, and attributed. Safety-critical actions always hand off to humans.

Non-goal 04

Not a full claims adjudication engine

careos prepares, assembles, and tracks revenue-side work. It is not, and does not pretend to be, a full claims adjudication engine. We integrate with the systems that do.

Non-goal 05

Not a generic chat workflow tool

AgentOS is a governed workforce with tiered autonomy, review gates and provenance. careos is not a chat widget glued to an EHR — and will not be sold as one.

Non-goal 06

Not an overnight BI dashboard

Command Centre runs on the domain event stream, not on a warehouse refresh cadence. careos is not another BI tool fed by stale extracts.

Talk to us

We are opening design-partner slots.

If you run care operations and want early access, a walkthrough, or a design-partner conversation, we would like to hear from you.