Create account
Menu

MIGRATE FROM RECAPTCHA

Keep the server verification boundary. Replace the provider contract.

Choose the GIWS version that matches the interaction you use today, issue new GIWS credentials, and run both integrations separately during rollout.

Create your workspace Open migration guide
03 core areas 01Map the experience02Replace both boundaries03Roll out safely

Migration pathway

Map the experience

Use V1 for an explicit challenge, V2 for checkbox or invisible managed verification, and V3 for action-based scoring.

  • Challenge → V1
  • Checkbox or invisible → V2
  • Score action → V3

Migration pathway

Replace both boundaries

Change the browser loader and the backend verification endpoint together. Provider keys and response fields are not interchangeable.

  • Issue new site credentials
  • Keep secrets server-side
  • Validate hostname and action

Migration pathway

Roll out safely

Test on a staging hostname, monitor stable error codes, and remove the previous integration only after backend enforcement is confirmed.

  • Separate staging site
  • No shared tokens
  • Explicit rollback point

CONTINUE EXPLORING

Follow the most relevant path without losing the context of this page.

01

From Turnstile

Recalibrate managed outcomes.

 02

From hCaptcha

Preserve accessible completion.

START WITH A REAL SITE

Build a safer user journey.

Register a hostname and choose the amount of verification friction each action deserves.

Create account