Vigilink exists to own one thing properly.
Vigilink Inc. is incorporated in British Columbia, Canada and holds Safe SOS — the app, the responder network and the workforce platform built on top of them. The product has been shipping since 2023 from Abidjan, Côte d’Ivoire, by a small engineering team living in the market it serves. Vigilink is the structure around that work: one company, one product line, one promise to keep.
British Columbia, Canada
Corporate, finance, partnerships
Abidjan, Côte d’Ivoire
Product, responder network, support
Four things we do not trade away.
A safety company is only as good as what it refuses to compromise when a deadline or a deal is on the line.
The alert is the product
Everything else — the map, the community, the dashboard — exists to make one alert reach a human being who acts. Anything that does not serve that gets cut.
Two lanes, never crossed
A person’s own contacts and their employer’s security desk are notified in parallel and see nothing of each other. That separation is architectural, not a setting, which is why staff accept being on the system at all.
Build where the problem is
Product and operations sit in Abidjan, in the market we serve, on the networks and devices our users actually have. We are not designing for this market from somewhere else.
Say what is not built yet
We hold an implicit safety promise. Overstating coverage is how that promise breaks, so we publish what ships and name what does not.
Software is the easy half.
Anyone can build a button that sends a notification. The company is the network behind it, and that is operations work: recruiting responders, verifying credentials, keeping enough of them on duty in a given square kilometre, and measuring whether they arrive.
Verified, not crowdsourced
Nurses, first-aiders, security professionals and off-duty fire. Credentials are checked before anyone appears on a map.
On duty by choice
Responders set their own availability. An alert reaches the 25 closest who are on duty within roughly 2 km.
Rated after the fact
Accept, decline, arrive. Every response is recorded and rated, because density without reliability is a statistic, not a service.
Density before spread
We saturate one city before opening the next. A network at 1% in five countries helps nobody.
One city at a time, in this order.
Expansion is a sequence, not a map. Each step is chosen because it needs almost no product change from the one before it.
- Operating
Abidjan, Côte d’Ivoire
Beachhead. Density is what makes a responder network and a heat map work, so we win one city completely before spreading.
- Next
Francophone West Africa
Senegal, Cameroon, Mali, Burkina Faso, Benin, Togo. Same language, same mobile money rails, near-zero product change.
- Then
Anglophone West and East Africa
Nigeria and Ghana for scale; Kenya, Tanzania and Uganda for mobile money maturity.
- In parallel
Diaspora markets
Canada, France, Belgium and the US. Families abroad subscribe in hard currency for relatives at home.
Small team, unusually direct consequences.
The thing you ship this month decides whether someone gets reached next month. That is the appeal and it is also the pressure. We hire slowly and mostly for judgement.
Mobile engineering
React Native, on real devices, on real networks.
Backend and infrastructure
NestJS, MongoDB, WebSocket and live media at unforgiving latencies.
Responder operations
Verification, on-duty coverage, and whether people actually show up.
City and community leads
Density in one neighbourhood at a time. Mostly in person.
Enterprise sales
Security firms, NGOs, logistics. Pilot to contract.
No formal openings posted right now. If one of these is yours, write to us with something you have built and we will read it.