No. SoleyCue does not replace authentication or MFA. It provides an optional protection signal that operates alongside existing identity and access infrastructure in rare situations that fall outside the assurances provided by standard authentication and recovery flows.
Traditional knowledge factors rely on static, reusable secrets. SoleyCue verifies human recognition rather than memorized answers—there is no single secret to steal, reuse, or enumerate.
No. SoleyCue does not store reusable credentials or secrets. Each verification is contextual, non-rehearsed, and evaluated at the moment it's needed.
SoleyCue operates alongside existing identity and access infrastructure. It provides an optional protection signal that can be invoked by applications or access gateways after authentication is complete or when additional assurance is required, without changing passwords, MFA providers, or SSO.
SoleyCue adds a human-recognition signal for situations where authentication is successful, but additional protection is required before access is granted.
Yes. SoleyCue operates alongside existing identity and access infrastructure, including hybrid and on-prem deployments.
It does not replace identity providers or require moving identity systems to the cloud. SoleyCue provides an optional verification signal that can be invoked by applications or access gateways wherever access decisions are made.
SoleyCue is not designed to replace existing login or recovery mechanisms. It provides an additional, optional protection signal for scenarios that fall outside the assurances provided by traditional recovery paths, or where those paths require manual intervention.
These include scenarios such as lost devices, compromised inboxes, or high-value access. In these edge cases, applications already invest in custom handling. SoleyCue is intended to reduce friction and risk in those moments, not change everyday authentication.
Prologue is a mode of SoleyCue used to determine eligibility before account creation or authentication occurs, for systems where access should not be open by default.
When enforced server-side, Prologue cannot be bypassed by direct URLs or SSO alone. Eligibility must be verified before protected endpoints are exposed.
Email and SMS recovery paths provide convenience but rely on channels that are frequently targeted by attackers. SoleyCue complements these mechanisms by adding a protection signal that does not rely on interceptable channels, reusable secrets, or automated verification paths.
SoleyCue is adopted incrementally alongside existing identity and access infrastructure—starting with individual applications and security teams, then expanding naturally through the identity platforms they already use.
No. SoleyCue operates alongside existing web and identity infrastructure and does not require new hardware, operating system changes, or standards adoption.
If SoleyCue's protection signal is not satisfied, access does not proceed. No additional information is exposed, and the system does not automatically fall back to weaker recovery or verification paths.
SoleyCue is designed to minimize sensitive data exposure.
It does not store passwords, verification answers, memories, or biometric templates. Meaning is never transmitted or persisted — it exists only in the user's mind.
If SoleyCue were ever compromised, the stored data would not be sufficient to infer or replay verification, and existing authentication systems would continue to function normally. SoleyCue operates as an assistive signal, not a single point of failure.
SoleyCue is designed to strengthen the weakest moments in access control—without disrupting the systems that already work.