Built for Philippine barangays
Micara911 connects the three people in every emergency — the resident who reports it, the responder who answers it, and the officer at the desk who decides who goes. One record, updated live, from the first tap to the final sign-off.
Structure fire · 31 Chino Roces Avenue
Zone 4 — Chino Roces · reported from the resident app
Alfredo Sarmiento
Marisol Villanueva
Fire Rescue 1 · PDP-F1
Joel M. Ferrer
Resident sees
“A fire unit is on scene.”
Desk also sees
Gate code 4417 · approach from Chino Roces
Each one shows the same emergency from where that person stands — and nothing more than they should see.
For everyone in the barangay
Report an emergency in a few taps, with your location and photos attached. Then watch what happens next — verified, dispatched, on the way — instead of wondering whether anyone heard you.
For units in the field
Assignments arrive with the address, the reporter, and the dispatcher's instruction. Accept, roll, arrive, and record what you found — without stopping to phone it in.
For the barangay desk
Every open incident on one map, with the units near it. Verify a report, choose who answers, and see the whole barangay's state without asking anyone for a status update.
From the app, with location and photos. Or the desk records a walk-in or a phone call the same way, so nothing lives outside the system.
A duplicate, a test, or a real emergency. Verification is a decision someone makes and signs, not a status that changes by itself.
With a responder attached and an instruction only they can see. The system will not send an ambulance to a fire.
Accepted, en route, on site. The resident sees plain-language progress; the desk sees everything.
Resolution, outcome, and a resident's rating. The audit trail cannot be edited or deleted afterwards.
Location comes from the reporting handset, and the system records it as reported. It is accurate enough to send a unit to, but it is not tamper-proof, and Micara911 does not claim otherwise — the desk always verifies before dispatching.
An emergency record is evidence. These are properties of how it is built, not settings someone can switch off later.
Verification, dispatch and closure are each a decision someone makes, attributed to them, with a reason. The system will not quietly advance an incident on its own.
A dispatcher's instruction to a unit and a resident's status update are different records. The resident-facing view is built from its own projection, not filtered on the way out.
There is no endpoint that edits or deletes an audit entry. What was decided, by whom, and when survives the incident — including the parts nobody is proud of.
What a role can do is checked on every request. Hiding a button is a courtesy to the person using the console, never the thing that stops them.
Builds are being prepared. Rather than post a link that installs an app you cannot sign in to, we will publish them when they work end to end.
For residents of the barangay
For accredited responders and tanod
When published, these will be direct APK downloads rather than Play Store installs, and the responder app will only work for accounts a barangay official has enrolled.
Nothing to install at the barangay hall. Sign in with the account your administrator issued — what you can see and do follows the role they gave you, enforced by the server rather than by hidden buttons.