IronCalc

Key features

• Rust calculation engine The core recalculates workbooks in Rust with bindings for JavaScript, Python, and C, which suits performance-sensitive embedding where a scripting-language engine would be a bottleneck. Sample applications in Next.js and Dioxus show how the engine slots into real web stacks.[1][2]

• 200+ spreadsheet functions The engine ships implementations of more than 200 functions with Excel-compatible behaviour, covering the everyday arithmetic, logic, lookup, and text operations most models rely on. The documentation maintains a full function list, so teams can check coverage for their specific models before adopting.[1]

• Real .xlsx import and export Workbooks open from and save to the .xlsx format, so files round-trip with Excel instead of living in a proprietary container. A dedicated xlsx package handles the conversion, and finished workbooks download directly from the browser.[1][2]

• Browser workbook app A hosted app lets anyone create and edit spreadsheets with no signup, while the same app can be downloaded and self-hosted for private use. That duality means evaluation starts instantly and production can move behind the firewall.[1]

• MIT licence The software is free for personal and commercial use under the MIT licence, which keeps procurement simple for companies that rule out copyleft or seat-licensed tools. There are no paid tiers or gated enterprise features to negotiate around.[1]

• Embeddable packages Developers install the engine from Cargo, npm, or PyPI and call its functions directly, turning IronCalc into a calculation service inside a larger product. One package-manager command is enough to start, which keeps proof-of-concept work cheap.[1][2]

• Formatting, charts, and names The app supports cell styling, charts, defined names, and freeze panes, so shared workbooks can be readable documents rather than raw grids. These are the presentation features that decide whether colleagues accept a non-Excel tool.[1]

• Open roadmap Published plans name what is missing, including pivot tables, collaboration, and print support, letting adopters judge the gaps before committing. Funded milestones already completed suggest the list shrinks rather than grows.[1]

Who will love it

• Developers embedding calculation Teams building pricing tools, calculators, or reporting features get an MIT-licensed engine with packages in three ecosystems instead of licensing a proprietary SDK.[1][2]

• Self-hosting teams Organizations that keep documents on their own infrastructure can run the workbook app themselves rather than sending spreadsheets to a third-party cloud.[1][2]

• Open-format standardizers Groups exchanging .xlsx files with Excel users but refusing proprietary lock-in get genuine import and export in a free tool.[1][2]

Who should avoid it

• Real-time collaborators Teams that co-edit with live cursors and comments need a suite with collaboration today; IronCalc documents it as future work.[1]

• Pivot-table analysts Heavy Excel users depending on pivot tables, advanced print layouts, or complete Excel parity will hit documented gaps.[1]

• Non-technical buyers wanting support There is no documented paid support offering or established admin community, so buyers who need a help desk and proven references should wait.[1]

Alternatives and compatibility