Get your team's passwords out of the group chat, for good.
WPfoss is the official heylogin partner for Africa. We roll heylogin out across your whole team, move the passwords currently sitting in spreadsheets and chat threads into it, rotate the ones that leaked along the way, train everyone, and keep it tidy afterwards. You end up able to answer, in seconds, who has access to what.
The real problem is not the passwords. It is who still has them.
Password managers fail for organisational reasons, not technical ones. They get bought, half-deployed to the technical team, ignored by everyone else, and the shared logins carry on exactly as before. That is a licence cost with none of the security benefit.
- Shared logins circulated in WhatsApp, Slack or email, where they stay readable forever.
- A "passwords" spreadsheet on a shared drive, itself shared more widely than anyone realises.
- Nobody can answer "who currently has access to our payment provider?" with confidence.
- When someone leaves, the credentials they knew are never rotated, because nobody has a list.
- The same password reused across several systems, so one breach becomes several.
- A password manager bought last year that about a third of the team actually uses.
The licence price is the one fixed number published on this site: USD 79 per user per year, sold at list with no markup. See pricing for the detail.
What you receive
- heylogin Enterprise licences at the published list price. We do not mark them up.
- Rollout across your entire team, not just the technical staff.
- Migration of existing credentials out of spreadsheets, browser stores and chat threads.
- A sharing structure designed around how your team actually works, so people do not route around it.
- Staff training, so adoption survives the first week.
- A joiner and leaver procedure that includes credential rotation, not just account removal.
How the engagement runs
- 1
Find what is in use
Which systems the business depends on, who uses each, and where those credentials currently live. The list is always longer than expected.
- 2
Design the structure first
Groups, shared vaults and access boundaries agreed before rollout, because a badly organised vault is abandoned within a month.
- 3
Migrate and rotate
Credentials imported, and the ones that have been sitting in chat are changed, not just relocated.
- 4
Train everybody
Short sessions aimed at the least technical person in the room, because adoption is the whole game.
- 5
Review and maintain
Periodic access reviews, joiner and leaver handling, and a check that people have not drifted back to the spreadsheet.
What changes afterwards
Credentials leave chat threads and spreadsheets for good. You can answer, in seconds, who has access to any given system. A leaver's access ends on their last day, and the credentials they knew get rotated. Access reviews become a routine task rather than an archaeology project, and you have something concrete to show a client or auditor.
Frequently asked questions
How much does the licence cost?
USD 79 per user per year for the heylogin Enterprise plan, the published list price. We add no margin. Our deployment work is quoted separately as a fixed fee.
We already bought a password manager and nobody uses it.
That is the most common situation we walk into, and it is a rollout problem, not a product problem. We can often fix adoption on the tool you already own. Ask us before buying anything else.
Do you get access to our passwords?
No. We configure the structure and train your people. The vault contents are yours. Where we need temporary access to migrate one credential, it is agreed in advance and rotated afterwards.
Our promise, on every engagement
- Fixed rollout scope and fee agreed before work starts.
- Licences supplied at the published heylogin list price with no markup.
- Credentials migrated and exposed passwords rotated.
- Staff trained before the rollout is considered complete.
- Joiner, leaver and access-review procedures documented and handed over.
Know who has access to every critical business account.
We will plan the team structure, migration, password rotation, training and handover required to make heylogin part of normal work.