Built for Philippine barangays

When someone calls for help, the barangay already knows.

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.

Open the operations console →

Direct Android downloads, not Play Store installs iOS not yet available The console needs only a browser

Live
Every desk sees the same incident at the same moment
Offline
The field app keeps working without a signal
Audited
Decisions are recorded and cannot be edited after
Private
Internal notes never reach a resident's screen

Three points of view

Three apps, one incident.

Each one shows the same emergency from where that person stands — and nothing more than they should see.

Resident

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.

  • Police, fire, medical, or barangay assistance
  • Photos and exact location attached to the report
  • Live status, from received to resolved
  • Safety alerts and barangay hotlines in one place

Responder

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.

  • Accept or decline, with a reason that reaches the desk
  • En route, on site, resolved — recorded as it happens
  • Field notes and updates the resident can safely see
  • Keeps working with no signal, and syncs when it returns

Operations

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.

  • Live map of incidents, units, and responders
  • Dispatch with the right unit type enforced
  • Residents, units, responders, CCTV and hotlines
  • An audit entry behind every decision
apps, one incident record
3
apps, one incident record
kinds of emergency: police, fire, medical, barangay
4
kinds of emergency: police, fire, medical, barangay
steps, each signed by a person
5
steps, each signed by a person
ways to edit or delete an audit entry
0
ways to edit or delete an audit entry

The life of an incident

From the first tap to the final sign-off.

MCR-2026-000042

Structure fire · 31 Chino Roces Avenue

Zone 4 — Chino Roces · reported from the resident app

High
  1. Reported 9:42

    Alfredo Sarmiento

  2. Verified 9:43

    Marisol Villanueva

  3. Dispatched 9:44

    Fire Rescue 1 · PDP-F1

  4. On scene 9:51

    Joel M. Ferrer

  5. Resolved 10:07

    Outcome recorded · rated 5/5

Resident sees

“We received your report. The desk is looking at it now.”

“Your report has been verified. A unit is being assigned.”

“Fire Rescue 1 is on the way. About 4 minutes.”

“A fire unit is on scene.”

“Resolved. How did we do?”

Desk also sees

2 photos · handset location ±12 m

Not a duplicate · priority set to High

Instruction to unit: gate code 4417

Gate code 4417 · approach from Chino Roces

Audit: 9 entries · locked

  1. 01

    A resident reports

    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.

  2. 02

    The desk verifies

    A duplicate, a test, or a real emergency. Verification is a decision someone makes and signs, not a status that changes by itself.

  3. 03

    A unit is dispatched

    With a responder attached and an instruction only they can see. The system will not send an ambulance to a fire.

  4. 04

    The field answers

    Accepted, en route, on site. The resident sees plain-language progress; the desk sees everything.

  5. 05

    It closes, and it is on record

    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.

Properties, not settings

What the system guarantees.

An emergency record is evidence. These are properties of how it is built, not settings someone can switch off later.

Nothing is decided by accident

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.

Residents never see internal notes

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.

The record cannot be rewritten

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.

Permissions are enforced by the server

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.

Install

Get the apps.

Android builds are installable now. iOS is not yet available — distributing it needs an Apple Developer account, and we would rather say so than leave a button that does nothing.

Resident app

For residents of the barangay

Download for Android iOS — not yet available

Responder app

For accredited responders and tanod

Download for Android iOS — not yet available

These are direct APK downloads, not Play Store installs. Android will ask you to allow installation from this source. The responder app only works for accounts a barangay official has enrolled.

The operations console runs in a browser.

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.

Open the console →