SpruceID

SpruceID is identity infrastructure for government and public-service programmes. It connects a shared sign-in layer with portable digital credentials, so agencies can reuse trusted information across services without turning the product into a consumer proof-of-personhood network.

Credentials separate an attestation from service access

An authorised issuer can create a digital identity document, licence or qualification; the resident holds it in a credential wallet and presents it to a verifier. The credential carries the specific attestation, while the account or identifier used to enter a service is the access mechanism around it.

This issuer-holder-verifier flow can avoid repeating the same identity check at every agency, but the receiving agency still decides which issuers, credential formats, assurance levels and risk signals it accepts. A compatible credential does not itself grant a benefit, licence or other entitlement.

Identity Gateway joins existing services behind one login

Identity Gateway sits in front of applications such as DMV, benefits, licensing and permitting systems. It can provide shared authentication with MFA, device binding and standards-based protocols while connecting legacy applications and newer cross-agency workflows.

That reduces separate accounts and recovery journeys, not each programme’s own eligibility rules. The published material does not establish one universal recovery model or an automatic portability promise for every agency implementation.

Standards and integration are the main decision boundary

SpruceID’s model spans mobile-document standards, Verifiable Credentials and OpenID credential and presentation flows. Its practical fit depends on whether issuers, holder wallets and relying systems implement the credential and exchange standards required for the intended programme.

World is the useful contrast when an application needs an anonymous proof that someone is unique, live, or holds a supported document. SpruceID is oriented instead to interoperable government credentials, unified access and agency-system integration; its core mechanics do not require a chain-specific issuer or onchain verifier.