Compare routes
Side-by-side routes with the reasons behind each risk level, not a single score you have to trust.
Android first.
Open source.
Open source ยท In development
Know what the route knows.
Nayki is an Android-first navigation app that shows the evidence behind each route: lighting, nearby help, reported incidents and time of day. It never calls a place safe. When it has no data, it says so.
What it is
A map that shows its homework.
Most maps give you one line and a time. Nayki is built to give you the line, the alternatives, and what is known about each. You choose.
See where help is
A help layer for places that can assist: open venues, transport points and services near the route.
Report what you saw
Incident reports are kept and counted as unverified user reports until something stronger backs them.
SOS in one tap
An SOS flow designed around saved contacts and push notifications. It supports, and never replaces, calling emergency services.
The rule
It never says safe.
Nayki reports lower, moderate or higher risk, or unknown, with a confidence value and a count of the evidence behind it. Where nothing is known, the answer is "unavailable", not an invented comfort.
{
"coverage_status": "unavailable",
"confidence": "low",
"evidence_count": 0,
"safety_score": null,
"risk_level": "unknown"
}This is the response the backend returns when it has no safety evidence for a place. It is the API's own rule, written in the README.
Where it stands
Honest status.
Some of this runs, some of it is a prototype, and some of it is still to be connected.
| Part | Status | What that means |
|---|---|---|
| Android app | Prototype | Jetpack Compose screens for map, search, route comparison, heatmap, help layer, incidents, SOS and profile. They run on sample data. |
| Backend API | In the repo | FastAPI with Postgres/PostGIS and Redis. Endpoints for auth, routes, places, incidents, safety, SOS and privacy, with tests. |
| App to API link | Not yet | The app does not call the backend yet. Connecting them is the first big job. |
| Real safety data | Not yet | Data sources are wired as integrations in code. No city has coverage today. |
Two routes, one choice
The shorter way is not always the one you want.
Nayki puts the options next to each other, with the reasons: poor lighting, an isolated road, help far away, a recent report, the time of night. You decide which trade-off to take.
Looking for
collaborators.
Build it with us
Safety tools are better built by many hands.
We need Android and backend developers, people who know open data, designers, accessibility reviewers, and teams who work on safety in their city. If that is you, come and build this.