FINITE ELEMENT ANALYSIS · DRIVEN BY YOUR AI ASSISTANT · ON YOUR MACHINE

Build, run and check finite element models by talking to your AI.

feaX connects the AI assistant you already use to the finite element solver you already own. Describe the problem or hand over an existing model; feaX builds it, writes it for your solver, reads the results back, and checks them against an independent second solve. Nothing leaves your machine.

Request early accessSee a sample reporthow it works ↓
your assistant · feax (local)127.0.0.1
› Check endplate_M20 against a second solver. The frame assumes this joint is rigid.
00.0s import_model→ 31 keywords read, 1 skipped
00.4s validate→ 2 warnings
00.5s write(second solver) → endplate_M20_b
00.6s run(your solver) · run(second solver)
02:31 read_results×2 → displacements, reactions, stresses, bolt forces
02:33 compare→ 4 of 5 quantities within 5%
02:41 check→ 2 findings
Sum of reactions 96.0 kN vs 160.3 kN · +40%
Support set holds 4 of 16 base nodes (line 212). Support incomplete.
Joint classifies as semi-rigid; the frame assumes rigid.
both input files saved locally · figures illustrative
01 / WHAT FEAX IS

A pre- and post-processor built for an AI to drive, not a person to click.

Finite element work has always had three parts: building the model, solving it, and making sense of the results. The solver is mature software you already own and trust. The other two parts are where engineers spend their days, and where the errors live.

feaX takes those two parts and makes them something an AI assistant can do well. It holds one neutral, typed description of the model, validates it before anything is written, writes the input file your solver expects, reads your solver's results back, and compares them with a second, independent solve.

It does not solve anything itself. It does not send your models anywhere. It gives you back every input file it writes, so nothing depends on feaX to reproduce.

02 / HOW IT WORKS

A small local server between your assistant and your solver.

YOUR MACHINE OR YOUR FIRM'S SERVER · NOTHING LEAVES BY DEFAULT
YOU AND YOUR ASSISTANTThe conversationYou describe the problem, or point at a model you already have. The assistant plans the analysis and records every assumption it makes.
FEAXOne model, validated, written for any solverHolds the neutral model. Checks it before writing. Writes your solver's input file. Reads its results. Compares, checks, explains.
YOUR SOLVERYour licence, your hardwareThe solver you already trust does the solving. A bundled open-source solver provides the independent second opinion.
SENT TO USa licence check · crash reports if you opt in
NEVER SENTgeometry · models · input files · results
OPTIONALcloud compute if you have no solver · a hosted server if you want nothing installed
1 · BUILDFrom a description, a CAD file, or a model exported from another tool. Geometry, materials, supports, loads, mesh.
2 · RUNfeaX writes the input file, your solver runs it, feaX reads the results back. Optionally the same model on a second solver.
3 · CHECKUnits, equilibrium, supports, node sets, mesh convergence, agreement between solvers and with a hand calculation.
4 · UNDERSTANDAsk questions of the results, view them in 3D, compare designs, export a report with every assumption and both input files.
03 / WHY

Hours back, a second opinion on every run, and your data where it is.

TIMESetup and interpretation in minutesThe parts of FE work that take hours of clicking happen in conversation. The solve takes as long as it always did; everything around it gets short.
TRUSTAn independent second opinionThe same model solved on a second solver, compared, and the modelling itself checked for the errors that matter: supports, units, node sets, mesh. Findings in plain words, pointing at the line.
CONTROLYour solver, your machine, your filesResults come from the solver you already validated and licensed. Nothing is uploaded. Every input file is handed back, so you can rerun anything without feaX.
PORTABILITYOne model, any solverMove a model between solvers with a report of what did and did not translate. Switch solvers, or keep several, without rebuilding.

What feaX does not do: it does not replace the engineer's judgement or signature. A second solver agreeing with the first means the model was solved as written, not that it was the right model. feaX makes the evidence for that judgement fast and complete.

04 / A CHECK IN PRACTICE

One planted error, found in under three minutes.

A bolted end-plate connection, modelled in a commercial solver, with one node set left incomplete on purpose. The original solver runs it without complaint. feaX rebuilds the model, solves it a second time, and the reactions disagree by 40%. The report points at line 212.

read the full sample report →FIGURES ILLUSTRATIVE UNTIL THE BENCHMARK SET IS PUBLISHED
END PLATE · MESH, 2ND REFINEMENT · BOLT HOLES M20support set: 4 of 16 base nodes
quantityyour solversecond solverΔmax displacement, mm4.214.29+1.8%sum of reactions, kN96.0160.3+40%max bolt force, kN118.2121.7+3.0%joint stiffness, kNm/rad41 20040 100-2.7%
!Support set holds 4 of the 16 nodes on the base face (line 212). Applied load 160.0 kN; the original model's reactions sum to 96.0 kN. Suggested fix: regenerate the set from the face.
05 / USING IT

Install once, connect your assistant, keep working the way you already do.

STEP 1InstallOne command on macOS, Linux or Windows. feaX finds the solvers already on your machine and brings its own open-source one for second opinions.$ [install command]
STEP 2Connect your assistantfeaX speaks the open protocol AI assistants use for tools. One line adds it to the assistant you already have, or to your firm's own agent.$ feax connect [assistant]
STEP 3AskDescribe a problem, drop in a model, or ask for a check on one you inherited. Results, findings and both input files land in a folder you choose.› check this model against a second solver
FOR ANALYSTSBuild and check models in conversation, on the solver you own. Hours back every week.
FOR CHECKING ENGINEERSRebuild any incoming model, re-solve it independently, see what disagrees and why. You still sign.
FOR FIRMSData stays on your machines. Seats, not core-hours. One tool across every solver you run.
06 / STATUS

Seven years of core library. The product on top of it is being built now, in the open about what works.

2019FIRST COMMIT OF THE CORE
4SOLVERS SUPPORTED TODAY
0MODELS THAT LEAVE YOUR MACHINE
419TESTS PASSING · 2026-11
DONECore library and solver adaptersOne codebase, one test run, four solvers written for and read from.
NOWDesign partnersEarly builds on real models with a small number of firms.
NEXTModel built for the assistantA validated neutral model and the tools around it, instead of scripts.
NEXTThe second opinionImport from any supported solver, translation report, comparison, modelling checks.
GATEAccuracy publishedEvery benchmark case we run, per solver, misses included. Then the install goes public.

WE PUBLISH WHAT WE MISS. ONE BENCHMARK, A CONTACT TEST, IS CURRENTLY OPEN ON OUR LIST AND STAYS THERE UNTIL IT IS FIXED.

07 / ACCESS
DESIGN PARTNERS

Run early builds on real models.

  • Early builds, direct line to the founder
  • Your models never leave your machines
  • Fixed seat price for two years after launch
  • In return: real models, a monthly call, a quote when it earns one
Request early access
FOLLOW THE BUILD

Every release, every benchmark, every miss.

We publish the benchmark set and its results with each release, including the cases we miss, and write up what we learn. A short note when something ships, nothing else.

Get release notes
Francesco Ranaudo, founder · [FOUNDER BIO] · contact