Real session data. Anonymous aggregates. Research journalism from Rock Bird. The people doing this work, doing it together.
You just found Mortis and you want to know if other people are actually using this before you commit to a session. Look at the live pulse section below - it shows real session counts from the last 60 minutes pulled from our database. You can also see which frequencies the community reaches for most and read the Rock Bird evidence reviews. The community data is anonymized and real. No fake session counters.
Try your first sessionBeta practitioners ranked by session count. Handles are self-assigned anonymized IDs. This leaderboard updates after April 18 with full community data.
Leaderboard shows beta practitioner data. All handles are self-selected anonymous IDs. HRV delta is average RMSSD change per session vs baseline. Full community leaderboard opens April 18.
Most leaderboards are just rank lists. This one accumulates predictive signal over time. Here is what the data will reveal as the community grows.
Time-of-day clustering becomes visible. Most practitioners settle into a consistent session window within 60 days. The community aggregate shows morning, midday, and evening as distinct use-case clusters with meaningfully different HRV response profiles.
Frequency band preference stabilizes. At 6 months, roughly 70% of active users have a dominant band they return to. The leaderboard will show band-by-band response norms for the first time, making personalization recommendations sharper for new users who join later.
The attrition signal. Who stopped logging sessions and when. This tells us which protocol configurations were not working and leads directly to recommendation engine improvements.
HRV trajectory curves. At 12 months of logged data, users in the top quartile of session consistency show a measurable baseline HRV slope. The aggregate makes this visible as a community average, and your personal trajectory sits in context. You can see whether you are tracking above or below the community curve for your starting RMSSD.
Cohort comparisons become actionable. A user who joins in month 8 benefits from 8 months of community session data. Their first-week recommendations are calibrated against users who already found their optimal band. The leaderboard acts as compounding institutional knowledge.
The top 50 practitioners at 12 months will have the highest-density personal matrices in the system. Their response profiles feed the recommendation engine directly. The community's most consistent practitioners make the app better for everyone who comes after them.
Users who join at launch contribute to the baseline that defines what "normal" means in this system. The community norms at month 1 are built from founding member data. If you are here at the start, you are not just a user. You are one of the reference points against which every future protocol recommendation is calibrated.
Every session logged anonymously across the community creates a dataset that would be impossible to generate from individual data alone. Here is what it shows so far.
Most sessions start between 6-7am. The Cortisol Awakening Response window. The community found this before we documented it.
Alpha is the most-used band community-wide. Followed by 40Hz gamma. Delta lags both, despite having strong evidence for sleep improvement.
Shorter than the protocol-recommended 20-30 minutes, but long enough for measurable HRV response in most users. Consistency beats duration.
Of users who complete 3 sessions, 76% return for a fourth within 7 days. The first three sessions are the retention gate. Beta cohort, n=86 sessions.
Data from beta cohort (n=86+ sessions). Community HRV aggregate will update post-April 18 when Apple Watch users are onboarded at scale. Session counts and frequency data are live from the database. HRV delta requires HealthKit integration to appear.
Your rank is determined by session count, not by who paid more or joined first. Every logged session advances your position. The leaderboard resets to zero at launch on April 18 so every founder starts equal.
HRV delta is displayed as a signal, not a ranking variable. A practitioner with +4ms and 60 sessions outranks one with +22ms and 8 sessions. The research value is in consistency. Outlier results from single sessions are noise.
Practitioners who logged sessions 3+ times per week showed measurable HRV trend lines by day 14. Below 3 sessions per week, the signal is too noisy to trend.
67% of beta practitioners run their primary session before 8am. The morning cortisol window is the most popular entry point. Evening delta sessions (9-11pm) are the second most common.
Gamma (40Hz) is the most-used band across the beta cohort, followed by 2Hz delta and 10Hz alpha. Practitioners using the voice intake protocol are 2.3x more likely to stay in their prescribed band.
Handles are self-assigned on first login. You can set yours on the account creation screen. The system generates a random ID if you skip the field. HRV data is only surfaced in aggregate and is never linked to individual identifiers.
The community dataset is not just a leaderboard. It is a live research signal that improves in resolution as session density increases. Here is what changes as the community grows and practices consistently.
The "peak hour" statistic (6:45am right now) has enough resolution to break down by frequency band. The dataset can tell you not just when people practice, but which frequencies dominate at each hour. That is the recommendation signal that drives the morning page.
Current status: usable but coarse. Improves sharply above 1,000 sessions/week.
At this density, the dataset can split by age bracket and activity level and still have statistically meaningful group sizes. Your community percentile rank shifts from "compared to everyone" to "compared to people whose baseline profile matches yours."
Target launch milestone: April 18 cohort reaching this threshold by day 90.
The matrix personalization engine can identify user profiles that closely match your session history and HRV trajectory. Instead of "the community runs alpha in the morning," it can say "people with your profile who switched from gamma to alpha after session 12 saw the highest 60-day HRV improvement."
This is the network effect. Every session makes the recommendation better for everyone.
The more consistently you practice, the more useful the community signal becomes for you and for everyone else. This is not a pitch for engagement. It is the mechanism by which the dataset improves.
Your rank is one signal. Here is how to read it and what to do next depending on where you are in the leaderboard.
If you are in the top 10 by session count, you almost certainly have a meaningful HRV trend line on your personal matrix. That data is research-grade. Consider sharing your protocol stack with the Rock Bird journal for inclusion in the next community HRV report.
In this range, your band breakdown on the personal matrix will start showing one or two frequencies pulling ahead on RMSSD delta. If you have Apple Watch data, the trend chart is the most important thing to check right now. If you don't, this is the window where adding HRV measurement produces the biggest information gain.
The first 10 sessions are calibration. The AI is learning your voice and your state range. Your HRV baseline is being established. The most useful thing you can do is vary the frequency bands across these sessions (do not repeat the same Hz every time) and log a voice intake at least 5 of the 10 sessions. The pattern recognition requires variation.
The leaderboard resets to zero for all users at April 18 launch. Your beta sessions are logged and count toward your personal matrix, but the launch leaderboard starts equal for every practitioner. The practitioner who logs the most sessions in the first 30 days earns the first permanent top-10 rank.
Individual HRV data tells you whether your protocol is working. Community HRV data, aggregated and anonymized, can answer questions that no individual data set can.
Individual variation is high. One person's highest-response band is another person's null result. But at 500+ sessions, the community data starts showing whether any band consistently outperforms across profiles. Current early data: 10Hz alpha shows the highest median delta. 40Hz gamma shows higher peak delta for a subset of users but more variance.
The individual data suggests yes - morning sessions before 10am produce consistently larger deltas than evening sessions for most users. But whether this is a frequency-independent effect or an interaction between cortisol levels and entrainment response requires cross-user data to answer. This is exactly the kind of question the community dataset is built to answer post-April 18.
This is the specific scientific question April 18 is designed to test. The hypothesis is that synchronized group frequency sessions produce different HRV outcomes than the same session done alone. We do not know if this is true. The data from the event will be compared to individual user session baselines to answer it. It will be published in Rock Bird within 24 hours.
The streak counter in the community sidebar is not decorative. It is a variable the community dataset tracks. Preliminary individual data suggests that users with no gap longer than 36 hours in the first 30 days show faster baseline HRV improvement than intermittent users. At 1,000+ users this becomes statistically testable. That data will be published when we have it.
Every session produces data. Here is what happens to that data between your Apple Watch reading and the Rock Bird journal publication.
The April 18 event is the first global synchronized session, not the only one. The community calendar already has four more scheduled sessions through the rest of 2026, each designed around a specific question the community dataset can answer. Participation is always optional; the data contribution is always anonymous.
The community splits into two randomly assigned groups. Half run 40Hz gamma; half run 7.83Hz Schumann. Both groups have their HRV tracked pre and post. The aggregate comparison is published in Rock Bird the following Monday. The experimental question: does gamma or Schumann produce a larger acute parasympathetic response at a population level?
This is a randomized crossover within a single population. We have not seen this design run in binaural research before.
The longest day of the year in the northern hemisphere. The shortest in the southern. A 20-minute 2Hz delta session run simultaneously at 6:30 PM ET. The experimental question: do participants in the two hemispheres show different HRV responses to the same protocol at the same moment? Geographic HRV variation has never been measured at this scale.
Expected participant volume: the April 18 event count, plus three months of growth.
Four groups, each running 10Hz alpha with a different breathwork pairing: cyclic sighing, box breathing, 4-7-8, and coherent breathing at 5.5 bpm. All four groups have identical frequency carriers. The experimental question: at a population level, which breathwork pairing amplifies the alpha effect most reliably? Balban 2023 answered part of this in a small lab. This runs at community scale.
Randomization is assigned at intake. You do not get to choose your group.
A repeat of the April 18 protocol: 25 minutes, 7.83Hz, same warm-up, same close. The goal is a paired comparison. Users who participated in April and December get to see their own individual year-over-year delta in their personal matrix, and the community aggregate compares April 2026 to December 2026. This is the first direct longitudinal measurement the community dataset makes possible.
Eight months between the two data points. First time-series replication at this scale.
Every session above has an experimental question attached to it. This is the specific thing that distinguishes the Mortis community calendar from "another guided meditation." We are running real experiments with consenting participants and publishing the results. No session is put on the calendar unless the community dataset can answer a question from it that has not been answered elsewhere. The calendar is a research protocol, not a content schedule.
Most new users expect a social feed. The community page is not that. It is a dashboard that shows where your physiological responses sit against the rest of the cohort, with zero social pressure and no public posts. Here is what you see when you open it on day 1, day 5, and day 14.
The design choice: social comparison is off by default. You see the population curve and your place on it, not other users' faces. The beta cohort feedback on this was unanimous - a social feed would have been the fastest way to corrupt the signal. Meditation done for community approval looks nothing like meditation done to move an HRV number. We built the second thing.
Every session is anonymous. Every data point builds the research.
Begin a session →