I think I was posting an open source project of mine too many times (2-3 times different posts on about the same project but different angles) pointing to the same domain. Maybe the consensus is that it is utter garbage, who knows hahah.
Wasn't trying to spam, figured that if there was no interest it'd sink without a trace. Which it did of course as nobody saw it. I was generally just trying to get a temperature check on whether it was a good idea or not. I understand, I mean, HN's house HN's rules - genuinely don't want to turn this into a debate about moderation!
This is great insight, thank you. I have recently learnt that being shadow banned doesn't help either, so not sure if you'll see this comment. Either way, great work.
Delving deep into novel ways to extend Excel and make it more accessible. Perhaps different approach to copilot in that AI is only used during authoring, the yielded output being a standalone artifact.
It embeds Luau which tames the very old school C SDK. This means that the same code can run as native add-ins on Windows (XLL) and the more modern-but-far-slower web engine, thanks to WASM. Luau is safe and fast.
The exact same bytecode runs in both styles of add-in. You get the performance of native with no extra work. Many approaches for writing custom functions are unacceptably slow, particularly when their inputs come from fast moving realtime data feeds.
I know Luau is perhaps a left-field choice. However, coupled with a coding assistant and bringing that lightweight conversational dev experience right into Excel (xllify Assistant is an add-in itself) this is perhaps less of a barrier.
xllify takes your existing Excel formulas or VBA and produces clean, reusable custom functions packaged as proper add-ins. You can also just describe what you need in plain English.
Yes, this part is an LLM wrapper. LLMs can reliably write code that targets xllify, given adequate guardrails.
The engine is written in C++ and uses Luau (Roblox's Lua fork) as the sandboxed scripting runtime. Luau might seem an odd choice, but it's genuinely well-suited here, it's fast, sandboxed, and compiles easily for both native and WASM targets. And you don't really need to know Luau to use xllify: the AI writes it for you. We'll see if Luau is a barrier.
Anyway, the same Luau code runs two ways:
.. As a native XLL add-in on Windows, talking directly to Excel's C API. This gives you in-process, multi-threaded function execution with low overhead. If you've ever wrestled with the C API directly, you know why this matters. It's extremely fast but utterly brutal to work with. xllify tames.
.. As a web-based add-in via WebAssembly, using the Office JS platform. Same code, same functions, but now deployable on Mac and Web with all the discoverability and security benefits that come with the modern add-in model.
Luau coroutines are supported, so functions can do non-blocking work (API calls, streaming data) without locking up the calculation chain. The runtime ships with a comprehensive standard library so you're not starting from nothing.
DuckDB is available to do heavy lifting on data analytics problems on data that might be too big to fit into Excel.
LLMs can hallucinate, so xllify doesn't rely purely on generation. The AI will select from a library of verified, tested functions where they exist rather than generating from scratch every time. Industry-specific function packs (finance, healthcare) are on the way.
There are two ways to build:
.. xllify Assistant runs inside Excel itself. You have a conversation with the assistant, build and test functions live, and when you're done you can export a .zip with a ready-to-deploy add-in setup including the package.json Office JS packages.
.. xllify agent tooling for local development if you prefer working in your own editor/terminal.
The add-ins are fully self-contained. No runtime dependencies, no phoning home, no ongoing model costs. Once built, it's yours. Works in air-gapped environments.
Try the online demo and sign up for early access: https://xllify.com - I would love your thoughts on this niche little thing.
Thank you! Yes they've been around a long while. They perform well and can make use of multiple threads etc. The SDK is pretty old school so best to use a layer on top such as xllify, Excel-DNA...
Wasn't trying to spam, figured that if there was no interest it'd sink without a trace. Which it did of course as nobody saw it. I was generally just trying to get a temperature check on whether it was a good idea or not. I understand, I mean, HN's house HN's rules - genuinely don't want to turn this into a debate about moderation!