WHAT’S NEXT
Volunteer servers, offline maps, an audit.
Field testing now. Then community servers run by volunteers, offline maps with positions straight from satellites, and an independent security audit. Later, an iPhone app.
See the roadmapABOUT MESHTRIKE · WHY WE BUILT IT
Towers overload, storms knock them down, and sometimes someone switches them off. Meshtrike exists so the people standing around you are still in reach when that happens.
01 · WHY WE BUILT IT
We kept seeing the same thing in very different places. The network goes, and people standing a few metres apart can’t send each other a single line of text.
The headliner comes on, everyone reaches for their phone, and the nearest tower gives up. Texts stall, calls drop, and the friend you lost by the stage might as well be in another city.
Phones within 10–30 m link directly
Networks get throttled or switched off on purpose, often exactly when people most need to find each other and stay safe. A messenger that depends on that network goes quiet with it.
Sealed end to end, relays can’t read it
Wind, floods and earthquakes knock out power and masts long before anything is repaired. The people who most need to check in are the ones with no bars at all.
A LoRa radio reaches kilometres
Trails, valleys, boats and camps. Beautiful places, and dead zones where a simple “I’m fine, back by six” has no way to travel.
Carried for up to 72 hours
THE IDEA
Every phone already has Bluetooth and Wi-Fi radios that can reach the next phone directly. So we let phones carry sealed messages for each other, hop by hop, until they reach the right person. No tower, no server, and nobody in between can read them.
See how the mesh works02 · WHAT WE STAND FOR
Not slogans. Each one is a decision already made in the code, so it can’t quietly change later.
The rules are built into every screen: no names in notifications, no screenshots, nothing that reveals who talks to whom. There is no switch that turns them off.
No phone number, no email, no sign-up. Your identity is a key made on your phone, and there is no Meshtrike server to hack or subpoena.
Every line is public under Apache-2.0. Every real APK is signed with one release key, and anyone can check their copy.
We say what Meshtrike can’t protect you from, and that it hasn’t been independently audited yet. Read the limits.
Duress PIN, panic wipe, High-Risk mode, and QR handoff when radio is jammed. Features for the days you hope never come.
Free to download, with no analytics, no crash reporting and nothing sent home. The build checks for trackers on every change.
No SIM, no number and no account to lose. Pseudonyms are welcome, one APK can be passed phone to phone, and anyone can help translate it.
03 · WHAT WE WILL NEVER DO
Promises are cheap, so here are only the ones Meshtrike already keeps today. Hover a line, or read the code, and hold us to every one of them.
We will never Ask for your phone number.
No number, no email, no sign-up. Your identity is a key on your phone.
We will never Read your messages.
They are sealed on your phone. There is no server, and no key we could use to open them.
We will never Collect or sell your data.
The app collects nothing, so there is nothing to sell. The privacy policy says so in full.
We will never Add trackers, analytics or crash reporting.
The build pipeline checks every change for telemetry packages.
We will never Give the messenger internet access.
It doesn’t hold Android’s internet permission, and the release check fails if it ever appears.
We will never Put names or message text in notifications.
Just “New message” or “Incoming call”. Never the sender, a preview or a photo.
We will never Keep a record of who talks to whom.
No message paths, no hop counts. The app doesn’t know them and never stores them.
We will never Require a server.
Community servers may help one day. None will ever be required.
We will never Ship an APK that isn’t signed with our release key.
Android refuses updates signed by anyone else, and you can check any copy yourself.
We will never Call it audited before it is.
Until an independent audit, treat Meshtrike as beta for high-risk use.
04 · THE PRINCIPLES IN CODE
Every principle above is enforced somewhere you can read, run or rebuild yourself.
Read the source on GitHub$ ci/pipeline.sh
=== tests ===
# 162 tests, incl. 27 end-to-end mesh scenarios
=== telemetry ===
OK: no telemetry packages
=== manifest ===
OK: release build has no INTERNET permission
PIPELINE PASSED
05 · WHO WE ARE
We’re a small, pseudonymous team. That’s deliberate: the people Meshtrike is for often can’t afford to be named, and the people who build it shouldn’t have to be either. So don’t take our word for anything. Judge us by the code, the whitepaper and how we handle problems.
Everything happens in the open on GitHub, except security reports, which go privately first.
Pseudonyms are welcome. You never need your real name to help. Think about your own safety before you post.
06 · JOIN US
A mesh is only as strong as the people in it. No sign-ups and no forms: pick something, and tell us on GitHub.
WHAT’S NEXT
Field testing now. Then community servers run by volunteers, offline maps with positions straight from satellites, and an independent security audit. Later, an iPhone app.
See the roadmapDOWNLOAD
Install it while you still have signal, pair with your people in person, and you’re ready for when the network drops. Free, open source, no account.
LICENSES AND CREDITS