Frequently asked questions

We design and build custom engineering software for aeronautical and aerospace applications — solvers (CFD, structural, thermal, aeroelastic, propulsion), CAD kernels (2D/3D geometry cores), and desktop products: HFOIL (aeronautical CAD), HENMESH (aerospace mesh preprocessor + HEN-AI), HENFLOW (aerospace CFD + HENAI), and HENSTRUCT (aerospace structural FEA). We build to your specific problem rather than selling a fixed, one-size-fits-all platform.

Those platforms are built to serve every industry at once — automotive, civil, marine, aerospace, and more — which means you're paying for breadth you'll never use, and the tool wasn't designed around aero-specific decision-making in the first place. We do the opposite: we scope a solver or tool tightly to your exact engineering problem, built by someone with an aeronautical engineering background, not a general-purpose physics engine retrofitted for your industry. We're not trying to replace ANSYS for enterprise-scale multiphysics — we're the option for teams who need something precise, affordable, and built around their actual aeronautical workflow.

Four groups mainly: OEMs and manufacturers needing solver capability scoped to a specific product line; research labs needing validated, explainable tools rather than black-box outputs; academic programmes needing affordable aircraft geometry CAD for teaching; and UAV/eVTOL startups needing flight dynamics, propeller aerodynamics, and mission tools without enterprise CAE overhead.

Both. HFOIL, HENMESH, HENFLOW, and HENSTRUCT are standalone products you can license directly. Alongside that, we take on custom solver and CAD kernel development for teams with specific requirements the product line or off-the-shelf tools don't cover.

Sundarapandi Muthupandi, our founder, holds a B.E. in Aeronautical Engineering and has 7 years of hands-on experience building engineering software — solvers, CAD systems, and simulation tools. The engineering leadership on every project has aerospace domain background, not just software development experience.

We validate every solver against known analytical solutions, published test data, or your own reference data before delivery — and we tell you exactly what's been validated and against what benchmark. If a capability is still in development, we say so directly rather than presenting it as production-ready. We'd rather lose a sale than have our software feed a wrong number into your design decision.

We work with aeronautical and aerospace clients across OEMs, UAV/eVTOL programmes, research labs, and academic teams. We're glad to walk through relevant technical work on a call — including code-level detail where appropriate. Some client work is under NDA, so we tailor what we share based on your specific use case. Reach out and we'll show you what's most relevant.

Yes — HENDOI TECHNOLOGIES PRIVATE LIMITED, registered in Chennai, India. GSTIN: 33AAGCH6765E1ZK, CIN: U62099TN2023PTC158630. Full registration details are on our About page.

A native desktop application for aerospace aircraft geometry CAD — mission templates, parametric full-aircraft rebuild, wing/fuselage/tail builders, airfoil library, Geometry Studio, assembly, drawings, and STEP/IGES/STL export. Not general mechanical CAD. Volume CFD is HENFLOW; mesh prep is HENMESH; structural FEA is HENSTRUCT.

HENMESH is the aerospace simulation preprocessor (16 Phase 6 prep workbenches, Phase 7 HEN-AI, industrial BL/HexCore/overset, quality gates, suite export). HENFLOW is aeronautical/aerospace CFD (external aero, compressible, high-lift, rotorcraft, rocket/missile, reports, thirteen HENAI pillars). HENSTRUCT is aerospace structural FEA (static, dynamics, buckling, composites, fatigue, thermo-structural, aeroelasticity, margins). Typical chain: HFOIL (CAD) → HENMESH → HENFLOW and/or HENSTRUCT.

If your need fits HFOIL geometry, HENMESH mesh prep, HENFLOW aerospace CFD, or HENSTRUCT aerospace FEA, license the product. If you need owned solver IP, mission-level simulation, or a solver integrated into your own product — that's custom development. Not sure which fits? Tell us your problem and we'll tell you honestly which path makes sense.

Details are on each product page (HFOIL, HENMESH, HENFLOW, HENSTRUCT) — reach out via Contact for current licensing and pricing.

Very likely — our services page lists the solver and kernel categories we work in, but that list reflects our roadmap and core capability areas, not a hard boundary. Share your aeronautical requirement and we'll give you an honest feasibility read: what's straightforward, what's harder, and a realistic timeline.

It depends entirely on scope — a focused single-physics solver (e.g., a propeller BEMT solver) is a very different timeline from a coupled aero-structural-thermal solver. On a scoping call, we give you a realistic estimate up front, not an optimistic one we'll miss.

Depends on what serves you best. For some problems, building from first principles gives you full ownership and control. For others, integrating a proven open-source core (e.g., OpenFOAM-based CFD) under a custom interface and workflow is faster and more cost-effective. We'll recommend whichever approach actually fits your budget, timeline, and IP requirements — not whichever is easier for us.

If your product's roadmap depends on deep control over geometry — custom feature trees, specialized sketch constraints, tight integration with a proprietary solver — licensing a third-party kernel can become a long-term constraint. Owning your kernel means your product's geometry engine evolves on your timeline, not a vendor's.

That's specifically the gap we built HENDOI to fill. Enterprise CAE licensing often puts real solver capability out of reach for smaller aeronautical teams. Because we scope projects tightly instead of selling a broad platform, we can price closer to what a startup or lab budget can realistically support. Tell us your budget constraints upfront — we'll tell you honestly what's achievable within it.

You describe your problem — what you're trying to simulate, analyze, or build, and what you've tried so far. We ask clarifying technical questions, then follow up with architecture options, a feasibility assessment, and a realistic timeline. No sales pressure, no pre-built pitch deck.

Yes, on request — standard practice for engineering IP discussions.

Contact us with a short description of your problem, or view our services to see the solver and kernel categories we work in. We'll respond with next steps directly — no multi-week sales process.