Bolt = StackBlitz, ie Bolt doesn't have it's own subscription plans - if you go to your stackblitz billing profile I linked above you can cancel and downgrade to the free plan!
Hi- Eric cofounder of StackBlitz/Bolt here, not sure what OP is talking about? You can cancel your subscription at any time over at https://stackblitz.com/settings/billing
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
Technically speaking yes, but practically it turns out you often need multiple levers to actually get resolution when dealing with bad faith actors.
At some point I intend to write a blog post about what happened so other startups have a frame of reference on how to deal with this sort of thing. Truly wild stuff and can be very counterintuitive.
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)
we haven’t ever pivoted from webcontainers, not sure what you’re talking about there. it’s been our main thing since forever :)
stackblitz itself is a product suite built on top of webcontainers. note that many issues in the repo you linked are not for webcontainers specifically, but instead mostly for stackblitz specific functionality.
we have about 3m devs/mo using us for free on stackblitz.com, so we do the best we can for free public issue triage but do prioritize our paying customers (we are a business after all :)
We originally thought the same but a few years back started seeing increasing demand outside of stackblitz itself.
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
Thanks for this feedback- we’ll definitely make it easier to land on the webcontainer.new demo from the homepage. I think our main concern initially was that without docs context it might be too confusing what’s going on, but I think we could find ways to ease that in that experience itself
Hi HN! Cofounder of StackBlitz/WebContainers here, cool to wake up and see this on the front page unexpectedly :) Happy to answer any questions!
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
Eric (StackBlitz CEO) here- just wanted to confirm that we are indeed using VitePress! By far the best documentation site generator available right now from a DX, design, and flexibility perspective. Highly recommend.
Eric (StackBlitz CEO) here- you can actually self host StackBlitz! You’ll just need our Enterprise Edition (https://stackblitz.com/enterprise) which can be run on any cloud or on-prem. Happy to answer any questions you might have!
Eric (CEO of StackBlitz) here- your explanation is 100% correct regarding why & how servers need to be used to power parts of WebContainer environments (i.e. proxying npm, git, transforming binaries, amongst a handful of other things).
Some of these operations can be cacheable which is ideal for scalability, but even the ones that cannot tend to be far cheaper than running VMs which incur by the minute CPU costs.
Our intention is to be fully transparent on the how & why, so I’m happy to answer further questions on all this! I also think it’d be good for us to include something more detailed like your explanation in our docs so that other folks don’t feel similarly confused when reading them- curious if there’s particular points that jump out to you that I can share with our team to include!
In regards to my comment 4 years ago, this was in reference to our v1 technology toolchain (turbo npm client, etc) which is all available as open source over at https://github.com/stackblitz/core.
In regards to WebContainer, it's still very much in beta and undergoing many internal API changes as we iterate, but we absolutely intend to release an OSS API once we hit GA.
Our current docs/developer portal has some additional API/config information on StackBlitz, WebContainer, etc (albeit still WIP): https://developer.stackblitz.com/
TL;DR this only lets you edit files, not actually run commands since there’s no underlying container (unless you pay by the minute for Github Codespaces).
This is in contrast to WebContainers which launched a few months ago (https://news.ycombinator.com/item?id=27223012) and enables VS Code to run entirely in-browser (including terminal commands) using a WebAssembly based operating system.
Source: worked on WebContainer and am CEO of StackBlitz