Upbond

• If procurement requires a widely reviewed CIAM platform with substantial presence on Gartner Peer Insights / G2 / TrustRadius, the limited public review footprint for Upbond is a concern.
• If modeling cost early is essential (detailed MAU-based pricing, auth request pricing), vendors with published pricing (e.g., Auth0, Okta) may be preferable.
• If strict compliance artifacts are required out-of-the-box (SOC 2 Type II, ISO 27018, PCI, HIPAA, public pen-test disclosures, and a mature trust center), consider vendors that publish or readily provide those artifacts.
• If the project is a standard CIAM implementation without a need for embedded wallet/Web3 features, a specialized CIAM vendor may provide a faster path to production.
• If the deployment is outside Japan and requires a broad local integrator/support ecosystem, the available signals for Upbond indicate a Japan-heavy ecosystem.

• Limited third-party customer reviews on major B2B review platforms (G2, TrustRadius, Capterra) in accessible search results.
• Pricing opacity: no clear public tiering was discovered.
• Limited public security artifacts beyond an ISMS announcement and a general security policy; pen-test summaries, SOC reports, and trust-center materials are not publicly available.
• Potential inconsistencies in public materials (for example, leadership name variants and wording around certification standards).

• The vendor frames Login3.0 around DID/VC concepts for cross-service identity issuance and consent management.
• The vendor states that personal information is not written to public blockchains, and that Web3 is used primarily to issue DIDs.
• The UPBOND Wallet SDK is positioned as an embedded, non-custodial wallet aimed at simplifying wallet creation and onboarding.
• Documentation describes a Shamir Secret Sharing (2-of-3) design for key handling.

Sources: Login3.0 page; UPBOND Wallet landing page; Upbond GitBook documentation.

Searches did not surface credible G2, TrustRadius, or Capterra product review pages for Upbond. Similarly, no clear Gartner Peer Insights product listing for Upbond was located in accessible results. As a result, peer-review data is limited.

Consequently, customer sentiment assessment relies on:

• Public partner press releases (vendor- or partner-controlled)
• Technical documentation and vendor statements
• Limited third-party listings (small, non-mainstream product listings)
• Automated site trust checks rather than user reviews

This limited third-party review footprint is a risk signal for procurement processes that rely on validated peer reviews.

• Login3.0 FAQ (vendor-controlled): "The web3.0 technology is only used to issue user IDs (DIDs), so no personal information is exposed to the blockchain."
• Cosmos Initia release (partner PR): describes Login3.0 as enabling users to manage and control where their data is shared and to manage visibility of shared data.
• An automated site trust check: indicates the vendor's wallet subdomain has a moderate trust score and notes factors such as hidden WHOIS and low traffic.

Sources: Official vendor documentation and product pages; Partner press releases; Automated site trust check report.

• Cosmos Initia describes a PoC (passport pre-registration and baggage delivery) at two MIMARU facilities from September–November 2024 using Login3.0.
• The partner-reported metric shows baggage delivery usage increased substantially compared to other facilities during the experiment.
• Daiwa House Group announced a "MIMARU My Page" using Login3.0 began operation January 14, 2026.

Critical evaluation:

• The reported uplift is partner-published and likely context-specific; methodology details (control matching, seasonality, sample size) are not provided.
• The deployment indicates movement from PoC to an operational service in at least one partner deployment.

Sources: Partner press release; Partner company release (official announcements)

Upbond (UPBOND Corporation, Japan) provides Web3-adjacent identity and wallet infrastructure designed to support consumer-facing businesses in unifying logins/IDs across services, managing user consent, and (in some implementations) connecting user-held data ("lifelogs") with company-held data. Its two most visible product lines are:

• Login3.0: a personal/individual-sovereign login infrastructure that uses DID/VC concepts to issue an ID consistently across multiple services, enabling single sign-on (SSO), consent management, and integration with enterprise systems. The vendor states Web3 technology is used only for issuing DIDs and that personal information is not exposed on-chain.
• UPBOND Wallet: a browser-based, non-custodial wallet/embedded-wallet style SDK intended to reduce user drop-off during wallet creation and onboarding. Implementation is via a JavaScript SDK (npm); the vendor documentation describes a Shamir Secret Sharing approach for key handling.

Sources: Official vendor product pages and documentation; product FAQ and developer documentation.

Upbond’s messaging covers:

• B2C / consumer services that require first-party identity, cross-service SSO, and consent handling in the context of cookie deprecation.
• Web3 adoption and embedded wallet experiences (e.g., NFT membership cards, travel/loyalty experiences), with an emphasis on abstracting Web3 complexity from end users.
• Japan-based enterprises and partners building proofs-of-concept (PoCs) and production deployments (examples include hospitality/travel and media).

Available evidence indicates Upbond has stronger traction in Japan based on partnerships and co-development announcements.

Sources: Vendor product pages and corporate marketing materials; press releases from partner engagements.