Sorry, it's like a way you can write browser extensions, but not have to worry about the limitations of the various browser vendors or their distribution channels, while delivering the "extended browser" by embedding it as a plug-in a web app. In essence, it's just a browser-as-API that you can embed and run inside a regular web app. This is possible because your web app only hosts the client-side interface which connects to a back-end of a headless browser running in the cloud or your server somewhere.
The no-frills, "just the browser" product, is normally called "remote browser isolation"[0] (or, RBI), but ViewFinder lets you build custom browsing extensions on top of this. So you can embed such a remote browser in your web app to encapsulate some off-site 3rd-party functionality that you nevertheless want to include in whatever process is part of that user story or task, for example, submitting a document that you just generated with the embedding web app, useful in the case where the 3rd-party provides no API to do so, making it more fluent than giving someone a list of instructions to then go off-site to follow, or doing it yourself "manually".
You can also use this interface to plug in to some existing headless browser, such as one running an automation job you have set up with puppeteer for observability and intervention if this bot gets stuck--for example, on a CAPTCHA.
One of the browsing extensions I built atop the basic RBI is "co-browsing" so you can have multiple people connect to the same cloud-based browser, from anywhere around the world, and view and interact with it simultaneously. Maybe two friends can watch a podcast at the same time and chat with the built-in chat? But mostly people are interested in this kind of thing for delivering live, real-time customer support to people who are using their app, while they interact with the client over the chat or a telephone. Ditto for training.
From a more meta level, it's a way to craft any programmable experience atop a browser, with somewhat more power that browser extensions (tho offset by the fact that my API is not well documented and can be improved for this purpose).
You run a browser in computer A, but you use the browser on computer B. How that works is B sends your inputs to A, and A sends the pixels back to B for display. B is in effect a dumb thin client.
The no-frills, "just the browser" product, is normally called "remote browser isolation"[0] (or, RBI), but ViewFinder lets you build custom browsing extensions on top of this. So you can embed such a remote browser in your web app to encapsulate some off-site 3rd-party functionality that you nevertheless want to include in whatever process is part of that user story or task, for example, submitting a document that you just generated with the embedding web app, useful in the case where the 3rd-party provides no API to do so, making it more fluent than giving someone a list of instructions to then go off-site to follow, or doing it yourself "manually".
You can also use this interface to plug in to some existing headless browser, such as one running an automation job you have set up with puppeteer for observability and intervention if this bot gets stuck--for example, on a CAPTCHA.
One of the browsing extensions I built atop the basic RBI is "co-browsing" so you can have multiple people connect to the same cloud-based browser, from anywhere around the world, and view and interact with it simultaneously. Maybe two friends can watch a podcast at the same time and chat with the built-in chat? But mostly people are interested in this kind of thing for delivering live, real-time customer support to people who are using their app, while they interact with the client over the chat or a telephone. Ditto for training.
From a more meta level, it's a way to craft any programmable experience atop a browser, with somewhat more power that browser extensions (tho offset by the fact that my API is not well documented and can be improved for this purpose).
[0]: https://en.wikipedia.org/wiki/Browser_isolation