About xfea
xfea is a language for finite element models and results that your AI assistant writes, checks and runs on your solver, on your machine. You describe a structure; your assistant builds the model in xfea, shows it to you, solves it and reads the results back, with evidence an engineer can defend. The Python it writes is yours to read, change and run again.
AI assistants can already write scripts for finite element software. What they lack is a way to see what they built: whether the supports are where they should be, whether the joint is joined, whether the result is plausible. A model written in a solver’s own input language is hard to check, for a person and for an AI alike.
xfea gives both of you one readable description of the model, whatever the solver, and makes it observable at every stage: a picture before the solve, the checks a solver would skip, the solve as it runs, the results in one form, and a one-page report. See Checking a model.
Principles
Section titled “Principles”- Your solver, on your machine. xfea doesn’t run solvers. The mesh and the results never leave your machine; only the model’s definition goes to xfea’s service, to be turned into your solver’s input.
- Your AI. xfea doesn’t host an assistant. It gives yours tools, through an MCP server on your machine, and the assistant does the reasoning.
- Open where you work. The library, the MCP server, meshing, the results database and the viewer are open (Elastic License 2.0): read them, change them, build on them. The conversion to each solver is xfea’s own, run as a service. See What’s free, what needs an account. These docs’ text and pictures are under CC BY 4.0: quote and reuse them, with credit.
- Checked in public. Every release solves a set of reference cases and publishes how each compares with its known answer, failures included: Verification.
Where it stands
Section titled “Where it stands”xfea is at 0.1, in early access. Models of beams, shells and solids, with supports, releases, springs, ties and contact, in static, nonlinear, modal, buckling and heat transfer steps, solve end to end. Through the service, some things are not supported yet: connectors, rigid parts, constraints other than rigid couplings, and interfaces other than contact and ties between parts. Before 1.0 the API can still change between minor versions: see API stability.
Who makes it
Section titled “Who makes it”xfea is made by Francesco Ranaudo: francescoranaudo.com.
xfea grew out of compas_fea2, developed at the Block Research Group, ETH Zurich.
Get in touch
Section titled “Get in touch”- Questions, early access, on-premises use, a plugin for another solver: the contact form. Tick its box to get the newsletter too.
- Bugs and requests: GitHub issues.
- The code: github.com/fea-x/xfea.
- News: xfea.ai.
© 2026 Francesco Ranaudo · Text and pictures CC BY 4.0 · Code Elastic License 2.0 · how to reuse them