Most of our customers ask the question: "How does ThumbmarkJS differ from X?". Most often we are compared to fingerprint.com, which we welcome. And while ThumbmarkJS has a lot in common, it is meant for a different market.

While ThumbmarkJS certainly is a highly accurate visitor identification solution, we first and foremost aim to be the best at scale. This means we always prioritize the scalability (performance and cost) over adding each possible feature. While use-cases are many, being great at the core features at scale is the key to success.

The pieces of the puzzle

1. Own the entire fingerprinting stack

2. Architect for scale

3. Focus on the core

Own the entire fingerprinting stack

Unlike most of our competitors, ThumbmarkJS owns the entire fingerprinting stack in the client and the backend. This allows us to optimize each step of the process for maximum efficiency.

In the past, we've seen some solution providers struggle with providing their services due to dependencies on third-party technology and license changes. Since the technology doesn't differentiate them, many take the strategy of packaging third-party solutions and essentially reselling them. This path often leads to a cost base that will not scale into the billions.

Additionally, there is almost a monopoly of high-quality, high-accuracy browser fingerprinting technology. Being on the receiving end of this technology puts one at a disadvantage, as you are always at the mercy of the provider. At ThumbmarkJS, having achieved the highest levels of accuracy with our own tech, we control our future and can guarantee it for our customers as well.

Architect for scale

Building a system that works isn't hard. Building a system that scales to the billions cost-efficiently is. Since our purpose from the start has been to be the best at scale, we've spent countless of hours choosing the right system design and architecture to make it possible. Fortunately, achieving a system that scales efficiently is difficult enough that it puts us at a distinct advantage.

Doesn't AI solve this? Not at all. Creating scalability from the design requires one to understand the system as a whole, not just the parts that are easy to optimize. AI is great at optimizing individual parts, but it's not good at understanding the system as a whole. You need experience to do that.

Focus on the core

Adding features costs everyone. It's tempting to win a customer by adding a feature they ask for. But how do you know if you should or not? We at ThumbmarkJS always weigh the commonality of the need against and the cost of adding it. Implementation is cheap, but if the feature jeopardizes the scalability (in either performance or cost) of the system, we avoid it. Having all bells and whistles is not the goal, but rather serving the core use-cases at scale.

How well does ThumbmarkJS scale?

Due to the scalable, high-concurrency architecture, serving 1 million or 1 billion requests in a day is more or less the same. No matter what your scale is, we can handle it. Most often the question is, does the cost make sense for your use case? Fortunately, at high volumes, we do offer volume discounts.