For workplaces & campuses

Private support for people. A clearer view for the ones responsible for them.

Everyone gets a companion that is theirs alone. Leaders get de-identified patterns across the community: enough to act with care, never enough to single anyone out.

Lumus dashboard showing de-identified wellbeing themes and engagement across an organisation De-identified group patterns

Two products, one wall between them

The personal conversation and the organisational view never blur together.

The private door

People talk with Milo

A companion in the app they already use, on their terms. What they say stays between them and Milo, full stop.

The governed view

Lumus reads the room

A de-identified picture of themes and change over time, built only from the aggregate signal layer, so leaders can respond to what a community is carrying.

Lumus

A calmer way to see what a community is carrying.

Themes, sentiment, and movement over time, grouped by area and team. Leaders read paraphrased threads, never names, and ask better questions before they make a decision.

Explore Lumus at trylumus.com
Lumus dashboard showing wellbeing themes, sentiment split, and change over time

Privacy is the architecture

Useful to an institution only if it stays safe for its people.

The reason a leader can trust the patterns is the same reason a person can trust the conversation: the company gave up the ability to see who said what, on purpose, in the build. Can't beats won't.

i.

The Signal layer is the only thing leaders ever see

Milo turns conversations into a small, de-identified signal: an area, a tone, a de-dramatised paraphrase with the “who” stripped out. That aggregate layer is the single path to the dashboard. Chats are never on it.

ii.

Nothing appears until at least five people are in it

Every slice enforces a floor of five. A team of three simply does not render, so no pattern can ever be narrowed back down to a person. The suppression lives in the code, not in a setting someone can toggle.

iii.

A crisis goes to clinicians, never to the employer

If someone is in danger, Milo brings in Aha's care team, with helplines shared in the moment. That path is for the person's safety, and it never routes to a manager or to HR.

Healthcare and education deployments carry their own bar: HIPAA and BAA requirements, FERPA, the DPDP Act, GDPR, and local privacy obligations depend on the setting. Aha scopes the applicable path with each organisation before deployment.

Milo

Build a more thoughtful support system

Bring Milo to your people.

A short conversation is the best place to start.

Talk to Aha