System Requirements
deFlex runs entirely in the browser. The solver runs server-side, so your local hardware requirements are modest. The main demand on your machine is rendering the 3D viewport.
Browser requirements
deFlex requires a modern browser with WebGL 2.0 support:
| Browser | Minimum Version | Status |
|---|---|---|
| Google Chrome | 80+ | Fully supported |
| Mozilla Firefox | 78+ | Fully supported |
| Microsoft Edge | 80+ (Chromium-based) | Fully supported |
| Safari | 15+ | Experimental — WebGL 2 support varies |
Safari's WebGL 2 implementation has known inconsistencies on some macOS versions. If you experience rendering issues, switch to Chrome or Firefox.
JavaScript must be enabled. deFlex relies heavily on WebGL shaders and Web Workers for viewport rendering and background data processing. Browser extensions that block scripts or modify page content (aggressive ad blockers, privacy extensions) may interfere with the application.
Hardware recommendations
| Component | Minimum | Recommended |
|---|---|---|
| GPU | Integrated graphics (Intel UHD 620+) | Discrete GPU (any modern NVIDIA, AMD, or Apple Silicon) |
| RAM | 4 GB | 8 GB or more |
| Display | 1280 x 720 | 1920 x 1080 or higher |
| Input | Trackpad or mouse | Mouse with scroll wheel (strongly recommended for 3D navigation) |
The 3D viewport uses hardware-accelerated rendering. Integrated GPUs handle typical design domains (plates up to ~200x200 elements) without issue. For larger meshes or when viewing fine-grained design results during solver iterations, a discrete GPU provides smoother interaction.
A mouse with a scroll wheel makes viewport navigation significantly more comfortable than a trackpad — orbiting, panning, and zooming all map to mouse buttons and the scroll wheel.
If the viewport feels sluggish, check that your browser is using hardware acceleration. In Chrome, navigate to chrome://gpu and confirm that WebGL is listed as "Hardware accelerated."
Internet connection
deFlex requires an active internet connection at all times. The application loads from a web server, and the solver runs on backend infrastructure — your browser sends the problem definition to the server and receives results back as the solver iterates.
| Activity | Bandwidth | Latency sensitivity |
|---|---|---|
| Loading the application | ~5 MB initial load | Low |
| Solver submission | < 100 KB (problem definition) | Low |
| Streaming solver results | ~10-50 KB per iteration | Moderate |
| File import (STEP) | Depends on file size | Low |
A stable broadband connection (5+ Mbps) is sufficient for all workflows. The solver streams partial results after each iteration, so higher latency connections may experience slight delays in the live design result updates, but this does not affect solver accuracy or final results.
Because the solver runs server-side, you do not need a powerful local CPU for optimization. Even a Chromebook or tablet with a modern browser can run deFlex — the heavy computation happens on the server.