About / Product mission
Engineering software should show its working.
VehicleLab explores how transparent, browser-based tools can make vehicle-dynamics models easier to inspect, run, question, and validate.
- Runs locally
- No simulation data uploaded
- Deterministic direct + RK4 solvers
- SI units
- Canonical cases verified
- Release 2.1.1
Mission
Make the path from equation to result legible.
VehicleLab is an engineering application where users can understand a model’s force balance, configure its assumptions, execute it without installing a specialist desktop stack, and inspect numerical evidence alongside the response.
Browser delivery matters because it reduces setup friction. Transparency matters because accessibility without visible equations, conventions, and limits can create false confidence.
Product principles
Rules for the current product.
- 01
Explain before amplifying
Present the model and its meaning before using visual output to build confidence.
- 02
Keep context near results
Units, signs, assumptions, and limitations belong close to the quantities they shape.
- 03
Compute locally by default
Deterministic browser execution keeps the current study responsive and private.
- 04
Make evidence visible
Validation is part of the product experience rather than a hidden implementation detail.
- 05
Earn model complexity
Add capability only when a testable engineering reason justifies it.
Current status
VehicleLab 2.1.1
VehicleLab combines browser-local Quarter-Car and Half-Car studies, Full-Car 7-DOF Ride, qualified Planar Handling, and prepared 14-DOF / 28-state coupled vehicle dynamics. Native C++/WebAssembly and TypeScript reference implementations retain explicit numerical identities.
The applied vehicle supports moving-rack Double-Wishbone mechanics, tire forces and physical Motion. Flat, Raised Cosine, Sine and supported smooth OpenCRG surfaces feed the qualified Road-contact model. Standalone suspension, steering and tire labs provide focused inspection and independent evidence.
Engineering plots, CSV and provenance exports follow completed results. Reports and video are available in their documented workflows; applied 14-DOF video remains deferred. Save/Open retains supported project definitions, with imported source files reattached locally.
Explore current full-vehicle dynamics or inspect the verification evidence.
Current limitations
Narrow by design
Generic parameters are uncorrelated to measured vehicles. Coupled Road dynamics use a qualified smooth, continuously loaded point-contact envelope, not arbitrary terrain or finite-width tire contact. Supported OpenCRG ingestion has explicit feature and domain limits. Prescribed 7-DOF Ride may accept inputs rejected by 14-DOF contact. MacPherson geometry is a qualified standalone workflow, not an applied full-vehicle dynamics option. Numerical verification is not certification or a general-purpose multibody claim.
Future direction
Discuss an engineering use case.
For an engineering conversation, pilot interest or product feedback, visit Varad Karkhanis’s public website. Dedicated VehicleLab inquiry channels and premium offerings are future plans.
Discuss a pilot / Contact →Future model, workflow, and comparison capabilities may be explored when they have a clear engineering purpose, explicit assumptions, stable data contracts, and validation cases. This is a direction—not a claim that those features are committed or complete.