Product
One workspace.
One habit.
Halo is a private space where a company keeps its appreciation. Here is everything in it, in the order you meet it.
A room only your
company can enter.
Registration is tied to a verified company email domain. There is no public feed, no discovery, no cross-company social graph. What is said inside stays inside.
- Domain-verified joining
Only addresses on your domain can create an account in your workspace.
- Your logo, your accent
Workspace branding sits underneath Halo's, never on top of it.
- Directory sync
People, departments and managers arrive from Google Workspace, Microsoft 365 or SCIM.
- Approved templates
Admins can curate which card designs are available and require approval for custom ones.
Workspace
acmecorp.halo.app · 128 members
- Joining
- Verified domain only
- Default card visibility
- Private
- Departments
- 6
- Custom templates
- Allowed, with approval
Departments, not a
company-wide feed.
Recognition means more when it comes from people who understand what the work took. Departments behave like channels: each one has members, a feed, and its own rhythm.
- Its own feed
What happened this week in Engineering, without everything from Sales.
- Department managers
Can recognise anyone in their department without spending points.
- Optional leaderboard
Off by default. Some cultures want it, most do not, and Halo does not insist.
Alex Johnson was thanked for unblocking the release at 11pm.
2h agoPriya Raman hit 2 years today.
this morningSam Bell was welcomed to the platform team.
yesterdayDev Kaur was thanked for the incident write-up.
2 days ago
Who can do what.
Six roles, and the only meaningful difference between them is how much they can change and whether they need points to recognise someone.
| Role | Send cards | Needs points | Manages |
|---|---|---|---|
| Owner | Anyone | No | Billing, workspace, every role |
| HR admin | Anyone | No | People, templates, policies, analytics |
| Manager | Anyone | No | Their reports |
| Department manager | Their department | No | One department |
| Employee | Anyone | Yes, on the free plan | Their own profile |
| Guest | No | — | Nothing. Read-only, scoped to one department |
The reward for being valued
is the ability to value someone else.
Receiving a card earns points. Points are not a currency you cash out, they are access: premium templates, animated cards, seasonal collections. Recognition circulates instead of terminating.
- Managers and HR never spend them
Nobody should run out of the ability to say thank you.
- They carry over
Points do not expire monthly. There is no artificial urgency.
- Optional gifts
If your company enables it, points can go toward a real reward. Most companies leave this off, and Halo works fine that way.
- No quotas
Halo will never tell someone they are behind on appreciation. That is how you get hollow recognition.
Two people open Halo
for different reasons.
If you work here
Halo is where you find out that someone noticed. A card arrives, it is specific, and it stays on your profile. Over three years that profile becomes the most honest record of your work that exists anywhere in the company, written by the people sitting next to you rather than by a form you filled in during review season.
If you run it
Halo tells you where appreciation is flowing and, more usefully, where it is not.
Coverage, not volume
How many people received nothing this quarter matters more than the total.
Automatic reminders
Birthdays and anniversaries surface a day early, with a draft, never auto-sent.
Export
Everything is yours. CSV and JSON, on demand.