Good question, here's the link to it: https://patents.google.com/patent/US20220417315A1/en?q=(stackblitz)&oq=stackblitz https://patents.google.com/patent/US2022

Good question, here's the link to it: https://patents.google.com/patent/US20220417315A1/en?q=(stackblitz)&oq=stackblitz https://patents.google.com/patent/US20220417315A1/en?q=(stac... It's somewhat specific to our use case as you'll see when you read through. A motivation for securing this was that we've had issues (one instance in particular) where we caught a direct competitor directly copy+pasting code from our compiled builds into their own competing product. Asking them nicely to stop didn't do anything, nor getting emails from our lawyers. The main lever a startup has to solve this is to keep innovating and being the best product in the market, which is what we have done & continue to do. But having a patent is a useful lever for general deterrence from bad actors like this. (Also want to say thanks and give credit to Vinay Hiremath, cofounder of Loom, who went through similar in the early days of Loom and helped point us down the path of securing a patent)