Rust/WASM Lighting Toolkit

What it does

This toolkit parses lighting measurement files and converts them into SVG visualizations. It handles both legacy photometric formats (EULUMDAT from 1990 and IES from 1991) and newer spectral standards (TM-33 and ATLA-S001). Users can load old lighting data files and generate graphics that designers can work with.

Who it is for

Lighting designers and engineers who work with photometric data. Teams managing lighting product specifications where files span decades of different formats. Anyone transitioning from legacy lumen-based measurements to modern spectral wavelength data.

Pricing

The site does not show prices.

How it stands out

The toolkit targets a gap in existing tooling. Legacy formats still dominate industry workflows despite being three decades old, but most modern software has dropped support for them. This project maintains backward compatibility while adding support for newer spectral standards that most established tools barely cover. By offering both sides—old and new—it positions itself as a bridge for an industry in transition.

The choice to publish on both crates.io and PyPI suggests dual positioning: Rust developers get a native package, while Python users (common in data analysis and design work) get straightforward access. The WASM component implies browser-based editing is possible without server infrastructure.

What a founder should check

First, verify the actual switching costs. Legacy file formats have been around for 30+ years, which means there are embedded workflows, institutional knowledge, and competing tools that handle them. Check whether lighting engineers perceive their current process as painful enough to adopt something new, or if they view format conversion as a solved (if tedious) problem.

Second, understand the market size for spectral data support. TM-33 and ATLA-S001 represent the future, but adoption may still be limited. Research how many companies actually need spectral analysis versus basic photometric data. The revenue opportunity depends on whether this is addressing a real bottleneck for a substantial customer base or solving a problem that only niche users face.

Third, examine the competitive moat. Incumbent lighting software vendors (often tied to specific manufacturers) control large portions of the workflow. Even if this toolkit is technically superior, vendors might integrate spectral support themselves, or customers might stay locked into existing products due to switching costs and integration with CAD software they already use. Assess whether being a standalone tool—rather than a plugin or integrated solution—limits market penetration.