Succura: A Quieter Way to Watch Over the People You Love

Most alerting products for aging parents ask the wrong person to do the work. They ask the parent — to wear a pendant, to press a button, to remember a device is there at all. The people who buy those products know the truth: the pendant ends up in a drawer. The alert only works if nothing has to be worn, pressed, or remembered.

Succura is our answer to that. It's a passive, in-home alerting system built by Noevant and brought to market first by Invictus Systems. This is a look under the hood — what it is, why we're building it the way we are, and how the technology actually works.

What it is

Succura watches ordinary indoor cameras in a parent's home. When it sees a person on the floor who isn't getting up — or hears the kind of sound that means something has gone wrong — it works a contact tree: it calls and texts the people who matter, one after another, until a human acknowledges. Nothing to wear. Nothing to charge. Nothing to press.

The buyer isn't the parent. It's the adult child — the person who lies awake wondering whether they'd know if something happened three states away. Succura is built for that person's peace of mind, and it's honest about what it is: it notices and it notifies. It doesn't promise outcomes it can't control, and it deliberately never dials 911. That last choice is not a limitation — it's the design. More on that below.

Why we're building it this way

Passive beats worn, every time

The entire premise is that the system does its job whether or not the person it's watching over cooperates. A pendant depends on the wearer. A camera that's already on the wall depends on nothing. That single decision — passive over worn — is why this can help people the pendant era left behind.

No monthly fee

Invictus was built on a promise: no monthly bills, no lock-in. Succura keeps it. You pay once — hardware plus a couple of years of service, wrapped into a single upfront price — and you're done. When the service term runs out, you can top it up with another one-time payment. No subscription quietly draining a card for years. That's not a marketing angle; it's the whole identity of the brand, and it's a genuine differentiator in a category built on recurring revenue.

The line we don't cross: it never calls 911

This is the most important design decision in the product, and it's worth sitting with. The moment a system takes it upon itself to summon police, fire, or an ambulance, it steps into a heavily regulated world — the world of monitored dispatch — and inherits all of that world's liability and duty-of-care obligations. We don't want to make promises about emergency response that we can't guarantee, and we don't want a false alarm sending first responders to a door for no reason.

So Succura does something different and, we'd argue, better for its purpose: it notifies the people who already know the parent. The son who can call the neighbor. The daughter who has a key. A person who can decide, in context, what actually needs to happen — instead of an algorithm defaulting to the most drastic option. The rule we tell buyers is simple: more contacts means a more robust alert. We ask for at least three. The system is designed so that a real event reaches a real human quickly, and so that the audit trail of who was contacted, when, and what they did is captured completely — because that record is the honest backbone of the whole thing.

How it works

There are two halves: a small computer that lives in the home (we call it the box), and a cloud service that runs the contact tree. They speak to each other over a signed, tamper-evident channel. Here's the path an event takes.

The box: seeing without sending video anywhere

The box is a compact mini-PC with a dedicated AI accelerator — a Hailo-8 neural chip — sitting alongside the main processor. It pulls a low-resolution substream from the home's indoor cameras and does all of its analysis locally. Video never leaves the house. That's a privacy decision and a liability decision at once: there's no cloud archive of grandma's living room to breach, and the box is judging a body's posture, not building a surveillance record.

The analysis is deliberately layered so one modest chip can watch six to eight cameras at once:

• A cheap gate runs constantly. A lightweight person-detector asks one question per frame — "is anyone even here?" Most of the time in most rooms, the answer is no, and nothing expensive runs.
• The expensive analysis only wakes when a person is present. When someone's in frame, the box runs a pose model that maps seventeen points on the body — shoulders, hips, knees, ankles, and so on. From those points it computes two things: is the torso oriented horizontally, low in the frame (a body on the floor rather than a body standing), and has that body gone still? Either signal alone is weak — someone bending to tie a shoe is horizontal but upright; someone napping isn't an emergency — so the system requires both, held together, for a configurable window of time. A few seconds on the floor is nothing. A body down and not moving for long enough is the signal.
• Sound runs in parallel. An audio model listens for a short list of distress signatures — a scream, breaking glass, a shout — and uses a rolling vote across several listening windows so a single loud television doesn't trip it.

Getting this decision logic right is where the real engineering lives, and it's built to be provable on a workbench before it ever touches a camera. The "is this person on the floor" math, for instance, has a subtle trap: when a person is standing, their body length runs top-to-bottom, but when they lie down, that length rotates sideways — so any naive "how tall is this body" measurement collapses to nothing the moment someone is horizontal. The logic has to measure the body's overall extent, not its height, or it fails at exactly the moment it matters most. We found and fixed that class of bug in testing that never required a single piece of hardware — because the decision-making is written as pure logic, separate from the camera and the chip. On the box, the chip's only job is to feed that logic clean data. That separation is why we can trust it.

The signed handoff

When the box decides something happened, it sends a compact message to the cloud service. Every message is cryptographically signed with a secret unique to that home, over the exact bytes being sent. The cloud service recomputes the signature and compares it. A message with the wrong signature is rejected outright. A message about a home that isn't currently armed is quietly dropped. This means the escalation path can't be spoofed by anyone who doesn't hold that home's key, and the whole exchange leaves a verifiable trail.

The cloud: working the contact tree

Once a valid event lands and the home is armed, the escalation engine goes to work. It walks the contact list in order. Each contact gets both a call and a text. The call can be acknowledged by pressing a key; the text by replying. If the first contact doesn't respond within a short window, it moves to the next, and the next, until someone acknowledges. Every step — who was reached, how, when, and what they did — is written to an immutable record. That record is the product's spine: it's what turns "we think we called someone" into "here is exactly what happened, timestamped."

Staying alive in the field

A box that silently dies is worse than no box, because it creates false confidence. So the box phones home on a heartbeat, and if it goes quiet, that silence is itself an alertable condition. The system also updates itself the way critical infrastructure should: every update lands on a spare partition, and the box only commits to it after a health check confirms the chip is really inferring, the detector is really running, and the heartbeat is really green. If any of that fails, the box automatically rolls back to the last known-good version — no technician, no house call, no typing commands. In the worst case, a power cycle heals it. Someone's parent should never be the one debugging the thing meant to watch over them.

The bigger picture

Succura is the first commercial product built on Noevant's intelligence layer — the escalation engine, the models, the box software — with Invictus carrying the customer relationship and the trust that comes from being a real, local installer with a no-nonsense reputation. The architecture is built so that everything Noevant knows how to do can eventually power more than one brand, while each business stays cleanly separable. That's deliberate, and it's the kind of decision you make at unit one if you're building something meant to last and, someday, to stand on its own.

But the reason we're building it isn't the architecture. It's the person lying awake at 2 a.m. wondering about a parent who won't wear the pendant. Succura is for them — a quiet, honest system that watches without intruding, notifies without overreaching, and leaves a clear record of everything it did. It doesn't promise to save anyone. It promises to notice, and to make the call. For a lot of families, that's exactly the thing that was missing.