Official Next.js SDK

Protection that fits your application.

With @truesift/next you integrate a clear verification interface in the browser while keeping the authoritative decision where it belongs: on your server.

01

Browser

TrueSiftCheck creates the short-lived verification token and returns it to your form.

02

Local routes

Challenge and Verify remain in your Next.js application. The Secret Key stays server-side.

03

Business Route

Only verificationToken comes from the client. Action, Path and Origin are defined by your server.

Real SDK demo

The real component. Not a mock-up.

This preview renders TrueSiftCheck directly from @truesift/next/client. The scenarios run through the local demo routes from the SDK example and show the actual widget lifecycle.

State simulatorAllow

Successful human verification.

Scenario
Theme
Language

Checkbox · Compact

Recommended visual direction for forms.

TrueSiftSecurity check is ready.Privacy-first verification

Checkbox · Normal

Default npm-like fallback behaviour.

TrueSiftSecurity check is ready.Privacy-first verification

Banner · Flexible

Legacy / marketing mode, still available when needed.

TrueSiftSecurity check is ready.Privacy-first verification

Checkbox · Compact · Light card

Checks how the active theme behaves inside a light card.

TrueSiftSecurity check is ready.Privacy-first verification

Latest verification callbacks

No verification callbacks yet.

Security principle

The interface is not proof.

Decisions such as allow, review or block are never accepted from browser data. The protected business route verifies the token server-side against the expected Action, Path and Origin — only then does it execute the action.