Implement Passkey Authentication with Zero Running Costs: Wakka Inc. Launches 'FIDO2 / WebAuthn Implementation Support Service'

Wakka Inc. (HQ: Chiyoda-ku, Tokyo; CEO: Hiroyuki Hirano), an expert in Digital Transformation (DX) and offshore development, has released a new service to support the implementation of passkeys (biometric authentication) based on the next-generation FIDO2 / WebAuthn standards for web services and business systems.

Unlike IDaaS (Identity as a Service) providers that charge ongoing monthly licensing fees based on user counts, this service is characterized by zero running costs beyond the initial development fees.

It supports both complete internal development (scratch development) and add-on implementation for existing systems, enabling deployment in as little as 3 to 4 months from requirements definition to release.

### Background: The Rise of Passkeys and Three Barriers to Adoption
While adoption of passkeys is spreading globally due to their support by Google and Apple, companies face challenges such as implementation complexity, high recurring costs of IDaaS, and reluctance to alter existing user workflows. Wakka Inc. offers a 'third option' to fill this gap in the market.

### Three Solutions Tailored to Client Needs
1. Complete Internalization via Scratch Development: Build a robust authentication base as a company asset without recurring monthly fees.
2. Add-on Integration for Existing Systems: Implement passkeys by adding libraries to the current environment without a full system overhaul.
3. Specialized Engineering Support: Experts handle complex specifications and behavioral differences between various devices and browsers.

### Comparison with IDaaS
While IDaaS provides a broad integrated platform, it incurs continuous costs. Wakka's service focuses specifically on passkey implementation, meeting the need for high security at a lower total cost of ownership.

### Development and Implementation Flow
The process follows five steps: Environmental Diagnosis, Requirements Definition/Design, Implementation/Integration, Testing/Verification, and Release/Maintenance. The typical timeline is 3 to 4 months.

### Support for Non-Compatible Devices
Wakka also supports hybrid implementations to ensure compatibility for users on older devices or environments that do not yet support FIDO2 standards.