AutoLISP Interpreter: Rust/WASM AutoLISP interpreter for CAD workflows

What it does

AutoLISP Interpreter is a browser-based implementation of AutoLISP, the programming language built into AutoCAD. It runs as a Rust application compiled to WebAssembly, allowing AutoLISP code to execute in a web browser without requiring AutoCAD installation. The tool can output results in SVG and DXF formats (AutoCAD R12/AC1009). It supports core AutoLISP functions including defun, setq, if, while, cond, mathematical operations, trigonometric functions, list manipulation, and drawing commands.

Who it is for

The primary audience is engineers and technical users who rely on AutoLISP-based workflows for CAD automation, particularly those needing to preserve or migrate legacy automation scripts. Organizations running schematic generation, parametric drawing creation, or other AutoCAD-based procedural tasks could benefit. The tool also appeals to software historians and developers interested in functional programming or the history of LISP in AI research.

Pricing

The site does not show prices.

How it stands out

This interpreter fills a specific gap: running AutoLISP without AutoCAD. Most existing solutions require the full AutoCAD application, which carries substantial licensing costs. By moving execution to the browser via WebAssembly, the tool removes that dependency. The project emphasizes preservation—capturing a three-decade-old workflow pattern (CSV-to-schematic automation from 1991) before the knowledge disappears. The source code is available on GitHub, giving transparency on implementation and function coverage.

What a founder should check

Anyone building a competing solution should investigate: (1) Incumbent moat: AutoCAD's dominance and whether Autodesk offers or plans browser-based AutoLISP execution, making this obsolete. (2) Completeness of function coverage: AutoLISP has hundreds of functions; this interpreter supports a subset. Verify which functions matter most to target users and whether the gap is a switching barrier. (3) Lock-in and ecosystem effects: Most AutoLISP users have years of scripts and integrations tied to AutoCAD's full environment. Test whether missing functions, performance differences, or output format limitations prevent real-world migration, or whether users will always maintain AutoCAD licenses anyway.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.