Nature
What this product is
Aerospace-specific simulation preprocessor and meshing software for 2D and 3D — built to prepare airfoil and aircraft geometry for aerospace CFD and structural workflows, not a generic multiphysics toolbox.
This product is not yet live
HENMESH is announced on the HENDOI roadmap. You cannot open, buy or run it today. Live products: HENFOIL · HENSYNTH
Launch in process · not live yet
HENMESH
Aerospace simulation preprocessor / meshing · 2D & 3D
Prepare aerospace geometry for CFD and structure — with mesh honesty first.
Aerospace-specific simulation preprocessor and meshing software for 2D and 3D — built to prepare airfoil and aircraft geometry for aerospace CFD and structural workflows, not a generic multiphysics toolbox.
Illustration · not a live UI
Problem
What it is meant to solve
Teams often stitch general mesh tools into aircraft and airfoil pipelines: wrong defaults, weak aerospace naming, late quality failures, and no clean hand-off into a labelled analysis trail.
HENMESH aims to turn airfoil and aircraft geometry into analysis-ready meshes with aerospace intent — surface and volume controls, quality checks and export paths meant for HENFLOW and HENSTRUCT. Not live yet; launch in process. Live today: HENFOIL and HENSYNTH.
Problems in the field
Why aerospace teams need a dedicated product
Generic defaults, aerospace pain
General meshers start from multiphysics habits. Chord, LE clustering, far-field sizing and unit conventions arrive as afterthoughts — every project rebuilds the same aerospace setup by hand.
Naming that does not travel
Surface and volume packs leave the mesher without airfoil or aircraft language. The CFD or FEA case then invents its own labels, and the review trail breaks between tools.
Quality failures show up too late
Skew, aspect ratio and wall-layer problems appear after the solver has already burned hours. Catching mesh honesty earlier is cheaper than debugging a failed field.
No clean hand-off into the stack
Meshes become orphan files — disconnected from HENFOIL sections, HENSYNTH concepts and the method IDs engineers need when they defend a case.
Planned intent
What we intend to ship — when it goes live
These are roadmap intents, not live features. Nothing below is available to run today.
2D section & airfoil meshes
Domains suited to section and airfoil screens — resolution near the leading edge, wake and far field sized for aerospace CFD habits, not a blank CAD export.
3D wing & configuration packs
Surface and volume controls for wings, bodies and early configurations intended to feed HENFLOW and HENSTRUCT without renaming every patch by hand.
Quality gates before the solver
Mesh honesty checks with clear pass / warning / fail language so a bad pack does not silently enter a CFD or structural run.
Aerospace-labelled exports
Export paths and naming meant for the HENDOI stack — so a mesh pack carries intent into the next product instead of a nameless dump.
01 · Depth
What HENMESH is for
HENMESH is planned as the mesh and preprocessor layer in the HENDOI aerospace stack. After you decide a section in HENFOIL or a concept in HENSYNTH, simulation needs a mesh that respects chord, span, leading-edge resolution and domain conventions engineers already use. HENMESH is that preparation step — 2D for section and airfoil screens, 3D for wings, bodies and configurations.
02 · Depth
Nature of the product
It is a simulation preprocessor first: geometry in, analysis-ready mesh out, with aerospace vocabulary on surfaces, volumes and quality reports. It is not a general CAD kernel, not a CFD solver and not a certification mesh authority. The product exists to shorten the path from a defended geometry to a solver-ready domain that still carries method honesty.
03 · Depth
Problems it is meant to solve
General meshers force aerospace teams to rebuild the same setup every project. Naming does not match airfoil or aircraft language. Quality failures show up late in the CFD or structural run. HENMESH is intended to catch mesh honesty earlier, keep method labels on mesh packs, and shorten the path from a defended geometry to a solver-ready domain.
04 · Depth
How it fits the stack
Live today: HENFOIL (section) and HENSYNTH (aircraft conceptual). Next: HENMESH prepares the mesh; HENFLOW consumes it for aerospace CFD; HENSTRUCT for structural analysis & simulation. Until HENMESH launches, keep geometry and screening work in the live products — and share mesh industrial challenges so the first release fits real pipelines.
05 · Depth
What this page is not
HENMESH is not available to register, buy or run today. There is no mesh download, no solver job and no plan meter for HENMESH yet. This page describes intent so OEMs, UAV teams and labs can share feedback while we build. Do not treat this page as a shipping date.
Stack position
Where HENMESH sits
- 01
HENFOIL / HENSYNTH — live geometry & screening
- 02
HENMESH — prepare aerospace meshes (next)
- 03
HENFLOW — aerospace CFD on those meshes
- 04
HENSTRUCT — aerospace structural analysis & simulation
Honesty
Clear limits on this page
Not live
You cannot open, buy or run HENMESH today. No mesh jobs, seats or downloads exist under this name yet.
Not a CFD / FEA solver
HENMESH prepares domains. Flow fields belong to HENFLOW; structural runs to HENSTRUCT — both also upcoming.
Not a certification mesh claim
Authority mesh standards and certification FEA remain outside the product claim until we say otherwise.
Who it is for
- Aerospace OEMs preparing CFD or FEA cases
- UAV / eVTOL teams needing 2D section and 3D wing meshes
- Labs teaching mesh quality before a solver run
Also upcoming
Aerospace industry collaboration
Share thoughts and ideas — help us build better solutions
We are looking for aerospace industry collaboration. Share your thoughts, ideas and real workflow challenges so we can improve our products and deliver the best solutions for OEMs, UAV / eVTOL teams, labs and aeronautical engineering companies.
- What slows your team with tools you use today?
- What would make HENFOIL, HENSYNTH or our upcoming stack (HENMESH, HENFLOW, HENSTRUCT) more useful in your pipeline?
- Ideas for mesh, CFD or structural workflows we should prioritise next?