A normal alarm has no idea what your body is doing. It fires at 6:30 whether you're in the lightest sleep of the night or the deepest, and the difference between those two mornings is enormous. Remwake scores your sleep in real time and picks the moment.
You surfaced at 6:47, during light sleep, near the top of your fourth cycle. Deadline was 7:00.
Sleep runs in cycles. Across the night you move between light sleep, deep sleep, and REM, over and over. Get pulled out of deep sleep and you wake up thick-headed and slow, sometimes for an hour. Come up during light sleep and you're clear almost immediately.
Your alarm doesn't know the difference. Remwake does. Instead of a single fixed time, you give it a window, and it watches for the moment inside that window when you're already surfacing.
Every epoch through the night, Remwake combines heart rate, motion, and heart-rate variability into a single sleep score. These are the real weights the engine runs on.
Heart rate leads because it moves reliably with sleep depth. Motion catches the shifts and micro-wakings that heart rate misses. HRV is the tiebreaker, sensitive but noisy, so it gets the smallest share.
These are the actual parameters Remwake's scoring engine runs on, not a marketing simplification of them.
The default span Remwake is allowed to work inside. It never fires late, only earlier, and only when you're light enough that waking is easy.
Your first nights teach the engine your personal baseline. Everyone's resting heart rate and movement patterns differ, so the model adapts rather than assuming.
A five-minute guard stops a single restless moment from being mistaken for morning. The engine wants a real trend, not one twitch.
No wearable, no problem. Remwake recalibrates its motion sensitivity for a phone on the mattress, with its own thresholds and its own calibration period.
The engine keeps a running window of recent epochs and requires a minimum history before it will act, so early-night noise never triggers an alarm.
How light you need to be before it fires is a single number, so the whole behavior of the alarm can be dialed in without touching the model.
Remwake taught me more about interface design than any other project. Your user is at their least capable at the exact moment they're using your app, which strips away everything that isn't essential.
At night you set a window and put the phone down. In the morning there is one thing to do. Anything else can wait until you're a person again.
Dark from the start, not as a toggle. Low light, high contrast where it matters, no screen that blasts you awake before the alarm does.
The engine collects a lot. The app shows what actually helps you sleep better and hides the rest, because a dashboard at 6am helps nobody.
Remwake comes out of Feral Labs, where I use health data to make people's lives measurably better. Get in touch and I'll keep you posted.
Get in touch