Sentium is not yet publicly available. We've got our proof of concept ready, which you can try below. Contact us
Bots are getting smarter and harder to stop, and existing solutions are not keeping up. It's time for a new cryptography based solution: Sentium, a no-data proof-of-work based challenge that respects user privacy.
Serverless infrastructure
GDPR & CCPA compliant
Zero cross-site tracking
Around 31% of all internet traffic is automated. Whilst automated traffic isn't inherently bad, malicious bots are used more and more to submit spam, commit fraud, and create fake accounts.
Sentium issues browser-based cryptographic challenges that are computationally expensive to solve. Legitimate users of your services remain unaffected, whilst bots waste their compute power on every request.
See how Sentium's challenge automatically executes when a user starts filling in their form, and how it's already done by the time they're finished.
Sentium was added to this form with only a few lines of JavaScript code. Server-side challenge verification only requires one simple POST request to Sentium's API.
This fast-changing landscape results in enterprises being left with two options: creating a custom solution by combining multiple expensive providers together, or invading user privacy and collecting copious amounts of personal and tracking data from users.
To make matters worse, some users get incorrectly flagged as bots, forcing them to complete multiple challenges in a row. This makes your users unhappy and increases the chances of them leaving your platform.
Sentium's challenges work to clog up a bot's compute power to slow down their operation. This results in virtually no data needing to be collected, which in turn allows for a completely white-label solution. Your users don't even need to know Sentium exists.
As Sentium challenges are issued to the browser, they can start as soon as your user starts filling out a form, or even as soon as the page loads. The challenge will likely already be completed by the time the form is filled in.