92 karma · joined March 11, 2020
Based on the feedback in this thread we're going to be releasing an updated version that focuses more around tooling for the browser agents themselves as opposed to scaling/scheduling, so stay tuned for that!
Playwright and other browser automation scripts are a much more powerful version of RPA but they do require some knowledge of code. But there are more and more developers every year and code just gets more powerful every year. So I think it's a good bet to make that browser automation in code will replace RPA altogether some day.
What does this check look like for you? Do you just diff the html to see if there are any changes?
1. Developer tooling should be open source by default 2. Open source doesn't meaningfully affect revenue/scaling because developers that would use your self-hosted version would build in-house anyway.
Our approach is a bit different. With finic you just write the script. We handle the entire job deployment and scaling on our end.
Uses weaviate so that even the vectorstore can be self-hosted
Some examples use cases for Sidekick include:
- Customer support bots that answer questions based on your knowledgebase
- Internal tools for searching through documentation scattered across different SaaS tools
We'll also add support for huggingface embeddings like MPNET and SBERT in the future!
It means that the bot may not always provide the correct response to a question, even if the answer can be found in the support documents. The bot may not have access to all the information or may not be able to understand the context of the question.