Good questions!

This currently runs only on your local machine. We do have a cloud version coming soon, but running your bots this way will be optional.

Yes, the code only is stored, not the data it processes. We could encrypt them so we can't read, but it would prevent us updating your scripts in future for new versions of axiom.

It does mean we could run your code, but this is not something we do, unless you want us to run your script in our cloud.

UI.Vision and long-established macro-recorders like iMacros target developers; this is a complete no-code approach.

Our tool is primarily built for non-technical people. We also have and are building up a bot sharing system (i.e. templated bot app store). It will be subject to manual vetting for quite a while.

In a previous company we were scraping customers web pages to load customer and product information because the number of systems and teams involved to connect to their CDP would take months to get up and running. A few problems we had to solve was the web pages changing underneath us and some pages not being formatted the same. We ended up having to detect those changes server-side to alert us to update the scraper. How do you all deal with these use-cases?

Also, we tried to leverage: https://www.diffbot.com/ but the lack-of-accuracy/lack-of-complete-data + cost never justified it's usage.

Yes, very good question (I've answered a similar one on detecting whether the page has finished loading).

It's a deceptively hard problem. Essentially, what we do is fingerprint the element. If the page changes, it boils down to how effective our fingerprinting and search algorithms are, to find the element if it has moved or changed.

The algorithms behind that are good enough for most use-cases now, but it's something we're continuously iterating on.