GrayPass

GrayPass adds a “fresh assurance” check right before your application performs sensitive actions. It first uses your existing login to establish who entered, then checks whether the expected person is still in control as session evidence ages.

It’s a fit when you already have identity controls (login, passkeys, MFA) but still need a second opinion for high-risk operations like changing payout details. GrayPass is designed to help you make a policy-based decision and enforce it in your app.

• Continued control check before a protected action executes, not only at sign-in
• Action-bound authorization so proof is tied to the exact action your app is about to run
• Identity plus context using your identity provider and information about device, session, and transaction context
• Brainprint continuity based on interaction timing (pointer movement, click timing, keystroke timing, scrolling pace) without capturing what people type
• Policy-driven outcomes that your application can enforce as allow, verify again, hold, or deny

GrayPass focuses on continuity evidence. A “Brainprint” is a privacy-preserving, tenant-scoped representation of someone’s interaction rhythm, enrolled during onboarding and later compared to new evidence from timing and movement patterns. It’s not intended to establish identity or permission by itself, and it doesn’t capture typed words.