Mesh-aware sizing
Model topology, cell count and mesh partitioning can drive compute sizing instead of forcing every simulation onto the same machine.
Fire Dynamics Simulator · Cloud Compute
Run serious fire simulations without owning the server room.
A cloud workspace designed for FDS engineers: transparent compute, dedicated resources, live solver telemetry and project-ready results.
PROGRESS64%T = 576 / 900 s
CELLS4.8M12 meshes
HRR NOW2.31 MWdesign 2.5 MW
ETA28 minillustrative
Dedicated compute per jobEU cloud architectureUsage-based designFDS / MPI ready
01 // Platform
Compute infrastructure shaped around the way FDS actually works.
Parallel by design
Architecture prepared for MPI workloads, with isolated compute resources and predictable performance for engineering jobs.
See what the solver sees
Progress, logs, HRR and device readings presented while the run is active—not only after the calculation ends.
02 // Workflow
From model to results in four clear stages.
STEP 01
Analyse
Inspect the FDS model and derive the information required for compute sizing.
STEP 02
Confirm
Review the proposed run configuration before any cloud computation starts.
STEP 03
Compute
Launch the solver on dedicated cloud resources and follow telemetry live.
STEP 04
Review
Collect solver outputs, engineering data and files required for further analysis.
03 // Outputs
The files engineers expect. The visibility project teams need.
Smokeview-ready outputs
Keep the native FDS workflow intact, including simulation data intended for Smokeview post-processing.
Device data
Temperature, visibility, velocity and other DEVC time series ready for engineering assessment and charting.
Solver history
Preserve run logs and computational context so results remain traceable during checking and reporting.
Project workspace
A future home for scenarios, revisions and comparison runs instead of scattering output folders across local machines.
04 // FAQ
Built for FDS workflows.
Can I upload and run an .fds file now?
Not yet. This first release is the landing-page prototype only. Upload, estimation and compute functions are intentionally disabled.
Will it replace FDS or Smokeview?
No. The concept is cloud infrastructure around the established FDS workflow, not a replacement solver.
Will simulations be able to run in parallel?
The planned architecture supports independent cloud jobs, making concurrent scenario runs possible once the compute backend is implemented.
Is pricing available?
Not in this prototype. A later estimator can calculate an indicative configuration and cost before a job is launched.