The FriendlyCaptcha Alternative. Hardware-level and truly invisible.

Friendly Captcha vs TrustSig, side by side

Both are EU-hosted and cookieless. The difference is the detection model and how much of it runs on the visitor's machine.

TrustSig asks the visitor's device for nothing

Friendly Captcha is a solid EU choice, so the move is usually about the widget and the compute.

Swap Friendly Captcha for TrustSig

Remove the widget mount and its verify call, then add the scan and one verify call. Two npm packages, no infrastructure changes.

1. 01
   Frontend: remove the widget mount

   // Before: Friendly Captcha widget
   // <div className="frc-captcha" data-sitekey={SITE_KEY} />
   
   // After: TrustSig (no element, nothing computed in the browser)
   import { useTrustSig } from "@trustsig/react"
   
   function ActionForm() {
     const { getResponse } = useTrustSig()
   
     const handleSubmit = async () => {
       const response = await getResponse()
       await fetch("/api/action", {
         headers: { "X-TrustSig-Response": response?.token || "" },
       })
     }
   }

2. 02
   Backend: replace the verify call

   // Before: Friendly Captcha (network round-trip)
   // await fetch("https://api.friendlycaptcha.com/api/v1/siteverify", ...)
   
   // After: TrustSig (one verify call at the edge)
   import { TrustSig } from "@trustsig/server"
   
   const ts = new TrustSig({ secretKey: process.env.TRUSTSIG_SECRET_KEY })
   
   app.post("/api/action", async (req, res) => {
     const token = req.headers["x-trustsig-response"]
   
     const result = await ts.verifyRemote(token)
   
     if (result.action !== "ALLOW")
       return res.status(403).json({ error: "Blocked" })
   })

Friendly Captcha migration questions