Protect a sign-up form from fake sign-ups, fake accounts and abuse
Fake sign-ups come from programs that create accounts in bulk on a sign-up form. Antisy checks that each sign-up comes from a browser and not from a program, before the account is created, with no puzzle for the person signing up.
Where do fake accounts and sign-up abuse come from?
A sign-up form open to everyone is open to programs too: they create accounts on it in bulk, which they then abuse. It is simpler to refuse a fake account at sign-up than to remove it afterwards.
See: Fake accounts and sign-up fraud: what they are, what they cost
How does Antisy stop fake sign-ups?
The sign-up page carries Antisy’s tag, and a token goes with each submission. Before creating the account, your server makes a call, assess, which ties the token to the account. The answer has two outcomes: allow, create the account; deny, refuse, without saying why.
The siteverify call of simple forms does not tie the token to an account: it does not suit a sign-up.
Which data is processed?
What the script measures for any submission, and what the table of retention periods keeps of a sign-up: a login identifier, encrypted and hashed, and the outcome of the attempt, deleted after 90 days.
Is it available today?
Not yet. The Node server kit (Express, Fastify, Next.js) that makes this call will be published on npm; it is not yet.
Access is by waiting list. The API and the dashboard (in French) have been in service since 27 October 2026, hosted at Infomaniak in Geneva; no customer is in production yet. A pilot is planned; it has not started.
See: The pilot · Join the waiting list
What a bot check does not replace
No bot check is perfect, and Antisy announces no detection rate. It adds to the other defences of an account, such as limiting attempts or a second factor; it does not replace them.