ESO is one of the largest software companies in public safety, and plenty of departments run its products without complaint. But its fire RMS is sold the enterprise way: module by module, quote by quote, with the number disclosed after the demo. If you're on this page, you've probably seen one of those quotes — or one of the renewal letters that follow.
Everything below comes from documents anyone can check: a city's published ESO invoice, council records, and named news reporting.
What a One-Station Department Actually Pays
The City of Nevada, Missouri published its ESO invoice — one station, three vehicles, thirteen personnel, covering a roughly fourteen-month term from November 2023 through January 2025. Eight modules, eight line items:
From the published invoice, covering Nov 22, 2023 – Jan 21, 2025. The migration line items (NFIRS $2,995, properties $995, personnel $130) were discounted to $0 for this customer. The fine print notes agreements "may include annual uplift" and usage-based quantity increases.
A second public payment record shows how the module total and an API-access charge can land separately. The City of Lawrence, Kansas's May 5, 2026 claim report records Lawrence-Douglas County Fire Medical paying $14,060.02 for an ESO annual module renewal, plus $2,805.35 for "Data API Access in ESO Fire RMS Suite." That's one customer's payment record, not a universal ESO price sheet — but it is a reason to ask which API or data-access services sit outside the annual module renewal.
Every one of those line items is a feature we include — along with scheduling, training, permits, work orders, budgets, and more than a dozen others that would each be another row on that invoice.
Everything on that invoice — incidents, inspections, hydrants, checklists, assets, personnel — plus fourteen more modules, unlimited users, $0 setup. Pricing page.
The year-five price in a renewal proposal that Bridgton, ME declined after starting near $2,500/yr on Emergency Reporting — the department left instead. Rockport reported its actual cost more than doubled in two years. Source: WGME I-Team.
Figures last reviewed July 2026. Always confirm current pricing with the vendor.
The Migrations Nobody Asked For
Cost is half the story. Lebanon, Missouri's council record from 2022 reports its FIREHOUSE Software installation was already "no longer supported by the company or Microsoft," with ESO Fire RMS promoted as the upgrade path — and ESO's NERIS FAQ confirms Emergency Reporting won't be upgraded for the new federal system either. Departments that came to ESO through those acquisitions have been moved, or pointed toward moving, twice. Wherever your data goes next, you get to pick the destination this time.
Ladue, Missouri published a useful split decision after making that move. In an October 2024 memo, Fire Chief Steve Lynn wrote that after ten months with ESO across department operations, "ESO platform is not the right software for the Ladue Fire Department." Ladue chose First Due for fire operations, but retained ESO for patient-care reporting because of its medical-control and quality-assurance program. The distinction matters: a department can value ESO's ePCR while deciding its fire RMS is not the right operational fit.
| Command Established | ESO Fire RMS | |
|---|---|---|
| Published pricing | $1,736/yr, all modules (pricing) | Not published — quoted per module (sample invoice) |
| Setup & migration fees | $0 — we do the work with you | $1,785 setup billed on the invoice above; data migration listed at $4,120, discounted to $0 for that customer |
| Users | Unlimited | Unlimited user licenses advertised |
| Price over time | Cancel anytime — remaining full months refunded (Terms) | Invoice references contractual "annual uplift" and usage increases; a 2026 payment record shows API access billed separately |
| NERIS incident reporting | Direct submission — NERIS V1 Data Exchange Compatible | V1 Data Exchange Compatible (per FSRI's partner list, July 2026) |
| EMS ePCR & hospital exchange | Not yet | A genuine ESO strength |
| Free trial | 30 days, no credit card | Demo and quote process |
Switching is on us
ESO's rate card put migrating Nevada, Missouri's own NFIRS data at $2,995 — discounted to $0 for that customer, that year. We don't price migration at all: you shouldn't have to pay, or negotiate away, a fee just to become someone's customer. Send us your exports; our team does the work with you.
Where ESO Is the Right Call
ESO's roots are in EMS, and integrated ePCR and hospital data exchange are genuine strengths. If your organization needs integrated patient care reporting, EMS billing, or hospital interoperability across a large system, ESO belongs on your shortlist — full ePCR isn't something we offer yet, and enterprise hospital interoperability isn't where we focus. For the fire RMS itself, get the quote and set it next to a number that's already public.
That strength shows up in a recent public deployment. In October 2025, the City of Dubuque reported that its ESO Health Data Exchange connection with UnityPoint Health returns hospital outcomes to EMS patient records. Fire Chief Amy Scheller said the integration gives paramedics "direct feedback on their work in real time." That's a closed-loop EMS and hospital workflow Command Established does not claim to replace.
Also looking at Emergency Reporting or Firehouse specifically? Those pages cover the transition details — and the rest of the field is a click away.
Frequently Asked Questions
How much does Command Established cost compared to ESO?
Our price is public: $1,736 a year for up to two stations, all modules, unlimited users (pricing). ESO doesn't publish pricing, but the City of Nevada, Missouri's published invoice shows a one-station department billed $6,311.66 across eight modules for a roughly fourteen-month term (about $5,410 per twelve months), plus a $1,785 one-time setup fee.
Can you migrate our data from ESO, Emergency Reporting, or Firehouse?
Yes, and it costs nothing. Incident history — including NFIRS exports — personnel, training, and inventory records come over through export files, AI-assisted bulk import, and our team's hands-on help.
Does Command Established support NERIS?
Yes. Incidents are structured for NERIS as you write them and submit directly from the platform. Command Established is NERIS V1 Data Exchange Compatible and listed on FSRI's integration partners page; the enrollment guide walks through connecting your department.
Are there per-module charges?
No. Every module is in the flat price. ESO's invoice above splits the same workflows into eight separately priced modules, several of them metered by station, vehicle, or record count — that's the per-module math a flat price removes. (Both products offer unlimited user logins.)
Is there a free trial?
30 days, the full product, no credit card. Start here or book a demo if you'd rather see it guided.
What happens if we decide to leave?
Your data is yours: module exports are self-serve, and our team assists with a complete export. If you cancel, we refund your remaining full unused months under our Terms. We'd rather earn the renewal than write a contract that traps you.
Command Established is an independent product and is not affiliated with, endorsed by, or sponsored by ESO Solutions, Inc. All trademarks are the property of their respective owners and are used here for identification and comparison only. Details about ESO come from the public sources linked on this page and were last reviewed in July 2026 — always confirm current pricing with the vendor. See something out of date? Let us know and we'll correct it.