platform

AI-first engineering simulation, grounded in evidence.

Anvil Sim is engineering simulation software for FEA, CFD, thermal, electronics, and geometry workflows. The product loop is simple: research, setup, solver run, benchmark comparison, visual replay, reviewer packet, and the next validation step.

AI workflow

in build

AI helps set up cases, read references, critique assumptions, generate tests, and diagnose solver behavior. Benchmarks carry the physics claims.

Geometry and meshing

under validation

Source geometry, units, source-face binding, mesh quality, and remesh stability move through explicit intake gates.

Solver kernels

reference-backed

Structural FEA, modal, thermal, FRF, electronics, and CFD work progresses through narrow kernels, analytic checks, reference solvers, and public benchmark rungs.

Electronics and AI chip thermal

preview

Heat-sink, enclosure airflow, and future AI chip package cases attach power maps, material assumptions, temperature QoIs, and reference data as the evidence grows.

Benchmark trust wall

growing

Each public claim should have a benchmark row with reference source, QoI, tolerance where available, status, and next step.

Native evidence console

in build

The Mac app is the review surface: visual replay, solver fields, benchmark deltas, provenance, evidence packets, and validation steps.

Reviewer packets

evidence-ready

A reviewer packet binds the claim, input assumptions, solver output, reference comparison, visual replay, current validation focus, and next evidence step.

product roadmap

The roadmap is tied to evidence.

Each line shows how today's public evidence grows into broader product capability.

HorizonFocusEvidence todayValidation focus
CurrentOrganized public proof surfaceBoomerang flight-path replay, benchmark wall, investor route, whitepaper, and domain-grouped demos.Keep every demo connected to a status row and validation note as public language expands.
NextBenchmark closure depthFRF, static FEA, NAFEMS core rows, flame reference calibration, CFD targets, and geometry/mesh validation focus rows.Target and roadmap rows move through executable closure before they become stronger proof claims.
ThenNative review workflowEvidence packets and visual replay move into a repeatable Mac review workflow for demos, benchmarks, and customer-style packets.The native UI must keep visual readiness separate from solver and benchmark readiness.
benchmark preview

The platform earns trust row by row.

The full wall keeps every row explicit: reference source, QoI, status, latest evidence, validation focus, and next benchmark step.

Boomerang flight path

Boomerang return-window gate

SCENARIO EVIDENCE

QoI: Trajectory enters the 0.50 m return window while airborne before first ground contact.

next: Attach measured-flight or public aerodynamic reference data before expanding the flight-validation claim.

Structural dynamics

FRF cantilever harmonic response

REFERENCE PASS

QoI: Peak 8,150 Hz vs CalculiX 8,178.154 Hz; 0.3443% peak-frequency delta and 0.0233 normalized curve RMS.

next: Add another geometry and a physical/reference sweep before expanding customer-style FRF readiness.

Static FEA

Static cantilever Hex8-EAS stress

REFERENCE PASS

QoI: Stress error 1.4588e-2 at 20x4x2 and 5.1531e-3 at 40x8x4.

next: Extend to source-bound geometry, mesh-convergence receipts, and an external solver comparison.

NAFEMS structural

NAFEMS linear-elastic core rows

REFERENCE ROWS

QoI: Selected LE rows are within declared tolerances; additional families remain in validation.

next: Separate each passing LE row from mixed modal/shell families and keep tolerances visible per case.

Public proof rules

Ambition stays connected to evidence.

Visuals should lead to solver results, benchmark rows, and reviewer packets.
A reference pass must name the reference and QoI behind the status.
Rows name the next evidence step before stronger public language appears.
Public pages stay focused on customer-facing routes, artifacts, and product structure.