finic

Playwright or Puppeteer over Chrome DevTools Protocol (CDP). For example: browser = await pw.chromium.connect_over_cdp('ws://localhost:8000/ws') Each connection to the WebSocket spins up a new Chrome session in headed mode, and you can run multiple sessions concurrently. Unlike other solutions, Finic is fully open-source (Apache 2.0 licensed). You can try it by pulling the official Docker image or cloning the repo at Finic on GitHub (https://github.com/finic-ai/finic) and running `docker-compose up --build`. This approach simplifies handling Chrome for scraping, saves on cloud costs, and keeps your setup clean. Give it a try!

re must be many tools for the job. The truth is that web scraping strategies need to constantly adapt as web standard change, and as companies that don’t want to be scraped adopt new technologies to try and block it. The old standards never completely go away, so the longer the internet exists, the more edge cases you’ll need to account for. This adds up to a LOT of infrastructure that needs to be set up and a lot of schlep developers have to go through to get up and running. Scraping is no easier today than it was 10 years ago - the problems are just different. Finic is an open source platform for building and deploying browser agents. Browser agents are bots deployed to the cloud that mimic the behaviour of humans, like web scrapers or remote process automation (RPA) jobs. Simple examples include scripts that scrape static websites like the SEC's EDGAR database. More complex use cases include integrating with legacy applications that don’t have public APIs, where the best way to automate data entry is to just manipulate HTML selectors (EHRs for example). Our goal is to make Finic the easiest way to deploy a Playwright-based browser automation. With this launch, you can already do so in just 4 steps. Check out our docs for more info: https://docs.finic.io/quickstart

e more complex. - Dedicate resources to building integrations in-house, which takes away resources that could be put towards building features that actually get you new customers. We’re hoping to eliminate this tradeoff with an iPaaS that allows developers to build new integrations fast, but is also flexible and robust enough to scale with the company’s needs. We’ll do this with a few key features: * Declarative connector engine: Rather than taking the standard approach of building out-of-the-box connectors, we want to focus on making it as fast as possible for developers to build custom connectors while abstracting away the network-level features like backoff and error handling and every company needs to ship an integration to production. * Bundle connectors + orchestration + monitoring: Many companies have to mix and match different tools to build end-to-end integrations. They need a vendor for connectors (Airbyte, FiveTran), one for orchestration (Dagster, Airflow), and another for monitoring (Datadog). This gets expensive fast. By focusing on custom connector development rather than building our own, we free up resources to also include orchestration and monitoring features that are good enough for most use cases. * Generative AI bridge: LLMs are great at writing and explaining basic code. We can leverage that to save developers time, while also making it accessible to non developers. We’re still in alpha and the project isn’t ready for production use yet, but we wanted to launch early and get the community’s input. https://finic.ai/