Wow, really cool project. As someone who's not primarily a frontend developer but has had to write a lot of browser-based feature tests, I love the concept and execution.

Why the subscription model though? That's the one thing that concerns me.

Is data being sent back to your servers to enable some of the functionality? I don't speak for my employer here, but as someone who works in the healthcare technology industry, if I wanted to get my bosses to buy into this, I would be looking for something that we license to run on our environments.

Thank you!

> Why the subscription model though?

The subscription model is primarily to cover the costs of creating and running automations at scale (i.e., LLM code gen and browser uptime) and to build a sustainable business around those features. We included the free tier to give users access to the IDE, but we're committed to adding value beyond just the IDE and subscriptions support that.

> Is data being sent back to your servers to enable some of the functionality?

Yes - we save all notebooks in our database. Since we're working to build a lot of value-add features for hosted executions, having notebooks saved online worked in service of that.

That said, we're now thinking about the local-only / no sign-up use case as well. We've gotten a lot of feedback about this, so it's something we're taking seriously now that we've gotten all of the core functionality in.

I will also add, we are HIPAA-compliant for healthcare use cases.

Really appreciate the questions!