RedAlert vs ESO: Fire First, Not EMS First

A side-by-side look at two records platforms: one built for the fire service from the start, and one built around EMS with a fire suite alongside.

  • Fire first, not EMS first. Alpine has built fire department software since 1994. ESO was founded in 2004 as an electronic patient care records company, and its own materials describe it as the leading ePCR vendor in the prehospital space.
  • Built around your department. Add custom fields, custom forms, and custom workflows to any record in the system, and every field flows straight into your reporting. When you need something more involved, like a custom report, Alpine's team in Rochester builds it with you. Platforms built to serve EMS agencies, fire departments, and hospitals nationwide are designed around a standard product. RedAlert is built to be changed.
  • Alerting built in, not partnered. The RedAlert Responder App is our own, so your members get alerted, respond, and report on the call all in RedAlert. ESO publicly describes mobile dispatch alerting through a partnership with IamResponding.
  • Your map, in your hand and on the rig. Crews plot hydrants, edit preplans, and draw incident perimeters in the Responder App on their own phones, and RedAlert MDT puts the live CAD feed, your preplans, and your hydrants on every apparatus tablet. No ESO-branded MDT appears in ESO's public product listings.
  • Attendance you can actually defend. The RedAlert Kiosk is station-mounted biometric check-in with call-triggered time windows, built for LOSAP, stipend, and pay-per-call programs.
  • Buy the modules you need. RedAlert is priced per module, so a volunteer department does not pay for an EMS ecosystem it will never open.
  • White-glove onboarding. A dedicated, Rochester-based project lead manages your rollout, migrates your data with nothing lost, configures the system, and runs weekly meetings with your team until you are live.
  • Support from Rochester, New York. Real people you can call and email, onshore, in the same building as the engineers who build the software.

Choose RedAlert if...

  • You are a fire department first, and want software built that way from the ground up
  • You need custom fields, forms, and workflows built around your department, not a standard enterprise product
  • You want alerting, en-route mapping, and records from one vendor instead of two
  • You need verifiable attendance for a LOSAP, pay-per-call, stipend, or points program
  • You want crews plotting hydrants and updating preplans in the Responder App, and the full picture on the apparatus tablet
  • You run a volunteer or combination department and want to buy only the modules you will use
  • You want a dedicated project lead who migrates your data, configures your system, and meets with your team weekly until you are live
  • You want to call a U.S.-based support team and reach someone who knows your system

Consider ESO if...

  • EMS is your agency's primary workload and patient care reporting drives your operation
  • You need ePCR and fire incident reporting in the same vendor ecosystem
  • You want one enterprise vendor spanning EMS, fire, and hospital data exchange

NERIS Compliant

Listed on FSRI's own integration partners page.

Since 1994

Over 1,000 departments and 200,000 first responders.

Onshore Support

Rochester, NY. Same building as engineering.

Configured to You

Custom fields, forms, and reports on any record.

Side by Side Comparison

Built Around Your Department

Category RedAlert ESO What This Means
Custom Fields & Workflows Table-driven SQL architecture. Departments add dropdowns, checkboxes, and free text fields to any record in the system (incidents, personnel, apparatus, properties, training, and attendance) and set up workflows around how they operate, with Alpine's team building anything more involved. Publicly markets agency-defined inspection checklists and configurable fire code sets. If your department tracks it, it can be a field, on any record in the system. Your team adjusts fields and forms as your needs change, and Alpine's team in Rochester builds the bigger pieces with you.
Custom Forms The forms your members fill out are built to your department: truck checks, training records, fire reports, special studies, plus-one codes, property inspection checklists, personnel records, and more, with your own fields. Publicly markets configurable digital checklists for vehicles, equipment, places, and people. Your members fill out forms your department designed, not a generic template, and every field they complete is available for reporting.
Reporting & Analytics Hundreds of built-in reports across every module, plus custom reports built by Alpine's engineering team. Every custom field and form feeds reporting, which is how custom payroll, ISO, OSHA, and point-program reports get built. Publicly markets ESO Insights analytics dashboards, including NERIS-specific dashboards. When the report you need does not exist, Alpine's engineering team builds it. Thirty years of department requests are why most of what you need is already there.

Operations

Category RedAlert ESO What This Means
Incident Reporting & NERIS NERIS Compliant. Incident templates, one-click narrative generation, custom plus-one codes, and a validator that catches errors before submission. Reports can be started from the apparatus tablet, a phone, or a desk. Publicly markets NERIS compliance. ESO's published implementation timeline describes a January 2026 go-live followed by a move to a weekly release cadence to stabilize the experience post-launch. RedAlert reports start before anyone sits down: from the rig on scene, from a phone, or at a desk. Templates handle the calls you run every week, and the narrative generates in one click.
Pre-Incident Planning & Mapping Preplans, properties, hazmat, dispatch warnings, site plans, and contacts can be created and edited in the Responder App on a phone or tablet, as well as in Desktop. Crews plot properties, hydrants, and points of interest onto the map from the field, with day, night, and satellite views and custom layers per user. Parent and child property relationships for malls, campuses, and complex sites. Publicly markets Properties and Inspections with mobile-first inspections and hazard maps built for crews. The crew walking the building updates the preplan from a phone while standing in it, and that same record reaches every responder through RedAlert's own apps, not a partner's.
Field Mapping & Incident Shapes Members draw polygons, lines, and circles on the map in the Responder App: a fire perimeter, a road closure, a staging radius. Shapes can be tied to a NERIS incident, styled by color and opacity, and set to expire at a date and time. Responding units and responding personnel appear on the same map. Publicly markets hazard maps within Properties and Inspections. Responder tracking is publicly described through a partnership with IamResponding. Draw the perimeter, mark the road closure, or set the staging area from the scene, and every member looking at the map sees it. Shapes expire on their own, so last week's closure is not cluttering this week's map.
Hydrants & Water Supply Crews view, plot, inspect, and flow test hydrants in the Responder App on a phone or tablet. Enter the full three-outlet flow test and a one-tap calculation returns available flow at 0, 10, and 20 psi, then writes the results back to the hydrant record, including its NFPA class. Out-of-service hydrants show darkened on the responder's map, and primary, secondary, and tertiary hydrants attach to each preplan. Import from CSV, GIS, and shapefiles. Publicly markets a hydrants module for recording hydrant data, tracking maintenance, and improving situational awareness. The flow test happens at the hydrant, on a phone, and the math is done for you. An out-of-service hydrant goes dark on the map automatically, every preplan that depended on it is flagged, and flow test curves print in the format ISO reviewers expect.
Fire Prevention & Inspections iPad inspections with your own occupancy types, permit types, and violation code sets. Permits generated from inspections with automatic renewal letters. Investigations case management with court-ready reports. Publicly markets Properties and Inspections with configurable checklists and fire code sets, plus a separate Permits module. Inspection findings reach responding crews through RedAlert's own Responder and MDT, so a hazard written up on Tuesday is on screen at the next call to that address.
Training & Certifications Course records, certification expiration tracking with advance warning, event scheduling, and verified attendance capture at the Kiosk. Publicly markets personnel management covering training, certifications, credentials, and work history. Drill attendance comes from verified check-in instead of a sign-in sheet, and training hours feed your point or stipend program automatically.
Assets, Inventory & Maintenance Four record types with their own fields: general inventory, SCBA testing, hose testing, and apparatus. Location tracking down to the compartment and shelf. QR and barcode scanning from any phone or tablet. Work orders with parts, labor, and vendor cost. Publicly markets digital checklists to capture the condition of vehicles, equipment, places, and people. Truck checks happen in the bay by scanning a QR code with any phone. A failed check opens a work order that tracks the part, the labor, and the vendor cost through to completion.
Attendance, LOSAP & Award Programs The RedAlert Kiosk: station-mounted biometric check-in by fingerprint, key fob, or ID card, with photo verification and CAD-triggered time windows that lock automatically. Point, stipend, and pay-per-call programs configured to your plan document. Attendance can also be recorded in Desktop or Mobile without the Kiosk. ESO publicly describes LOSAP tracking within ESO Activities, and FIREHOUSE Software, which ESO owns, includes a LOSAP points report. No station-mounted check-in hardware appears in ESO's public materials. Tracking points and verifying attendance are different things. RedAlert's Kiosk requires the member's own fingerprint or credential, at the station, inside a window the call defined, with a photo. If your program distributes public money, that is the record that holds up.

Personnel and Scheduling

Category RedAlert ESO What This Means
Personnel & Roster One member record driving alerting, station check-in, app access, training, certifications, and response history. Permissions configured to your command structure down to the field level. Publicly markets personnel management for training, certifications, credentials, work history, demographics, immunizations, and injuries and exposures. Add a member once and that record drives their alerting, check-ins, app access, and training file, with no separate roster to keep in sync with an alerting partner.
Scheduling Any repeating rotation, time codes and accrual banks built to your definitions, custom payroll reports formatted for your payroll system, and duty crew shifts measured against actual Kiosk clock-in. Publicly markets scheduling with call-outs, shift swaps, and time-off requests, integrated with incident records and common payroll systems. Payroll reports come out in the format your payroll system imports, built around your own time codes and accrual banks. Departments wanting fully automated shift coverage should evaluate that requirement specifically.
Mobile Access Native applications: RedAlert Mobile for field work, RedAlert Responder for alerting, and RedAlert MDT for the apparatus tablet. The full Desktop map runs in the Responder App, so members plot and edit properties, hydrants, points of interest, and incident shapes from their own phones. iOS and Android. Publicly markets mobile-first inspections. Mobile dispatch alerting is publicly described through a partnership with IamResponding. Field work, alerting, mapping, and the apparatus tablet are all RedAlert's own apps, on one roster and one login, supported by one vendor.

Technology and Integrations

Category RedAlert ESO What This Means
CAD Interface One interface that pre-fills the incident report with times, units, address, call type, and dispatcher comments, and simultaneously feeds the alerting app, the apparatus tablet, the station display, and the Kiosk attendance window. Available as a module. ESO's NERIS implementation timeline states that CAD data flows into NFIRS and NERIS incident records. One dispatch feed fills in the report, drives the Responder App, the MDT, and the Station Board, and opens the Kiosk for attendance on that exact call.
Alerting & Response RedAlert Responder: dispatch alerts to every member's phone, one-tap response status, GPS routing, and your own mapping. Responding units and personnel appear on the map with each member's photo and status. Includes Retone, letting a member on scene upgrade a call to a working fire or stand the department down. ESO publicly announced a partnership with IamResponding, which provides mobile dispatch alerts and real-time tracking alongside ESO's property, preplan, and hydrant data. Alerting is part of RedAlert, not a second vendor. Retone lets the first member on scene upgrade an automatic alarm to a working fire, or stand the department down, and push it to everyone still en route.
En-Route Data (MDT) RedAlert MDT: the live CAD feed, your hydrants and FDCs, and full preplans with hazards and utility shut-offs on every apparatus tablet. Crews can start the NERIS report from the same screen while still on scene. No ESO-branded mobile data terminal product appears in ESO's public fire product listings. The crew understands the building before stepping off the truck, on a mounted screen everyone can see, not a phone in someone's pocket.
Station Displays RedAlert Station Board turns any TV into a live command board during a call, and shows duty crew, out-of-service rigs, tasks due, and top responders between calls. Station dashboards showing ESO data, including call volume, response times, open reports, and the ESO Scheduling roster, are publicly described through an integration with First Arriving. The Station Board is part of RedAlert, so the firehouse screen runs on the same data, the same vendor, and the same support line as everything else.

Buyer Experience

Category RedAlert ESO What This Means
Fire Focus Alpine Software has built fire department software since 1994 and nothing else. Over 1,000 departments and 200,000 first responders. ESO describes itself as a pioneer in electronic patient care records software since its founding in 2004, and as the leading ePCR vendor in the prehospital space. Its fire business has grown through acquisitions of established fire records vendors, including FIREHOUSE Software in 2017 and Emergency Reporting in 2021. ESO's own announcement described the Emergency Reporting deal as bringing fire service breadth and depth to its health and safety ecosystem. Three decades of fire department software and nothing else. The depth shows in the parts nobody demos: point program rules, ISO-ready flow tests, and what happens when a truck check fails.
Pricing Model Priced per module. Departments buy the modules they will use and skip the ones they will not. Quotes provided directly. Marketed as a connected fire and EMS ecosystem spanning incidents, electronic health records, scheduling, and inspections. A volunteer department running 200 calls a year buys the fire modules it uses and skips the rest. It does not pay for an EMS ecosystem built for someone else's workload.
Contract Terms Annual contracts. Contract terms are not published publicly. RedAlert runs on annual contracts. Before signing with ESO, request the initial term, renewal terms, and any annual escalator in writing.
Procurement Path Direct purchase, or through a cooperative purchasing agreement if your agency requires one. Most departments buy directly. Public listings show ESO products available through software marketplaces. Buy directly, or through a cooperative purchasing agreement if your agency's process requires one.
Implementation & Onboarding 90 to 120 days typical, with a dedicated, Rochester-based project lead who manages the rollout, migrates your data with nothing lost, configures the system, and runs weekly meetings with your team through go-live. ESO's public FAQ describes an assigned project manager who runs a kick-off call and guides the agency to go-live, with onsite training days available. Ongoing product training is publicly delivered through on-demand courses, webinars, and the ESO Training Academy. One person in Rochester owns your rollout from kickoff to go-live, meets with your team every week, and brings your data over complete, including NFIRS history. White-glove from start to finish.
Best Fit Agency Size Any size, with particular depth for volunteer and combination departments. Publicly describes serving EMS agencies, fire departments, hospitals, and state EMS and trauma offices. Volunteer and combination departments are where RedAlert specializes: attendance programs, duty crews, and departments running without dedicated administrative staff.
Support Experience U.S.-based support team in Rochester, New York. Phone and email, real people, in the same building as the engineers who build the software. Public materials reference customer support as part of the platform offering. Call Alpine and you reach Rochester, New York: real people, onshore, in the same building as the engineers who build the software.

Built Around Your Department

Custom Fields & Workflows

RedAlert

Table-driven SQL architecture. Departments add dropdowns, checkboxes, and free text fields to any record in the system (incidents, personnel, apparatus, properties, training, and attendance) and set up workflows around how they operate, with Alpine's team building anything more involved.

ESO

Publicly markets agency-defined inspection checklists and configurable fire code sets.

What This Means

If your department tracks it, it can be a field, on any record in the system. Your team adjusts fields and forms as your needs change, and Alpine's team in Rochester builds the bigger pieces with you.

Custom Forms

RedAlert

The forms your members fill out are built to your department: truck checks, training records, fire reports, special studies, plus-one codes, property inspection checklists, personnel records, and more, with your own fields.

ESO

Publicly markets configurable digital checklists for vehicles, equipment, places, and people.

What This Means

Your members fill out forms your department designed, not a generic template, and every field they complete is available for reporting.

Reporting & Analytics

RedAlert

Hundreds of built-in reports across every module, plus custom reports built by Alpine's engineering team. Every custom field and form feeds reporting, which is how custom payroll, ISO, OSHA, and point-program reports get built.

ESO

Publicly markets ESO Insights analytics dashboards, including NERIS-specific dashboards.

What This Means

When the report you need does not exist, Alpine's engineering team builds it. Thirty years of department requests are why most of what you need is already there.

Operations

Incident Reporting & NERIS

RedAlert

NERIS Compliant. Incident templates, one-click narrative generation, custom plus-one codes, and a validator that catches errors before submission. Reports can be started from the apparatus tablet, a phone, or a desk.

ESO

Publicly markets NERIS compliance. ESO's published implementation timeline describes a January 2026 go-live followed by a move to a weekly release cadence to stabilize the experience post-launch.

What This Means

RedAlert reports start before anyone sits down: from the rig on scene, from a phone, or at a desk. Templates handle the calls you run every week, and the narrative generates in one click.

Pre-Incident Planning & Mapping

RedAlert

Preplans, properties, hazmat, dispatch warnings, site plans, and contacts can be created and edited in the Responder App on a phone or tablet, as well as in Desktop. Crews plot properties, hydrants, and points of interest onto the map from the field, with day, night, and satellite views and custom layers per user. Parent and child property relationships for malls, campuses, and complex sites.

ESO

Publicly markets Properties and Inspections with mobile-first inspections and hazard maps built for crews.

What This Means

The crew walking the building updates the preplan from a phone while standing in it, and that same record reaches every responder through RedAlert's own apps, not a partner's.

Field Mapping & Incident Shapes

RedAlert

Members draw polygons, lines, and circles on the map in the Responder App: a fire perimeter, a road closure, a staging radius. Shapes can be tied to a NERIS incident, styled by color and opacity, and set to expire at a date and time. Responding units and responding personnel appear on the same map.

ESO

Publicly markets hazard maps within Properties and Inspections. Responder tracking is publicly described through a partnership with IamResponding.

What This Means

Draw the perimeter, mark the road closure, or set the staging area from the scene, and every member looking at the map sees it. Shapes expire on their own, so last week's closure is not cluttering this week's map.

Hydrants & Water Supply

RedAlert

Crews view, plot, inspect, and flow test hydrants in the Responder App on a phone or tablet. Enter the full three-outlet flow test and a one-tap calculation returns available flow at 0, 10, and 20 psi, then writes the results back to the hydrant record, including its NFPA class. Out-of-service hydrants show darkened on the responder's map, and primary, secondary, and tertiary hydrants attach to each preplan. Import from CSV, GIS, and shapefiles.

ESO

Publicly markets a hydrants module for recording hydrant data, tracking maintenance, and improving situational awareness.

What This Means

The flow test happens at the hydrant, on a phone, and the math is done for you. An out-of-service hydrant goes dark on the map automatically, every preplan that depended on it is flagged, and flow test curves print in the format ISO reviewers expect.

Fire Prevention & Inspections

RedAlert

iPad inspections with your own occupancy types, permit types, and violation code sets. Permits generated from inspections with automatic renewal letters. Investigations case management with court-ready reports.

ESO

Publicly markets Properties and Inspections with configurable checklists and fire code sets, plus a separate Permits module.

What This Means

Inspection findings reach responding crews through RedAlert's own Responder and MDT, so a hazard written up on Tuesday is on screen at the next call to that address.

Training & Certifications

RedAlert

Course records, certification expiration tracking with advance warning, event scheduling, and verified attendance capture at the Kiosk.

ESO

Publicly markets personnel management covering training, certifications, credentials, and work history.

What This Means

Drill attendance comes from verified check-in instead of a sign-in sheet, and training hours feed your point or stipend program automatically.

Assets, Inventory & Maintenance

RedAlert

Four record types with their own fields: general inventory, SCBA testing, hose testing, and apparatus. Location tracking down to the compartment and shelf. QR and barcode scanning from any phone or tablet. Work orders with parts, labor, and vendor cost.

ESO

Publicly markets digital checklists to capture the condition of vehicles, equipment, places, and people.

What This Means

Truck checks happen in the bay by scanning a QR code with any phone. A failed check opens a work order that tracks the part, the labor, and the vendor cost through to completion.

Attendance, LOSAP & Award Programs

RedAlert

The RedAlert Kiosk: station-mounted biometric check-in by fingerprint, key fob, or ID card, with photo verification and CAD-triggered time windows that lock automatically. Point, stipend, and pay-per-call programs configured to your plan document. Attendance can also be recorded in Desktop or Mobile without the Kiosk.

ESO

ESO publicly describes LOSAP tracking within ESO Activities, and FIREHOUSE Software, which ESO owns, includes a LOSAP points report. No station-mounted check-in hardware appears in ESO's public materials.

What This Means

Tracking points and verifying attendance are different things. RedAlert's Kiosk requires the member's own fingerprint or credential, at the station, inside a window the call defined, with a photo. If your program distributes public money, that is the record that holds up.

Personnel and Scheduling

Personnel & Roster

RedAlert

One member record driving alerting, station check-in, app access, training, certifications, and response history. Permissions configured to your command structure down to the field level.

ESO

Publicly markets personnel management for training, certifications, credentials, work history, demographics, immunizations, and injuries and exposures.

What This Means

Add a member once and that record drives their alerting, check-ins, app access, and training file, with no separate roster to keep in sync with an alerting partner.

Scheduling

RedAlert

Any repeating rotation, time codes and accrual banks built to your definitions, custom payroll reports formatted for your payroll system, and duty crew shifts measured against actual Kiosk clock-in.

ESO

Publicly markets scheduling with call-outs, shift swaps, and time-off requests, integrated with incident records and common payroll systems.

What This Means

Payroll reports come out in the format your payroll system imports, built around your own time codes and accrual banks. Departments wanting fully automated shift coverage should evaluate that requirement specifically.

Mobile Access

RedAlert

Native applications: RedAlert Mobile for field work, RedAlert Responder for alerting, and RedAlert MDT for the apparatus tablet. The full Desktop map runs in the Responder App, so members plot and edit properties, hydrants, points of interest, and incident shapes from their own phones. iOS and Android.

ESO

Publicly markets mobile-first inspections. Mobile dispatch alerting is publicly described through a partnership with IamResponding.

What This Means

Field work, alerting, mapping, and the apparatus tablet are all RedAlert's own apps, on one roster and one login, supported by one vendor.

Technology and Integrations

CAD Interface

RedAlert

One interface that pre-fills the incident report with times, units, address, call type, and dispatcher comments, and simultaneously feeds the alerting app, the apparatus tablet, the station display, and the Kiosk attendance window. Available as a module.

ESO

ESO's NERIS implementation timeline states that CAD data flows into NFIRS and NERIS incident records.

What This Means

One dispatch feed fills in the report, drives the Responder App, the MDT, and the Station Board, and opens the Kiosk for attendance on that exact call.

Alerting & Response

RedAlert

RedAlert Responder: dispatch alerts to every member's phone, one-tap response status, GPS routing, and your own mapping. Responding units and personnel appear on the map with each member's photo and status. Includes Retone, letting a member on scene upgrade a call to a working fire or stand the department down.

ESO

ESO publicly announced a partnership with IamResponding, which provides mobile dispatch alerts and real-time tracking alongside ESO's property, preplan, and hydrant data.

What This Means

Alerting is part of RedAlert, not a second vendor. Retone lets the first member on scene upgrade an automatic alarm to a working fire, or stand the department down, and push it to everyone still en route.

En-Route Data (MDT)

RedAlert

RedAlert MDT: the live CAD feed, your hydrants and FDCs, and full preplans with hazards and utility shut-offs on every apparatus tablet. Crews can start the NERIS report from the same screen while still on scene.

ESO

No ESO-branded mobile data terminal product appears in ESO's public fire product listings.

What This Means

The crew understands the building before stepping off the truck, on a mounted screen everyone can see, not a phone in someone's pocket.

Station Displays

RedAlert

RedAlert Station Board turns any TV into a live command board during a call, and shows duty crew, out-of-service rigs, tasks due, and top responders between calls.

ESO

Station dashboards showing ESO data, including call volume, response times, open reports, and the ESO Scheduling roster, are publicly described through an integration with First Arriving.

What This Means

The Station Board is part of RedAlert, so the firehouse screen runs on the same data, the same vendor, and the same support line as everything else.

Buyer Experience

Fire Focus

RedAlert

Alpine Software has built fire department software since 1994 and nothing else. Over 1,000 departments and 200,000 first responders.

ESO

ESO describes itself as a pioneer in electronic patient care records software since its founding in 2004, and as the leading ePCR vendor in the prehospital space. Its fire business has grown through acquisitions of established fire records vendors, including FIREHOUSE Software in 2017 and Emergency Reporting in 2021. ESO's own announcement described the Emergency Reporting deal as bringing fire service breadth and depth to its health and safety ecosystem.

What This Means

Three decades of fire department software and nothing else. The depth shows in the parts nobody demos: point program rules, ISO-ready flow tests, and what happens when a truck check fails.

Pricing Model

RedAlert

Priced per module. Departments buy the modules they will use and skip the ones they will not. Quotes provided directly.

ESO

Marketed as a connected fire and EMS ecosystem spanning incidents, electronic health records, scheduling, and inspections.

What This Means

A volunteer department running 200 calls a year buys the fire modules it uses and skips the rest. It does not pay for an EMS ecosystem built for someone else's workload.

Contract Terms

RedAlert

Annual contracts.

ESO

Contract terms are not published publicly.

What This Means

RedAlert runs on annual contracts. Before signing with ESO, request the initial term, renewal terms, and any annual escalator in writing.

Procurement Path

RedAlert

Direct purchase, or through a cooperative purchasing agreement if your agency requires one. Most departments buy directly.

ESO

Public listings show ESO products available through software marketplaces.

What This Means

Buy directly, or through a cooperative purchasing agreement if your agency's process requires one.

Implementation & Onboarding

RedAlert

90 to 120 days typical, with a dedicated, Rochester-based project lead who manages the rollout, migrates your data with nothing lost, configures the system, and runs weekly meetings with your team through go-live.

ESO

ESO's public FAQ describes an assigned project manager who runs a kick-off call and guides the agency to go-live, with onsite training days available. Ongoing product training is publicly delivered through on-demand courses, webinars, and the ESO Training Academy.

What This Means

One person in Rochester owns your rollout from kickoff to go-live, meets with your team every week, and brings your data over complete, including NFIRS history. White-glove from start to finish.

Best Fit Agency Size

RedAlert

Any size, with particular depth for volunteer and combination departments.

ESO

Publicly describes serving EMS agencies, fire departments, hospitals, and state EMS and trauma offices.

What This Means

Volunteer and combination departments are where RedAlert specializes: attendance programs, duty crews, and departments running without dedicated administrative staff.

Support Experience

RedAlert

U.S.-based support team in Rochester, New York. Phone and email, real people, in the same building as the engineers who build the software.

ESO

Public materials reference customer support as part of the platform offering.

What This Means

Call Alpine and you reach Rochester, New York: real people, onshore, in the same building as the engineers who build the software.

This comparison is based on publicly available information including vendor websites, public documentation, and press releases listed in the sources section below. Features, pricing, and packaging may change. We encourage buyers to verify current capabilities directly with each vendor before making a purchasing decision.

See It in Action

  • Alerting, en-route mapping, and records from one vendor
  • Preplans, hydrants, and hazards on the apparatus tablet before arrival
  • Verified attendance that holds up in an audit
RedAlert Responder app call screen on a phone, showing an aerial map with hydrants, a dispatch warning, and occupancy location details

Where RedAlert Stands Out

Fire First, Not EMS First

Alpine Software has built software for the fire service since 1994. Not EMS with a fire suite added later, not a hospital data company with a fire product line. Fire departments, for three decades.

It shows in the parts of the product nobody demos: how a LOSAP program is configured, how a hydrant flow test prints for ISO, what happens to a truck check when it fails. Those details exist because fire departments asked for them over thirty years, not because they were adapted from a patient care workflow.

Built Around Your Department

RedAlert was built to be changed. Your department adds dropdowns, checkboxes, and free text fields to any record in the system: incidents, personnel, apparatus, properties, training, and attendance. Build the forms your members fill out and the workflows your department actually follows, and adjust them as your needs change. When something is more involved, Alpine's team in Rochester builds it with you, during implementation and after.

Every one of those fields flows straight into reporting. That is how departments get payroll reports built around their own time codes, ISO documentation formatted the way their reviewer wants it, point calculations for a LOSAP plan nobody else runs, and their own data points captured on every call report.

Platforms built to serve EMS agencies, fire departments, and hospitals across the country are designed around a standard product that every customer shares. RedAlert is built to be changed.

Alerting Built In, Not Partnered

RedAlert Responder is our own alerting app. Dispatch drops the call and every member's phone lights up with the address, call type, and details. Members tap responding, command sees who is coming and from where, and turn-by-turn routing puts them on scene.

When alerting comes from a partner, your department runs two vendors, two rosters, two logins, and two support numbers, and the alert and the record live in different systems. With RedAlert, the member who gets alerted is the same member record your training, certifications, and attendance live on.

With the Responder App, the whole call stays in RedAlert: get alerted, respond, and report on the call, without switching systems or vendors.

Retone: The Crew on Scene Can Change the Call

Dispatch sends what it has. What is actually there is often something else. A member arriving at an automatic alarm who finds smoke showing can upgrade the call to a working fire and push an all-hands alert to every phone. A member who finds a false alarm can stand the department down so nobody else drives to a call that does not exist.

One tap from the scene, and everyone still en route knows what is actually happening.

The Building on the Tablet Before Arrival

RedAlert MDT puts the live CAD feed on every apparatus tablet, not just the command vehicle, alongside your own mapping layers and full preplan data: hazards, utility shut-offs, site plans, and occupancy information.

The seconds between dispatch and arrival are when most of the decisions get made. A crew that has seen the building on a mounted screen during the drive steps off the truck already knowing where the water is and what is inside.

Your Map, in Your Hand

The full RedAlert map runs in the Responder App on members' phones and tablets, with day, night, and satellite views and the custom layers each member chooses. Crews plot properties, hydrants, and points of interest from the field, update preplans, hazmat, and site plans while standing in the building, and run a full hydrant flow test at the hydrant, with available flow calculated in one tap.

On scene, members draw what everyone else needs to see: a fire perimeter, a road closure, a staging radius. Shapes can be tied to the NERIS incident and set to expire on their own. Responding units and personnel appear on the same map, and an out-of-service hydrant shows dark so nobody hooks up to it.

Inspection findings travel the same way. A hazard an inspector writes up on Tuesday is on the tablet at the next call to that address, because the inspector and the engine company are looking at the same record.

Attendance You Can Defend

The RedAlert Kiosk is a station-mounted touchscreen where members check in by fingerprint, key fob, or building ID card. It opens on a CAD trigger when the call comes in, locks automatically after a window your department sets, and photographs every check-in.

If your department distributes LOSAP points, stipends, or per-call pay, that attendance record is an accounting document. The difference between attendance that is reported and attendance that is proven is the difference between a number your board accepts and a number your board can defend.

One Dispatch Connection, Every Screen

The RedAlert CAD interface pre-fills the incident report with times, units, address, call type, and dispatcher comments. The same feed drives the Responder App on members' phones, MDT on the apparatus tablet, and the Station Board on the firehouse wall, and it opens the Kiosk for attendance on that exact call.

One connection to your dispatch center, every screen and every record kept in step.

Buy the Modules You Need

RedAlert is priced per module. A volunteer department running 200 calls a year can buy incident reporting, alerting, and attendance, and skip the rest.

An ecosystem built around EMS, electronic health records, and hospital data exchange is efficient for an agency that runs all of it. For a fire department that does not, it often means paying for a platform designed around someone else's workload.

White-Glove Onboarding, From Rochester

Every RedAlert implementation gets a dedicated project lead based in Rochester, New York. They manage the rollout, migrate your data from your prior system with nothing lost, configure RedAlert to how your department operates, and run weekly meetings with your team until you are live, typically in 90 to 120 days.

Switching records systems is the part departments dread most. Having one person who knows your department, your data, and your timeline, sitting down the hall from the engineers who build RedAlert, turns a migration from a project you manage into one that is managed for you.

Onshore Support in Rochester, New York

When you call Alpine, you reach Rochester. Real people, in the United States, in the same building as the engineers who build RedAlert.

Support quality is usually the first thing to slip as a software company scales, and the distance between the person answering your call and the person who can fix your problem is what determines whether it gets fixed.

How RedAlert Fits Into Your Software Stack

RedAlert is an all-in-one fire department software platform combining fire RMS, incident reporting and NERIS, alerting and mobile response, pre-incident planning and mapping, hydrants, and attendance and award programs in one database. Many departments comparing RedAlert and ESO are deciding between an EMS-centered ecosystem with alerting supplied by a partner, and a fire-first platform where alerting, en-route data, and records come from one vendor.

The call your crew runs is alerted through RedAlert Responder, mapped on the apparatus tablet, shown on the station wall, and recorded as the incident report and the attendance behind your point program, all from the same CAD interface and the same member record.

Built for the NERIS Transition

NERIS replaced NFIRS as the national fire incident reporting standard in January 2026, and RedAlert is NERIS Compliant, with Alpine listed on FSRI's own integration partners page.

NERIS compliance is now the baseline, not the differentiator. The question that matters is how much work the reporting actually takes. Incident templates for the calls you run constantly, one-click narrative generation from call type and actions taken, custom plus-one codes for whatever your county or state wants tracked, and validation that catches errors before submission rather than after the state sends them back. And with RedAlert MDT, the report can be started on the apparatus tablet while the crew is still on scene.

If your department fell behind during the transition, we convert your NFIRS records rather than making you re-enter them.

When ESO May Be the Right Choice

No single platform is right for every department. ESO has built a broad ecosystem that serves a real segment of the emergency services. Here are scenarios where ESO may be the stronger fit:

  • EMS is your agency's primary workload.

    ESO's own materials describe the company as the leading ePCR vendor in the prehospital space. If patient care reporting drives your operation and fire incidents are the smaller share, an EMS-centered platform is built around your largest workload. RedAlert is a fire records system and does not provide NEMSIS-compliant patient care reporting. Departments that document basic patient information as part of a BLS response can capture it through custom fields on the incident record.

  • You need fire and EMS documentation in one vendor ecosystem.

    ESO publicly markets integration between its fire incident reporting and its electronic health record, so a single call can produce both reports. If that combined workflow is a requirement, ESO addresses it directly.

  • You are consolidating EMS, fire, and hospital data exchange under one enterprise vendor.

    ESO publicly describes serving EMS agencies, fire departments, hospitals, and state EMS and trauma offices. If your strategic goal is one vendor across that whole ecosystem, ESO's breadth may support it. RedAlert is focused on fire operations and does not try to be everything to every agency.

If these scenarios describe your department, evaluate both platforms on their merits. If they do not, RedAlert is likely the more practical choice.

Pricing and Contracts: A Different Philosophy

RedAlert

  • Priced per module, so you buy only what you will use
  • Volunteer and combination departments can start small and add later
  • Everything you add shares the same database and member records
  • Alerting, en-route data, and records from one vendor
  • A dedicated, Rochester-based project lead for every implementation
  • Annual contracts
  • Direct purchase, or through a cooperative purchasing agreement if required

ESO

  • Marketed as a connected fire and EMS ecosystem
  • Spans fire incidents, electronic health records, scheduling, inspections, and analytics
  • Mobile dispatch alerting publicly described through a partnership with IamResponding
  • Station dashboards publicly described through an integration with First Arriving
  • Contract terms are not published publicly
  • Products available through software marketplace listings

What this means for buyers

  • With RedAlert, every line on your quote is a module you can decline. A department that will never run inspections does not pay for inspections.
  • Alerting is part of the platform, so there is no second vendor, second roster, or second contract to manage for it.
  • An EMS-centered ecosystem is efficient for an agency whose largest workload is patient care. For a fire department, it often means paying for a platform designed around someone else's priorities.

Disclaimer: Pricing, fees, and contract terms change over time and vary by vendor, agency size, module selection, and negotiation. The information above reflects publicly available sources and should not be treated as current or universal pricing. Always confirm current pricing and contract terms directly with each vendor during your evaluation.

Frequently Asked Questions

Is RedAlert cheaper than ESO?

It depends on what your department needs, and that is the point. RedAlert is priced per module, which means a fire department can buy incident reporting, alerting, and attendance tracking without paying for EMS or hospital data tools it will not use. And because alerting is part of RedAlert, there is no second alerting vendor to budget for.

Does RedAlert support NERIS?

Yes. RedAlert is NERIS Compliant and Alpine is listed on FSRI's integration partners page. NERIS templates, validation, and submission are part of the platform rather than a separately priced module, and reports can be started from the apparatus tablet while the crew is still on scene.

Can RedAlert be customized to our department's forms and workflows?

Yes, and it is one of the main reasons departments choose us. RedAlert was built to be changed: your department adds dropdowns, checkboxes, and free text fields to any record in the system, builds the forms your members fill out (truck checks, training records, fire reports, special studies, plus-one codes, property inspection checklists, and personnel records), and sets up workflows around how you operate. Every field flows into reporting, and when you need something more involved, like a custom report, Alpine's team in Rochester builds it with you.

Is ESO fire software or EMS software?

Both, but ESO was founded in 2004 as an electronic patient care records company, and its own materials describe it as the leading ePCR vendor in the prehospital space. Its fire business has grown through acquisitions of established fire records vendors, including FIREHOUSE Software and Emergency Reporting. RedAlert has been built for fire departments since 1994 and does not provide NEMSIS-compliant patient care reporting. If your agency is fire first, that difference shapes everything from attendance programs to how your crews are alerted.

Does ESO have its own mobile alerting app?

ESO publicly announced a partnership with IamResponding, which provides mobile dispatch alerts and real-time tracking alongside ESO's property, preplan, and hydrant data, and IamResponding's support documentation describes the integration. RedAlert Responder is Alpine's own alerting app, on the same roster and the same login as the rest of the platform.

What does RedAlert give my crew on the way to a call?

On every member's phone, RedAlert Responder shows the call details, routing, and your own mapping with hydrants and preplans. On the apparatus tablet, RedAlert MDT shows the live CAD feed alongside full preplan data: hazards, utility shut-offs, site plans, and occupancy information. Out-of-service hydrants are darkened on both, so the crew can see at a glance which water is usable. Responding units and personnel appear on the same map, along with any perimeter or road closure drawn by members already on scene.

Can our crews plot hydrants and update preplans from a phone?

Yes. The full RedAlert map runs in the RedAlert Responder App, so members can plot and edit properties, hydrants, and points of interest from the field, update preplans, hazmat, dispatch warnings, and site plans, and run a complete hydrant flow test with available flow calculated in one tap. Members can also draw polygons, lines, and circles on the map, such as a fire perimeter or a road closure, and tie them to the NERIS incident. Every action is controlled by permissions you set.

How does RedAlert handle LOSAP and pay-per-call tracking?

Attendance can be recorded by an officer in RedAlert Desktop or RedAlert Mobile, or captured at the RedAlert Kiosk, where members check in by fingerprint or key fob inside a time window tied to the actual call. Point caps, category maximums, eligibility rules, and weighting are configured to your plan document. If your program distributes public money, the question that matters is how attendance is verified, not just how it is recorded.

Does ESO track LOSAP?

Yes. ESO publicly describes LOSAP tracking within ESO Activities, and FIREHOUSE Software, which ESO owns, includes a LOSAP points report. The difference is verification. The RedAlert Kiosk requires each member's own fingerprint or credential at a station-mounted device, inside a time window tied to the actual call, with a photo of every check-in. If your program distributes public money, the question that matters is how attendance is verified, not just how it is recorded.

What is Retone?

Retone lets a member change the status of an active call from the RedAlert Responder App and push that update to everyone. Arrive at an automatic alarm and find a working fire, and every member's phone gets an all-hands alert. Arrive and find a false alarm, and the department stands down so nobody else responds to nothing.

Does RedAlert do ePCR or patient care reporting?

RedAlert does not provide NEMSIS-compliant patient care reporting. It is a fire records management system, and departments that record basic patient information as part of a BLS response can capture it through custom fields on the incident record. ESO publicly markets patient care reporting through its electronic health record, integrated with its fire incidents application. If your agency needs fire and EMS documentation in one ecosystem, that is a genuine point in ESO's favor and worth weighing directly.

Can RedAlert integrate with our CAD system?

Yes, as a module. The CAD interface pre-fills the incident record with times, units, address, call type, and dispatcher comments, and the same feed drives the alerting app, the apparatus tablet, and the station display, and opens the Kiosk attendance window for that call. One connection to your dispatch center serves all of it.

How long does implementation take, and who runs it?

RedAlert implementations typically run 90 to 120 days. Every one gets a dedicated project lead based in Rochester who manages the rollout, migrates your data from your prior system with nothing lost, configures the system to your department, and runs weekly meetings with your team until you go live. The migration is done by our team, not handed to your officers as a project.

Can we migrate from ESO?

Yes. Alpine's onshore team migrates records from your prior vendor as part of every implementation, including historical NFIRS incident data. Your officers do not retype anything.

What does support look like with Alpine?

Alpine's support team is in Rochester, New York, in the same building as the engineers who build RedAlert. Phone and email, onshore, real people you can reach directly. When something needs fixing, the person you call can walk down the hall to the engineer who can fix it.

We are a volunteer department. Is RedAlert built for us?

Volunteer and combination departments are where Alpine specializes. The attendance and award program tools, the modular pricing, and the support model exist because volunteer departments needed them. RedAlert also serves career departments, but the depth in point tracking, duty crew hours, and station-level attendance comes from the volunteer side of the service.

Fire Departments Deserve Fire Software

RedAlert gives your department alerting, en-route data, records, and attendance from one vendor, built by people who have done one thing since 1994, supported by a team you can actually call.

Remote Support