Lesson learned: start with fewer metrics and observe how they are used and interpreted. It is much easier to expand correctly from there. Collecting requirements in a single pass and building a monolith is rarely as productive as it seems - because the barrier to adding things and shifting responsibility to the dashboard is so low in the beginning, that it can easily become a dumping ground.
AFAIK this would be the first such firm focusing on zero knowledge cryptography. The blog doesn't say they are focusing solely on blockchain, but there is a noticeable gap there, as such financial contracts move increasingly to zero-knowledge implementations.
A web3 stack, everything client-side and peer-to-peer. HTML/CSS/JS for front-end. JS/blockchain for backend. JS client-side storage/compute, JS libp2p library for peer-to-peer discovery, networking, syncing, updates, user-generated content, etc. Blockchain for things that need to be tamper-proof or involve payment.