FDS fire simulations
computed in the cloud

Upload a .fds file — you will see an estimated cost within seconds, before you commit to running anything. The simulation runs in the cloud and you only pay for the compute time it actually takes.

HRR // STAIRWELL_AILLUSTRATIVE PREVIEW
3000
2000
1000
0
HRR_MAX // 2,480 kWT_CEILING 138 °CNOW
0 s225 s450 s675 s900 s
A dedicated VM per jobServers in the European UnionUsage-based billingResults for 60 days

Computing without a server room of your own. Anatomy of a single job.

FIG 0.1 / MODEL PARTITIONING
MESH_01MESH_02Z = 0,0034.22 // 11.08

Meshes from the .fds file

We read the &MESH sections and count the cells in each one — that is the basis for both the estimate and the machine sizing.

FIG 0.2 / CORE ALLOCATION
CLOUD_VMRANK_0RANK_1MPI // 15 RANK

One mesh per core

Meshes go to separate MPI processes on a dedicated server. No queue, no resource sharing.

FIG 0.3 / FIRE DEVELOPMENT
tQ2 480 kWT_ROZWOJUα·t² // 900 s

HRR curve and simulated time

The &TIME and &REAC sections give the simulated duration, and the CFL condition gives the real compute time.

Quote

From a .fds file to a concrete figure

The analysis happens locally in your browser. The file only reaches our server once you accept the quote.

  • 01

    The &MESH, &TIME and &REAC sections plus model elements (&OBST, &VENT, &DEVC) are read without uploading the file.

  • 02

    Runtime estimated from the CFL condition and a throughput of ~240,000 cell-timesteps/s per core.

  • 03

    You see the cost before the start — no subscription, no account.

FILEklatka_schodowa_A.fds
CELLS3 240 000
MESH_07 // 412 kCFL // krok 0,006 s
LOCAL ANALYSIS // FILE NEVER LEAVES THE BROWSER
ESTIMATE FROM THE CFL CONDITION
ESTIMATED COSTPLN 87
JOB TIMELINE // 0xAF15 MESHES // T_END 900 s
DONEFORECAST
START // MESH_01…08DEVC // TC_STAIRWELL_3MRESULTS QUEUE
0 s300 s600 s900 s
TELEMETRYEVERY 5 s
CORES15
STEP ms0,84
REMAINING1:47
HRR // LIVE
MESH ALLOCATION
MESH_AMESH_BPENDING
YOUR JOBS
3 / 3
KLATKA_SCHODOWA_A
RUNNING // 67%
OPEN
GARAZ_P1_ODDYM
COMPLETED // 60 DAYS
RESULTS
HALA_MAGAZYNOWA
COMPLETED // 60 DAYS
RESULTS
Progress

Follow the run live

The log refreshes every few seconds and the DEVC and HRR charts grow as the solver works. You do not have to wait for the end to see whether the model is heading the right way.

Run your first simulation
STATUS: ACTIVE

Quote

Cells and the estimated cost are worked out locally in your browser.

NO ACCOUNT // NO UPLOAD
STEP 02

Confirmation

You accept the amount, and only then does the file go to the server.

STRIPE // BLIK // P24
STEP 03

Computation

A dedicated machine runs the solver while you watch progress live.

DEDICATED MACHINE // EU
STEP 04

Results

SMV files, slice planes, DEVC CSVs and the full solver log.

AVAILABLE FOR 60 DAYS

Every job gets its own virtual machine — no queue and no sharing compute with anyone else.

A dedicated VM per job
Servers in the European Union

You pay for actual compute time and result storage. No subscription, no standing fees.

Usage-based billing
VAT invoice in your account

What you get

Smokeview visualisation

.smv files together with slice planes and boundaries — the full picture of how the fire and smoke developed.

Device data (DEVC)

CSV files with temperature, visibility and velocity readings — ready for assessing evacuation conditions.

Full FDS solver log

The complete run with solver parameters — for verification and project documentation.

Secure access for 60 days

You download results over a signed link; after 60 days they are removed from the server automatically.

Frequently asked questions

Which files are supported?

FDS input files with the .fds extension. We read the &MESH, &TIME and &REAC sections plus model elements (&OBST, &VENT, &DEVC) directly in your browser.

What does it cost and when do I pay?

You pay for actual compute time and result storage — no subscription, no standing fees. You see the estimated cost before the run starts, and payment (Stripe, BLIK, Przelewy24) happens after the computation finishes. A VAT invoice is available in your account.

How long does a run take?

It depends on the cell count and the simulated duration. We show a runtime estimate with the quote, based on the CFL condition and a throughput of ~240,000 cell-timesteps/s per core. Every job gets its own dedicated compute server.

Can I run several simulations at once?

Yes. Each job starts a separate virtual machine — there is no queue and no resource sharing between your simulations.

Is my file safe?

The file is analysed locally in your browser and uploaded only after you accept the quote. The computation runs on servers in the European Union, and the machine is destroyed once the job finishes.

Price the run.
Start the simulation.