Skip to content

vision

Ember: Outdoor Fire Detection for Mission Sites

Fire and early-smoke detection tuned for outdoor fuel, logistics, and perimeter monitoring — now shipping with live demos and an active builder challenge.

Innomium Vision Team
Cover for Ember: Outdoor Fire Detection for Mission Sites

Outdoor fire detection fails when models are trained only on controlled indoor flames. Ember targets the scenes operators actually worry about: forecourts, loading bays, storage yards, and perimeter lines.

Performance snapshot

  • 90% accuracy on outdoor fire and smoke validation splits under Innomium protocols
  • 19MB ONNX for edge deployment
  • Browser demo for rapid evaluation by safety teams

These metrics are protocol-specific. Sun glare, welding, dust, rain, and vehicle lights can all resemble a target event. A useful evaluation set includes those hard negatives alongside positive classes.

Designing an alerting workflow

A detection is not an incident. Safety teams need a path from signal to review: what triggers an alert, who receives it, which camera context is included, and when the event is closed. We recommend evaluating Ember with the actual operating protocol, including expected false alarms, escalation requirements, and the conditions in which human confirmation remains mandatory.

Outdoor scenes deserve particular care. A clearer threshold policy comes from calibrating against hard negatives from the real site, not only clean flame examples.

Challenge mechanism

Arena challenges can expand labeled outdoor data and pressure-test recall on difficult negatives. Challenge submissions are builder contributions under challenge rules — not client endorsements. Confirm current rounds and licenses on Arena and the model card before planning commercial use.

Related: [edge vision evaluation protocol](/updates/edge-vision-evaluation-protocol).

Want production AI shipped with the same discipline?

Talk with Innomium about vision models, long-context systems, or a focused engineering program.

Built for accountable delivery

Clear scope. Technical evidence. A team that can ship.

We begin with the operating constraint, agree on what success looks like, and build a delivery path your technical and business teams can review.

01

Defined outcomes

Scope, constraints, milestones, and decision owners before build work starts.

02

Evidence at every stage

Evaluation plans, working artifacts, and reviewable technical decisions—not presentation-only progress.

03

Production handover

Integration, observability, documentation, and an operating path for the teams who own the result.