# femforge > Typed finite-element orchestration in Python: a tagged STEP file in, typed results out, with gmsh and Elmer as the first backends. femforge drives finite-element analysis from Python. One typed SimulationConfig takes a tagged STEP file through meshing and a solve to a typed, provenance-tracked Result; gmsh and Elmer are the backends implemented today. ## Overview - [femforge]() - [Compatibility]() - [Concepts]() - [Install]() - [Quickstart]() ## User guide - [Artifacts and retention]() - [CLI]() - [Conditions and physics]() - [Driver and runs]() - [Elmer: native and Docker]() - [Frames]() - [Geometry and tags]() - [User guide]() - [Materials]() - [Mesh]() - [Optimization]() - [Results]() - [Telemetry]() - [Workbench]() ## API reference - [Artifacts]() - [Common]() - [Config]() - [Elmer solvers]() - [Elmer]() - [Docker images]() - [Geometry]() - [API reference]() - [Materials]() - [Meshing]() - [Optimize]() - [Physical]() - [Run]() - [JSON schemas]() - [Telemetry]() - [Validation]() - [Viz]() - [Dock]() - [Panels]() - [Registry]() - [Serve]() - [Theme]() - [Widgets]() ## Contributing - [Artifacts and retention]() - [Config objects]() - [Solver objects]() - [Telemetry]() - [Workbench client]() - [Setup]() - [Invariants]() - [Principles]() - [Release process]() - [Testing and gates]() - [Tooling]()