Read next:
- entry point:
README.md - solver roadmap:
SOLVER_ROADMAP.md - product execution:
PRODUCT_ROADMAP.md
Dedaliano is an open-source structural solver and an emerging structural engineering platform.
Today the strongest identity is:
- browser-native structural modeling and analysis
- open-source solver development
- broad structural mechanics coverage
- unusually deep benchmark and validation culture
The cleanest short description is:
Dedaliano is an open-source structural analysis and structural mechanics platform for structural engineering.
The stronger current claim is:
Dedaliano is becoming one of the strongest open structural solvers, with a broader product surface than most solver-first projects.
That claim is now supported by more than raw category count:
- latest reported full-suite status of
5896passing tests and0failures - explicit benchmark-gate suites for constraints, contact, shells, reduction, sparse / conditioning paths, and sparse 3D parity
- solver-core work that now includes constraints, shells, contact, SSI, fiber nonlinear analysis, imperfections, creep / shrinkage, and reduction
- an explicit multi-family shell story (
MITC4,MITC9,SHB8-ANS, and curved shells) with research-driven selection guidance instead of opaque defaults
Dedaliano is not:
- a general-purpose multiphysics platform like Abaqus, ANSYS, or Code_Aster at large
- a generic CAD/BIM replacement
- a full construction-documentation system
- a general CFD, thermal-fluid, or manufacturing simulation stack
The scope should stay structural first.
The current product surface is already broad enough to support a real company narrative:
- browser-native structural modeling and visualization
- a substantial Rust structural solver
- meaningful structural design-check and postprocess modules
- a large public benchmark and validation program
The detailed source of truth for what exists is:
engine/README.mdfor engine surfaceBENCHMARKS.mdfor capability, validation, and remaining gaps
The strongest current differentiators are:
Open sourceThe solver and validation story are inspectable and auditable.Browser-native deliveryNo desktop installation, licensing friction, or heavyweight deployment model.Validation moatThe repo already has an unusually large public benchmark surface for this class of product.Platform leverageThe same solver can support the web app, APIs, future plugins, single-purpose tools, and design workflows.
The next differentiators are less about adding whole new solver categories and more about:
- robustness on difficult real models
- performance at scale
- benchmark credibility on the newest solver families
- shell and nonlinear workflow maturity
- consistent solver-path behavior across constrained and unconstrained workflows
- benchmark-gated release discipline on the newest solver families
- scale-oriented workflow maturity such as reduction/substructuring and large-model solve discipline
- productizing the full solver surface cleanly across app, API, and downstream tools
If the goal is to become the best open structural solver by far, the winning path is now clear:
- dominate runtime and scale on real structural models
- build the deepest visible proof moat in the category
- make solver behavior deterministic and explainable
- harden the ugly mixed nonlinear workflows competitors still win on
- turn the multi-family shell stack into a coherent default workflow instead of a hidden expert feature
That credibility should be built visibly. The strongest long-term trust program is not one technique in isolation, but a stack:
- public benchmark and cross-validation coverage
- invariant and property-based testing
- fuzzing for edge cases and regression discovery
- selective proof-oriented rigor on small critical kernels
This document is about market framing, not the full solver inventory.
Use BENCHMARKS.md for capability/proof and SOLVER_ROADMAP.md for execution order.
Trying to be “the best solver overall” across all simulation categories is too broad.
The strongest winnable positions are:
- best open-source structural solver
- best browser-native structural solver
- best validated structural solver for everyday structural engineering
- best structural solver for building-frame and common office workflows
Near term, the most credible path is:
elite structural solver first, broader structural platform second
Those are credible paths. “Best solver in all engineering physics” is not the right target.
The solver can support several product layers:
- structural analysis application
- structural analysis API
- code-check and design modules
- connection and foundation tools
- report and calculation automation
- BIM / CAD integrations
- optimization and AI-assisted engineering tools
- education and benchmark-explorer products
The right expansion path is:
best structural solver -> best structural engineering platform
not:
best structural solver -> generic simulation company
The best expansion order from the current base is:
- structural solver trust and solver-quality leadership
- code checks / design modules
- reports and documentation
- connections
- foundations
- interoperability and BIM-connected workflows
- optimization / AI-assisted workflows
- collaboration / firm workflow tooling
This order follows how structural firms buy software:
can it analyze -> can it design -> can it produce deliverables -> can it fit our workflow
Good adjacent markets:
- building structural engineering
- bridge and staged-construction workflows
- prestress / PT workflows
- foundation and SSI-related workflows
- structural education
- engineering automation and report generation
- structural optimization and design review
- architect-friendly conceptual structural analysis as a later, guardrailed product layer
Bad adjacent markets for now:
- CFD
- broad thermal-fluid simulation
- manufacturing solids
- electromagnetics
- general multiphysics expansion
The solver is the core asset.
Business-wise, that means:
- every new structural product can reuse the same mechanics core
- benchmark credibility transfers across products
- design, reporting, and workflow products become higher-margin layers on top of solver trust
This is why solver quality should stay the center of the company narrative.
README.mdrepo identity and documentation mapengine/README.mdengine-facing overview and analysis surfaceBENCHMARKS.mdvalidation status, solver capability matrix, and benchmark ledgerSOLVER_ROADMAP.mdsolver mechanics, validation sequencing, and technical prioritiesPRODUCT_ROADMAP.mdapp, workflow, and market sequencing