As far as I can tell, it can. The code itself has a `LICENSE` file with the Apache license, and the readme says "The model is licensed under the Apache 2.0 license.". Strangely, the FAQ in the blog post doesn't address this question, which I expect will be frequent.
Apache 2 is just about as business friendly as you can get. It's:
* Do what you want
* Don't sue us
* You license any patents you control and used in this work. If you sue someone for patent violation for using this then other entities can counter sue you for violating any of their patents used in this work.
There is no viral nature, and it is older than GPLv3.
It's most simialr to BSD of the licenses you list.
LGPL is not business friendly at all. It's among the least business friendly licenses there is. Apache 2.0 is slightly more business friendly than BSD.
With some caveats, software licenses from most to least business friendly roughly go:
LGPL is more business friendly than GPL; it's literally "lesser" GPL.
You can use LGPL in commercial, closed-source projects as long as you keep the LGPL code in a separate dynamically linked library, e.g. a DLL, and provide a way for users to swap it out for their own patched DLL if they wish. (Plus some other license terms.)
Also, you can always use LGPL code under the terms of the GPL, so there's no way LGPL is more restrictive than GPL.
Beware that you may need to be careful using LGPL code in a browser: JavaScript is source code not object code, arguing WASM is a DLL wouldn’t help, most JavaScript minifiers perform static linking, and sending LGPL code to the browser could be considered distribution. I always avoided all LGPL licensed libraries when doing commercial front-end work.
