Search Results for "chrome"
Sort By:
Showing 2 open source projects for "chrome"
View related business solutions-
Turn traffic into pipeline and prospects into customersDocket is an AI-powered sales enablement platform designed to unify go-to-market (GTM) data through its proprietary Sales Knowledge Lake™ and activate it with intelligent AI agents. The platform helps marketing teams increase pipeline generation by 15% by engaging website visitors in human-like conversations and qualifying leads. For sales teams, Docket improves seller efficiency by 33% by providing instant product knowledge, retrieving collateral, and creating personalized documents. Built for GTM teams, Docket integrates with over 100 tools across the revenue tech stack and offers enterprise-grade security with SOC 2 Type II, GDPR, and ISO 27001 compliance. Customers report improved win rates, shorter sales cycles, and dramatically reduced response times. Docket’s scalable, accurate, and fast AI agents deliver reliable answers with confidence scores, empowering teams to close deals faster.
-
Outbound sales softwareAdversus is an outbound dialing solution that helps you streamline your call strategies, automate manual processes, and provide valuable insights to improve your outbound workflows and efficiency.
-
1
Turborepo
Build system optimized for JavaScript and TypeScript, written in Rust
Turborepo is a high-performance build system for JavaScript and TypeScript codebases. Turborepo reimagines build system techniques used by Facebook and Google to remove maintenance burden and overhead. Building once is painful enough, Turborepo will remember what you've built and skip the stuff that's already been computed. Turborepo looks at the contents of your files, not timestamps to figure out what needs to be built. Share a remote build cache with your teammates and CI/CD for even... -
2
Rendora
dynamic server-side rendering using headless Chrome
...Node.js/Express.js, Python/Django, etc...) and potentially your frontend proxy server (e.g. nginx, traefik, apache, etc...) or even directly to the outside world that does actually nothing but transporting requests and responses as they are except when it detects whitelisted requests according to the config. In that case, Rendora instructs a headless Chrome instance to request and render the corresponding page and then return the server-side rendered page back to the client (i.e. the frontend proxy server or the outside world).
- Previous
- You're on page 1
- Next
