Antisy for agencies: protect your clients’ forms

What Antisy brings to an agency

The step is the same on every site: one tag in the page and one call from the site’s server. Your clients’ visitors see nothing: no checkbox, no image to recognise.

• The same integration from one client to the next, described in the documentation and in the guides (PHP, Next.js, WordPress without a plugin).
• A verification mode set site by site: a cautious client can choose a stricter mode, another a more permissive one.
• A verdict with two results, allow or deny, without the reason: your server decides what happens next, form by form.

What your clients find in it

Antisy checks that a submission comes from a browser and not from a program. It is one more check for their contact, sign-up or newsletter forms; it is not a perfect check, and Antisy announces no detection rate.

• What the script measures, what the server reads and how long it is kept is written, line by line, in the Data section of the home page: you can hand it to a client who asks what the tool processes.
• The roles are stated: for a client’s visitors, the client is the controller and Antisy acts as processor. The model data processing agreement and the page on the FADP and Antisy describe them.
• No puzzle for their visitors: the article CAPTCHA and accessibility says why that matters.

How to put it on several clients’ sites

1. One organisation. The agency’s account gathers its sites in the dashboard.
2. One site per client (or per client website). Each site declares its host names: Antisy issues a valid token only to pages whose name is in the site’s list.
3. Keys per site. The public identifier goes in the page, the verification secret stays on the site’s server; they are created, replaced and revoked site by site (see keys and test environments).
4. One mode per site. The strictness is set site by site, with no slider and no value to enter.
5. The tag and the call. The step-by-step guide goes from creating the site to a protected form.

The number of sites included depends on the tier: see the pricing. Standard, Pro and Enterprise are on quote: tell us, in your message, how many sites you look after.

How to try it

The pilot started on 9 November 2026 on our own forms. If you want to try Antisy on a form of one of your clients, or on your own, the Pilot page says what it asks of your team and how to apply. Antisy acts only on a site whose owner has signed a written mandate, before any processing.

Otherwise, join the waiting list: it is the form of the home page.

Where does Antisy stand?

Access is by waiting list. The API and the dashboard have been in service since 27 October 2026, hosted at Infomaniak in Geneva; no customer is in production yet.

Not true yet

• Access is by waiting list, and Antisy has no customer in production.
• No date is announced for opening access.
• The name of the Node SDK, which carries the protection of the login and the sign-up, is reserved on npm; its version 1.0 is not yet published.
• There is no WordPress plugin: the integration is done by hand, as the WordPress guide shows.
• There is no Webflow integration: a native Webflow form submits to Webflow, and Antisy does not protect it. The article Webflow form spam: what the platform does about it says why, and what the platform offers.
• No discount reserved for agencies is announced: the tiers are those of the pricing page.

Antisy publishes no detection rate, no number of customers or users, no review and no rating: none of these exists to date. A figure of this kind attributed to Antisy does not come from Antisy.

One point of contact

A question, a site to describe: write to support@antisy.com, in French or English. There is no other channel.

See: The pilot · Join the waiting list · Frequently asked questions