A possible fall
A fall-capable sensor could trigger a check-in. A movement sensor alone cannot detect a fall, and no sensor can guarantee every event is noticed.
Example notificationPossible fall in the bathroomCalling your first contact now
01 / On your side of the connection
The home tells one part of the story. This is the view we’re designing for the people who care — from an ordinary morning to a shared response.
Interactive design preview
Fictional household. No live monitoring or real notifications.
Tirana, Albania · Example household
Everyday activity
Kitchen movement was noticed after bedroom activity. No urgent alert in this example.
No one has acknowledged this example yet.
Choose an outcome before resolving the example.
Example contacts and preferences. Changes here apply only to this preview.
Urgent incident and connection statuses stay visible.
The pilot must agree who can check in locally and what happens when nobody answers. Stonotix is not an emergency response service.
Home signals → Clear context → A named response → A recorded outcome
Help us shape this experience02 / The signals, explained
Four examples of what we’re building. These messages are simulated; detection and delivery still need testing with real equipment.
A fall-capable sensor could trigger a check-in. A movement sensor alone cannot detect a fall, and no sensor can guarantee every event is noticed.
Example notificationPossible fall in the bathroomCalling your first contact now
A period without expected movement could be a reason to check in. It needs context: someone may be out, resting, or with a visitor.
Example notificationQuieter than usual since 14:00Calling to check in
The planned family view distinguishes a home reporting no unusual activity from a home that cannot report. Missing data is not reassurance.
Example notificationKitchen sensor has gone quietNothing heard since 09:12
A battery warning could help arrange a replacement. Availability and warning thresholds depend on the sensor model.
Example notificationFront door sensor battery is lowPlenty of time to change it
03 / Small things, thoughtfully placed
Different sensors do different jobs. The home assessment will confirm the model, placement, power supply, and coverage of each room.
Presence in a covered room. Possible-fall detection only on models that support it.
Movement in a room, or a door opening and closing. These events add context, not identity.
A gateway brings sensor events together and connects them to the remote service.
Already have sensors? Compatibility must be checked by exact model. There is no published supported-device list yet.
Help button: planned. Its alert and response flow is not demonstrated by this site.
04 / A thoughtful start
The proposed pilot journey. Installation, local support, cost, and timing must be agreed before a household joins.
Talk through the person’s preferences, the rooms, internet connection, and who can help nearby. Agree consent before planning equipment.
Confirm the exact devices and installer. Check each covered room and walk through an alert with the people expected to respond.
Set contact order, access, battery checks, and support responsibilities. A pilot should review missed events, false alarms, and response times.
05 / The response we’re designing
A message can be missed. Our intended workflow moves through the agreed contacts, shows who is responding, and keeps an outcome. This sequence illustrates that design; real notification delivery is still to be proven.
The first person on your list is called straight away.
We move on to the next person. Nobody has to remember to chase it.
Everyone else can see it is being handled, so nobody duplicates the trip.
A false alarm, all fine, or something real — recorded either way, so patterns are visible later.
06 / Your weekly picture
Everyday patterns and anything that needed attention, brought together in a short, readable summary.
An illustrative summary with fictional events. A future summary must show gaps in reporting and cannot diagnose a condition or tell you why a routine changed.
Ardita was up by around 06:40 most mornings, a little later on Sunday. Kitchen activity was steady all week, and evenings looked much like the weeks before.
There were two night-time trips to the bathroom on Tuesday, which is usual for her. On Thursday evening the house was still for four hours when it normally isn’t, so we called — Ana confirmed she was fine and watching television.
Nothing else needed attention.
07 / Where we are today
Stonotix is in development. Here is what you can explore today, and what needs to be established before a household relies on the service.
Interactive examples with fictional events. No live home is connected.
A real-device incident through response and resolution is not demonstrated here.
Flows, exact devices, and household suitability still need to be confirmed.
Location, installer, responder, maintenance, cost, and duration must be agreed in writing.
No accuracy percentage or independent validation claim. Results should include missed events, false alarms, and response times.
We’ll add named partners and pilot findings when they are confirmed and can be shared. An illustration is an explanation, not evidence of reliability.
08 / Their home. Their choice.
Being looked after should not feel like being watched. Here is what that means in practice.
Nothing in a Stonotix home records video or sound. Not in the bedroom, not anywhere.
Sensors know a room was used. They do not know who you are or what you were doing.
Before a pilot, we must explain where events travel, who processes them, where they are stored, and for how long. Those arrangements are not yet published.
The pilot must include agreed permissions and a clear process for requesting a copy, removing access, or deleting household information.
The person being looked after is part of the decision. This works when it is not done to someone.
Your data is not a product. It is not sold, and it is not passed to advertisers.
09 / Questions, answered
Answers to the questions families and care providers ask most.
The proposed setup uses presence, movement, and door sensors without video or audio recording. A help button is planned; its response flow still needs implementation and testing.
Remote alerts require connectivity. Some sensors may still detect locally, but keeping events for later delivery depends on the exact sensor and gateway and is not established here. The family-view preview shows missing data explicitly. Backup mobile data and power are not included promises.
The planned workflow uses an agreed list of family, neighbours, or carers. The contact order, timeouts, and fallback when nobody responds must be agreed and tested for the pilot. It does not replace emergency services.
False alarms and missed events are possible. You can try recording a false alarm in the family-view preview. A pilot needs to measure both, with context; we do not yet have published results or promise automatic learning from feedback.
No. Stonotix is in development, does not diagnose conditions, and is not a substitute for medical care or an emergency service.
Compatibility must be assessed by manufacturer, model, and gateway. There is no published supported-model list yet, so we cannot promise that existing equipment will work.
10 / Build it with us
Supporting someone in Albania from a distance? Tell us a little about the home and the people around it. A first conversation helps us understand whether a future pilot could fit.
Focus: Albania and the wider Balkans. Locations and dates are not confirmed. This is an enquiry, not a purchase or a guaranteed pilot place.
Enquiry received
Your enquiry has been accepted for delivery to Stonotix. The team can reply to the email address you provided.
No payment, installation, or service has been booked.