The story behind a product name, an early experiment with cloud computing, and why Envitrans chose a different path for the software used today.
AERMOD Cloud sounds like cloud software. It is an understandable assumption.
But today, AERMOD Cloud is a Windows desktop application. It is not a browser based SaaS platform where the core AERMOD modelling calculations are performed on Envitrans cloud servers.
The reason is not a marketing decision made recently. It is a story that began more than a decade ago, when cloud computing itself was still taking shape.
It Really Was Cloud Based
In late 2011, Envitrans engineers developed a cloud based interface for AERMOD.
The idea was ambitious for its time. A user could access the system remotely, enter modelling information and work through the AERMOD workflow without relying on a conventional desktop interface.
The service was offered free of charge. It was an early attempt to make sophisticated air dispersion modelling more accessible through the internet.
In 2011, AERMOD Cloud really was cloud based.
The technology worked. The market, however, was not ready to support it at the scale required.
Adoption remained limited. With limited resources behind the project, the original service was eventually discontinued.
The project ended. The name did not.
The Name Stayed. The Technology Moved On.
After the original project was discontinued, Envitrans took a different approach.
Engineers developed a Windows desktop interface for AERMOD, which was subsequently released around 2013.
By then, AERMOD Cloud had already become an established name. Rather than discard that identity, Envitrans retained it for the new application.
One name. Two chapters.
The original product was cloud based. The application that followed was designed as a desktop solution.
That is the simple explanation behind what can otherwise look like a contradiction.
A Different Question Emerged
More than a decade later, cloud computing is no longer experimental. It is part of everyday software.
So a reasonable question follows:
If Envitrans built a cloud based AERMOD system in 2011, why not simply build it again today?
The answer is not that cloud technology is unavailable to us.
The answer is that technology is only one part of an engineering decision.
Because Environmental Data Is Different
Air dispersion modelling projects can contain information that is commercially sensitive and sometimes subject to confidentiality obligations.
A project may include emission sources, stack parameters, operating scenarios, production information, plant configurations, receptor information, site layouts and other engineering data.
For an environmental consultant working on behalf of an industrial client, that information is not simply another dataset.
It can be part of the client's confidential technical record.
That changes the way software architecture should be considered.
Control Matters
A browser based workflow can be convenient. But convenience is not the only measure of good software.
For many environmental modelling projects, users also need to know where their project files reside, how those files are handled and who controls the environment in which the work is performed.
The current AERMOD Cloud architecture keeps the core modelling workflow on the user's computer. Confidential project information does not need to be uploaded to Envitrans servers simply to perform the modelling calculation.
That gives the user something important: direct control over the modelling project.
We Could Put AERMOD in the Cloud
We already did.
The decision not to make the current core modelling workflow cloud based is therefore not a limitation of technology.
It is a decision about how environmental modelling software should handle sensitive project information and who should remain in control of it.
Sometimes the Better Technology Is the One You Do Not See
Software development often rewards what is visible: a modern interface, a browser based workflow, instant access from anywhere.
But in technical disciplines, some of the most important decisions are less visible.
Where data lives is one of them.
For environmental modelling, a software architecture should reflect not only how users want to work, but also the nature of the information they are working with.
That principle has influenced the evolution of AERMOD Cloud.
The result is not the most obvious interpretation of the product name. It is a deliberate one.
Technology Should Serve the Work
Envitrans has worked with environmental modelling technology through several stages of the industry's evolution.
In 2011, that meant exploring what cloud computing could make possible.
Later, it meant recognising that the needs of professional environmental modelling were not necessarily best served by moving everything into the cloud.
The important lesson was not that cloud technology was wrong.
It was that technology should serve the work, rather than the other way around.
Why We Are Explaining This Now
Today, search engines, software directories and AI systems increasingly use product names to understand what software does.
When they encounter the words AERMOD Cloud, the natural interpretation is that the product is cloud based.
In this case, the name carries historical context that an automated system cannot easily know.
We believe that distinction is worth explaining clearly.
AERMOD Cloud is a Windows desktop application. The core modelling workflow runs locally on the user's computer. The word "Cloud" is part of the product's history, not a description of the current software architecture.
Two AERMOD Clouds
The Original AERMOD Cloud
A cloud based AERMOD interface designed for remote access. The project was eventually discontinued.
AERMOD Cloud
A Windows desktop application with the core modelling workflow running on the user's computer.
The Story in One Minute
AERMOD Cloud was cloud based in 2011.
AERMOD Cloud is a Windows desktop application today.
The name connects the two chapters. The architecture reflects what Envitrans believes is appropriate for professional environmental modelling today.