The word “Open” in OpenFire refers to much more than the fact that the software is publicly available. It describes the way the platform has been built, the way engineering methods are implemented, and the way users can interact with the underlying technology.

An open-source library of methods

At the centre of the OpenFire ecosystem is an open-source library containing fire engineering methods drawn from recognised guidance, standards, technical references, and published research. Rather than treating calculations as hidden functionality inside a proprietary application, OpenFire implements methods as transparent and inspectable building blocks. Engineers can see how calculations have been coded, understand how results are obtained, and review the assumptions and limitations associated with individual methods.

The calculation engine itself is written in Rust, a modern programming language chosen for its performance, reliability, and safety. Every implemented method is available through the public source code repository, allowing engineers, researchers, reviewers, and developers to inspect the implementation directly. This means that the software can be reviewed in exactly the same way as any other technical resource used within engineering practice.

The source code repository contains much more than the equations themselves. It also includes documentation, examples, testing infrastructure, and supporting material that explains how methods have been implemented and verified. Users are therefore able to move beyond simply obtaining a result and instead understand how that result has been produced.

More than one way to work

OpenFire is not limited to a single way of working. While many users access methods through browser-based interfaces, the same calculation engine is also available through a Python API distributed through PyPI. This allows engineers to integrate OpenFire directly into their own workflows, automate repetitive tasks, develop internal tools, or combine OpenFire calculations with other software used within their organisations.

This flexibility is an important part of the platform. Different engineers work in different ways. Some prefer graphical interfaces, others rely heavily on spreadsheets, and many organisations have developed their own internal systems over time. By making the calculation engine available through multiple interfaces, OpenFire allows users to adopt whichever workflow best supports their needs while maintaining consistency in the underlying methods.

Open documentation

The documentation is also openly available and forms an important part of the ecosystem. Alongside the implemented methods, users can access definitions, worked examples, technical explanations, assumptions, limitations, and supporting guidance. The intention is not simply to provide calculations, but to provide the context necessary to understand when methods are applicable and how they should be used.

Built for better-informed decisions

Ultimately, OpenFire is designed to make fire engineering knowledge easier to access, understand, and apply. Whether you are looking for a specific calculation method, exploring alternative approaches, reviewing assumptions, or integrating fire engineering calculations into your own workflows, the underlying goal remains the same: to support competent engineers in making better-informed decisions.

The easiest way to experience OpenFire is through the integrated web application, which combines the underlying library, documentation, examples, and AI-assisted knowledge support into a single environment. By bringing together recognised guidance, engineering methods, research, and technical explanations, OpenFire provides a practical way to navigate the growing body of fire engineering knowledge while keeping transparency, professional judgement, and engineering competence at the centre of the process.