ericmsimons

Here's a screenshot I just took of my own billing page (see the "cancel subscription" link under the "Current Plan" section): https://imgur.com/a/6ZTWgEL

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)

Surprisingly a very large and growing number of use cases across interactive edu tools, AI code execution (https://webcontainers.io/ai), SaaS dev envs for end users to write code, amongst others

Btw one emergent use case we've seen growing rapidly has been code execution for AI agents. Would love thoughts/questions/feedback if you’re working on things in that space: https://webcontainers.io/ai

Happy to answer any q's!

This is closer to what the Bytecode Alliance is looking to do with WASI, which we're playing a small (but crucial) part in: https://blog.stackblitz.com/posts/bytecode-alliance/

> Does "WebContainer API" mean "proprietary web service for accessing npm and git over http"?

Kinda, we have plans to allow self hosting and more reg open source- more to come!