A button close at hand. A phone nearby. People ready to help. Ruxum began by bringing these together for older adults living independently—and for families who could not always be there.
Historical product, not the current app. This is the story of the earlier pendant and its companion app, not a current hardware offer.
The original Ruxum was a rechargeable pendant worn on a necklace, with a large button, a vibration motor and red, blue and green indicator lights. It connected over Bluetooth to the wearer’s nearby smartphone running the earlier Ruxum app. The pendant was not a standalone cellular calling device: the phone and its connectivity carried the request beyond the wearer.
Its purpose was practical. Someone alone at home could ask for help without first finding a contact and making a call. If the device detected a possible fall, it could initiate an alert even when the person had not pressed the button. Family members and nearby trusted people formed the response network.
Sources: original product listing and original FAQ.
The pendant was only the start of the journey. The earlier system linked an alert to a named person’s response and kept a record of what happened.
Holding the button for about three seconds triggered the panic-alert sequence. Vibration and indicator lights gave feedback to the wearer.
The paired phone received the pendant’s signal. The original service described app notifications, with SMS and WhatsApp as additional paid channels.
Up to four designated contacts could be configured: two nearby primary contacts and two secondary contacts, such as family living farther away. The old website called them “Ruxshaks.”
A Ruxshak could confirm they were coming. The app recorded responses and arrivals, and made previously stored information available to help with the handoff.
The earlier wearable used movement sensing to identify possible falls. Its published sequence included a 20-second vibration window: a wearer who was all right could press the button to cancel; otherwise the system proceeded to the alert.
Detection could miss a fall or trigger on another movement. Cancellation was a way to reduce false alarms, not proof that every remaining alert was a true fall.
The legacy app let the wearer specify a preferred hospital and store document photos that a Ruxshak might need during hospital admission. Its response records connected the initial request, acknowledgments and arrival information.
This depended on a charged pendant, a working nearby phone, connectivity and people able to respond. It was not a guarantee of medical assistance or ambulance arrival.
Sources: panic-alert page, fall-detection page and FAQ.
The pendant also supported everyday routines and helped a family see what had been recorded over time.
Medicine reminders were configured in the app with a name, daily times and start and end dates. The original material also described activity and life-event reminders. A vibration on the pendant provided a prompt without requiring the wearer to keep looking at a screen.
A button press acknowledged a reminder. That recorded a response to the prompt; it did not independently verify that a medicine had been taken.
The legacy app grouped wearable-derived information into walking or activity, rest, breathing and posture views. The intent was to make patterns in daily routines visible to the wearer and, through reports, to their chosen contact.
These were wellness descriptions from the earlier product, not validated diagnoses, clinical respiratory monitoring or a way to rule out illness.
The product listing described an emailed weekly report combining wellness information, reminder responses, emergency case logs and Ruxshak responses. A designated report recipient could review the record even when they were not the person responding nearby.
The original website also explored a Society Package: a shared Ruxshak code connected a wider circle in a senior community. The idea was to organize nearby people as well as relatives living elsewhere.
This was an early community-support model, not evidence of a currently staffed response service or a live network of institutional partners.
Sources: product listing, FAQ, and the original reminder, wellness, reporting and community pages.
The original About page traced Ruxum’s beginnings to a family experience: after Prasad Karnik’s father had a stroke, the need was not only for help to exist nearby, but for someone to recognize the need and bring that help into action. Prasad and iMicroMed developed the pendant around that gap between an incident and a response.
Sources: original About page and January 2023 announcement. These are dates recorded in Ruxum’s own historical material.
This page brings the earlier product story together in one place, using Ruxum’s own website and recovered artwork. The links below preserve access to its original wording. Captures are dated 2024; the product history they describe began earlier.
Original imagery: homepage artwork, captured 10 January 2024. A recovered copy is hosted here so this page’s image does not depend on the archive loading.
Preserved topic summaries: fall detection, wellness monitoring, and the introduction. Existing legacy links continue to work.
This is a newly written historical account, not a verbatim restoration. Old prices, checkout links and service offers are not current. Testimonials and performance or medical-safety claims in the archived pages have not been independently verified and are not adopted here.
Updated . Product and content owner: Prasad Karnik. Editorial standards and corrections.
