Fire & rescue · Operational web applicationPilot testing · Tivat, Montenegro
FireNexa
FireNexa is an operational platform I am building for fire and rescue teams in Montenegro: it connects dispatchers, commanders and firefighters through call publication, crew responses, coordination and intervention records. The current mobile-friendly web version is in pilot use with teams in Tivat alongside their established notification process. Dedicated iOS and Android apps are planned after the pilot is evaluated.
- Type
- Fire & rescue · Operational web application
- Status
- Pilot testing · Tivat, Montenegro
The product path
One call. A coordinated response. A clear record.
I am developing FireNexa as a practical operating tool for fire and rescue teams. The current web version makes field testing possible across phones and computers. Feedback from that pilot will shape the next release.
- 01 · NOW
Pilot in Tivat
Teams test dispatch, member responses and records while their existing alerting method remains in place.
- 02 · PLANNED
iOS and Android apps
After evaluating the pilot and addressing field feedback, the plan is to develop dedicated mobile apps for everyday crew use.
My role
Product concept, workflow design, full-stack development and deployment.
Goal
Build a dependable operational workflow that reduces uncertainty between a call going out and a crew responding, while preserving the established notification channel during the pilot.
What was built
- A dispatch workflow to create and publish operational calls with an incident location, assembly point and clear instructions for the crew.
- A personal member view for acknowledging a call, reporting availability and following the intervention, attendance and response history.
- Distinct permissions for dispatchers, commanders and members; separate workspaces for DVD Tivat and the Protection and Rescue Service Tivat, with service selection for members of both.
- A responsive web app with optional browser push notifications, an intervention archive and operational records for reviewing what happened afterward.
Technical approach
- Designed around local fire and rescue workflows and rehearsed with explicitly marked exercise calls before pilot use.
- Service boundaries and role permissions are enforced on the server, rather than relying on what the interface happens to show.
- The pilot runs in parallel with established alerting. FireNexa is for internal team operations, not a channel for the public to report emergencies.
Inside the working app

An actual interface
The call, the response and the next step — in view.
One screen brings together what a member needs when a call arrives: the incident, assembly point, instructions and the response they have already sent. The example comes from an explicitly marked test call, not a live emergency.
Technologies
- React
- TypeScript
- Supabase
- PostgreSQL
- Row Level Security
- Web Push
- PWA
- Netlify