A companion for residents and families in assisted living
A companion that keeps residents connected to the people who matter most.
Sevah gives assisted living communities a companion that keeps residents engaged, connected to family, and supported between staff visits — so families feel closer and communities deliver a more personal experience.
Built for assisted living communities, with staff review preserved before anything reaches the community record.
See the companion workflow with our team.
The browser demo below uses synthetic data. For a guided tour of the full ALF workflow, book time with our team.
Why now
Senior living has a connection gap, not a feature gap.
Assisted living communities are being asked to deliver a more personal, connected experience — with family expectations rising, staffing staying tight, and residents wanting more engagement between scheduled activities. The biggest gap isn't more care hours — it's connection between visits, between family calls, and during the stretches when staff are focused elsewhere.
Workflow fit
A companion that makes the gaps between visits feel shorter.
Companion stays in the apartment, keeps residents engaged with conversation and connection throughout the day, shares wellness updates that families can see, and gives staff a lighter lift between scheduled check-ins. That makes a community feel more personal without asking anyone to do more.
Between-visit support
Fits the daily rhythm of community life
- Engages residents with conversation, reminders, and connection
- Keeps families in the loop with daily wellness updates
- Gives staff breathing room between scheduled visits
Resident & family connection
Turns daily moments into shared updates
- Conversation and engagement tailored to each resident
- Wellness snapshots families can see from anywhere
- Helps the care team start each shift with better context
Pilot scope
One floor, one community, measurable adoption
- Starts with one floor and one high-value workflow
- Expands after resident and family signal is proven
- Avoids a community-wide change on day one
Safety boundaries
Keeps staff review and trust in the community
- One floor before wider rollout
- Tight workflow scope before expansion
- Evidence-backed claims only
Product experiences
Start with Companion, then add adjacent workflows on the same stack.
Sevah does four things for every resident: be present, keep family close, surface what matters, and help the care team start each shift with better context.
Today
Companion
A companion that keeps residents engaged, connects them with family throughout the day, and gives staff a lighter lift between scheduled visits.
Where it lives
Lives in the resident apartment and starts with a bounded pilot on one floor or wing of the community.
What it enables next
Creates the room-level signal that supports adjacent workflow decisions later.
Product forms
Core motions
- Resident conversation & engagement
- Daily family connection
- Staff-reviewed wellness notes
Operator value
Communities get a premium resident-experience differentiator — families stay closer, residents feel more connected, and staff spend less time on low-touch check-ins.
Facility value
Communities get a resident-and-family-facing experience that makes the building feel more personal, increasing move-in appeal and family confidence.
Next workflow
Orchestrator
The operating layer above the room: deployment controls, exception routing, fleet visibility, and rollout discipline across wings and buildings.
Where it lives
Lives with the operator, not the resident, as the control plane across units, wings, and buildings.
What it enables next
Turns a working pilot into a repeatable operating system instead of a one-off deployment.
Product forms
Core motions
- Exception routing
- Pilot controls
- Cross-building performance visibility
Operator value
Operators get a cleaner way to standardize pilots, see where workflow is breaking, and expand only when one building is actually working.
Facility value
Regional teams get visibility into which buildings are adopting the workflow well and where service quality is improving.
Longer-term workflow
Pick & Place
A service-robot experience for repetitive movement tasks such as supply runs, delivery handoffs, and low-complexity floor logistics that pull staff away from residents.
Where it lives
Lives in the hallways and back-of-house workflow where repetitive movement is stealing time from care.
What it enables next
Extends the stack from room intelligence into physical labor leverage inside the building.
Product forms
Core motions
- Supply runs
- Delivery routes
- Non-clinical floor transport
Operator value
Operators get labor leverage on non-clinical movement work so licensed staff spend more time on care, not hallway transport.
Facility value
Facilities get a clearer path from software-led room intelligence to measurable building-level operating efficiency.
Business outcomes
Buy Sevah on resident experience and family confidence.
The case for Sevah is experiential before it is operational. Communities offer it to keep residents more engaged, give families daily peace of mind, and create a premium experience that sets them apart at move-in time — without adding headcount.
Keep residents engaged between scheduled activities and visits
Give families daily wellness updates without extra staff time
Create a premium community differentiator at move-in
Improve family confidence without another full-time liaison
Team and credibility
Built for the communities families search for first.
Sevah's credibility comes from staying narrow: assisted living, resident and family connection, and a premium experience that makes communities more personal instead of adding more software noise. Buyers should see visible engineering work, clear staff-review boundaries, and product decisions shaped by what residents and families actually want.
“Sevah is not pitching generic robotics theater. It is building a companion for assisted living communities that keeps residents engaged and families connected — with staff review built in so nothing happens without the care team.”
Proof and trust
Early deployment signals beat generic promise copy.
Sevah should be judged on credible workflow boundaries and real deployment posture, not inflated claims. The company story is strongest when it stays brutally specific about where the product fits and what is ready today.
Built for assisted living communities
Designed to fit existing community workflows
Staff review stays in the loop
Pilot-ready deployment, not broad claim inflation
After the pilot
Start with one community workflow. Add adjacent value later.
The homepage story starts with resident engagement, family connection, and daily wellness updates. If a pilot proves useful, the same companion can later support activity reminders, community-wide family updates, and a broader rollout across the building.
01
Current pilot scope
Start where the resident and family experience is already thin — between scheduled visits, between family calls, and during the stretches when staff are stretched.
02
Adjacent workflows
Add daily wellness snapshots and community-wide family updates after the core companion experience is working for residents.
03
Wider community rollout
Roll the same companion experience into more apartments across the community once residents and families confirm it makes a difference.
Pilot fit
See whether Sevah fits one floor before you offer it to the whole community.
Start with a tightly scoped pilot focused on one floor: resident engagement, family connection, and daily wellness updates. Measure resident satisfaction and family confidence before broader rollout.
No resident-identifying data, unreviewed clinical claims, or inflated outcome numbers are used in this call-to-action path.
Try it live
CareOS Virtual Round Demo
Talk to Companion in real time and see a simulated documentation workflow built from the conversation.
Demo sandbox using synthetic case data only — no real PHI is used, and this is not a live signed clinical system. Licensed clinical verification is required before any care workflow use.
Requires microphone access to talk to Companion
Open full screenField notes
Notes from building companion workflows.
Deeper product and engineering context lives here, below the core homepage thesis.
Streaming transcription is faster, wrong, and confidently so.
Whisper-family models were built to transcribe whole utterances. Force them to stream and you trade away the future context they need to be accurate. At the bedside, where the last word often changes the first, that tradeoff is sharper than it looks.
Eldercare is the first ring.
The features that break autonomous delivery — slow, structured, low manipulation, high human-context — are the features that make care a tractable first deployment.
Small talk is the hardest thing we build, because there's no slot to fill.
Task bots have a finish line — book the flight, set the timer. Open-ended companionship has no success signal and nothing to complete, which is exactly why it's so much harder to get right.