Thank you once again, Pier, for this excellent summary!
While reading the sections on different browser fingerprinting techniques, I wanted to add a few extra insights. If you're interested in diving deeper into this topic, check out the Browser Fingerprint section of our knowledge base:
"You run it on your machine, and it works smoothly, but then, after you deploy it on a VM or a server, it gets detected and stops working."
If this sounds familiar, just watch the video in the linked article, and you’ll see why. With our method, it's possible to emulate a macOS device on a Windows Server while maintaining a consistent browser fingerprint. The next challenge we’re tackling is achieving a bulletproof, masked fingerprint in headless mode within Docker. We hope to soon reach the same level of success as we have on Windows Server.
Another interesting topic in the article is "Headless Browsers vs. Real Browsers." I’m happy to share that when you run our custom-built browsers, Chroma and Junglefox, in headless mode, you get the same high-quality fingerprint as in headful mode.
Lastly, a thought on Browser as a Service: If you're reading this, chances are you're already considering building your own web scraping infrastructure to cut costs. That’s exactly what you can do with Kameleo for web automation. Unlike other solutions, we don’t charge based on bandwidth or requests—only on the number of Parallel Automated Browsers you use. This lets you optimize costs efficiently.
Thank you once again, Pier, for this excellent summary!
While reading the sections on different browser fingerprinting techniques, I wanted to add a few extra insights. If you're interested in diving deeper into this topic, check out the Browser Fingerprint section of our knowledge base:
🔗 https://help.kameleo.io/hc/en-us/sections/360000880477-Browser-fingerprint-technologies
In particular, I recommend this article on Intelligent Canvas Spoofing, which explains Kameleo’s unique approach:
🔗https://help.kameleo.io/hc/en-us/articles/7021925786397-Intelligent-Canvas-Spoofing-Our-research-on-canvas-fingerprinting
Pier mentions in the article:
"You run it on your machine, and it works smoothly, but then, after you deploy it on a VM or a server, it gets detected and stops working."
If this sounds familiar, just watch the video in the linked article, and you’ll see why. With our method, it's possible to emulate a macOS device on a Windows Server while maintaining a consistent browser fingerprint. The next challenge we’re tackling is achieving a bulletproof, masked fingerprint in headless mode within Docker. We hope to soon reach the same level of success as we have on Windows Server.
Another interesting topic in the article is "Headless Browsers vs. Real Browsers." I’m happy to share that when you run our custom-built browsers, Chroma and Junglefox, in headless mode, you get the same high-quality fingerprint as in headful mode.
Lastly, a thought on Browser as a Service: If you're reading this, chances are you're already considering building your own web scraping infrastructure to cut costs. That’s exactly what you can do with Kameleo for web automation. Unlike other solutions, we don’t charge based on bandwidth or requests—only on the number of Parallel Automated Browsers you use. This lets you optimize costs efficiently.