mHealth that travels with the client, not the location.
Home care is delivered across thousands of locations every day. The platform that supports it should follow the client — across visits, across staff handovers, across services. We build that infrastructure for home care providers in the EU and the US.
The home is a complex clinical environment.
Our platform is built for that contact.
Continuous signal. Distributed teams. Institutional accountability.
The platform captures longitudinal health data from the client between visits, presents it in a form your field staff can act on, and escalates exceptions to the clinical decision-makers in your organisation. It operates alongside the care management software you already use — without replacing it, or requiring centralised data flows between client households.
What the platform delivers in a home care context.
Capability and what it means in practice
Continuous client monitoring
Wearable and ambient sensors capture vitals, activity, sleep, and behavioural patterns between scheduled visits.
Field-staff decision support
Care workers see actionable summaries on their existing devices — not a separate dashboard to learn.
Clinical escalation pathways
Exceptions route automatically to designated clinical roles in your organisation, with audit trail.
Personalised risk profiles
Thresholds and alerts are configured per client, not by population average.
Family and informal-carer visibility
Configurable, consent-based view for family members where appropriate.
Compliance-aware data architecture
GDPR by default; HIPAA-aligned configurations available for US deployments.
No system to migrate into. No vendor lock-in.
The platform connects to your existing care management software via standard APIs. Client data does not have to flow between households for the platform to function. Each deployment is configured against your operational reality — not a generic template.
What a home care pilot looks like.
1. Discovery (4–6 weeks)
We map your current operational model, IT estate, and clinical pathways. We define the pilot scope — typically a single client cohort, a single region, or a single service line — and agree on outcome measures.
2. Deployment (8–12 weeks)
We configure the platform against the pilot scope, integrate with your existing systems, equip the participating field staff, and onboard the client cohort. Training is delivered to clinical and operational roles in parallel.
3. Operation & evaluation (3–9 months)
The platform runs in production conditions. We meet monthly to review outcomes, surface operational issues, and refine configuration. The pilot closes with a written evaluation and a defined path to scaled deployment.
Who this fits.
This fits if you are
A home care provider with at least 50 active clients
Operating across multiple households or regions
Accountable to a regulator, payer, or commissioner
Already running a care management system (besides CRM)
Open to a structured pilot with shared learnings
This is not a fit if you are
An individual care worker or small agency below institutional scale
A direct-to-consumer wellness app provider
A retail health subscription service
Looking for off-the-shelf consumer wearables only
Looking for a fixed-price packaged product with no configuration
Built against the regulatory contexts you operate in
The platform's deployment architecture is aligned with EU MDR class IIa medical device pathways where clinical claims apply, GDPR for all EU deployments, and HIPAA-compatible configurations for US deployments. Specific certifications and conformity assessments are scoped per engagement.
Start a home care conversation.
If you operate a home care service and want to scope a pilot, a discovery call is the fastest way to test fit.