Login friction at global scale
A global trading platform needed modern login with less friction while staying strong on security for regulated traffic.
Case Study / Identity at Scale
Passkeys & Social Login — Deriv
NestJS authentication services for Passkeys / WebAuthn patterns and social login on a global trading platform.
← All case studies
The challenge
Find the real problem.
Modern login had to meet enterprise traffic and security expectations.
Deriv needed identity infrastructure that reduced friction without weakening security for regulated, high-volume traffic.
The delivery path was NestJS services with Passkeys-class patterns, social login, and production API boundaries product teams could depend on.
Legacy auth paths were limiting
Password-centric flows and fragmented social login made product teams slower to improve the identity experience.
Passkeys needed production boundaries
WebAuthn / Passkeys patterns had to ship as real NestJS services with clear API contracts, not a prototype.
Identity is daily critical infrastructure
Auth failures block every product surface, so delivery had to be reliable for teams that depend on login every day.
What we built
Connect the pieces.
NestJS auth services for Passkeys and social login at Deriv.
At Deriv, we built NestJS authentication services covering Passkeys / WebAuthn patterns, social login, and production API boundaries for a global trading platform.
The result is enterprise identity infrastructure product teams rely on daily — already named on the public Upwork portfolio.
Passkeys / WebAuthn patterns
Implemented Passkeys-class authentication flows so users can authenticate with modern, phishing-resistant patterns.
Social login services
Integrated social login paths behind NestJS services with consistent API boundaries for product teams.
Production NestJS identity APIs
Structured auth services for maintainability, clear contracts, and the traffic profile of a global platform.
Security-minded delivery
Kept identity work aligned with regulated traffic expectations: explicit boundaries, careful rollout, and operational clarity.
What we learned
Better with every build.
Identity work succeeds when it is treated as platform infrastructure.
Passkeys and social login only matter when they ship as owned services with clear contracts. This case study uses the Deriv naming already public on the Upwork portfolio.
Auth is a product surface
Login friction shows up as churn and support load long before it shows up as an engineering ticket.
Passkeys and social login only help when they are production services, not demos.
NestJS fits identity systems
Modular NestJS services keep OAuth, Passkeys, and social paths maintainable as requirements grow.
Clear modules beat a single auth monolith for long-lived platforms.
Scale changes the design bar
Global trading traffic forces explicit API boundaries and careful failure modes.
Enterprise identity work is infrastructure, not a feature toggle.
Outcomes
A stronger foundation.
Enterprise identity infrastructure for Passkeys and social login that product teams rely on daily.
NestJS auth services with production API boundaries suited to global trading traffic.
Start a project
Ready to build the platform
your team runs on?
Tell us where work is stalling — a portal, backend, marketplace, staffing system, an AI layer, or cloud ops.
In 30 minutes we’ll map the highest-leverage build first.