Download websites that use Ushahidi

About Ushahidi

Software written for emergencies has a deployment pattern that nothing else in a technology catalogue shares. An installation goes up for one election, one earthquake or one disease outbreak, collects reports for a few weeks, and then either freezes into an archive or vanishes with the hosting account. Ushahidi carries that pattern, so any count of it is a photograph of a moving population rather than a measure of an install base.

The structured facts describe an organization rather than a company. Ushahidi publishes the platform under the AGPL v3 license, the code is PHP, and the project dates to 2008. Our catalogue files it under CMS, and the classification is itself informative. A platform for gathering reports from the public and putting them on a map does not fit the ecommerce, analytics or content management buckets that most detections fall into, and the misfit is the whole point. Nobody deploys this to run a business. Organizations deploy it to collect information from people who have no other way to send it. A copyleft license matters more here than it would for a commercial product, because the groups running the platform need to adapt it to a local language, a local reporting channel or a local legal constraint, and they need to do that without asking anyone for permission.

Self-hosting then shapes what anyone outside can see. A PHP application published under AGPL v3 gets copied onto whatever hosting a newsroom, a relief agency or a university department already pays for, usually on a subdomain, sometimes behind a login, very often with the branding replaced. As of October 2026 we detect Ushahidi on 1 site, and every one of those structural habits pushes the figure down rather than up. Public, identifiable, still-running deployments are the only ones a crawler can confirm. Rebranded installs are the hardest case of all, since the code is meant to be adapted and the groups adapting it have every reason to make the result look like their own project rather than like a downloaded platform.

For a researcher the interesting query runs the opposite way from a domain lookup. Given the technology, which institutions have stood up a public reporting platform, on what kind of domain, and alongside what else. Civic technology funders use that view to see where the tooling they paid for actually landed. Journalists use it to find live deployments while an event is still running. Security researchers want it for a blunter reason, since a self-hosted application that nobody has logged into since the crisis ended is exactly the kind of thing that stops being patched. A per-domain check produces none of this, because the difficulty was never checking a domain, it was knowing which domains to check.