Skip to content
All stories
LogisticsPassport.js'ten

How Northwind Trading retired its own auth stack in six weeks

A freight platform with 240 enterprise accounts moved off a hand-rolled Passport.js setup without a flag day.

Illustrative example

Northwind Trading is a composite example, not a named customer. The situation and the way it was solved are drawn from what teams actually bring to us; the company itself is invented. Real customer stories are published only with the customer’s permission and their own name on them.

6 weeks
end to end
240
enterprise accounts migrated
0
forced password resets

The situation

Passport.js had carried them from launch to their first hundred customers. It stopped scaling the moment enterprise buyers started asking for their own identity provider: every new connection meant a strategy, a config branch and a deploy.

What they did

They imported existing accounts with their original identifiers preserved, then ran both sign-in paths in parallel for a month. New sessions went through Paycux; old ones expired naturally.

What changed

Connection setup moved from an engineering ticket to a link the customer's IT administrator opens themselves. The auth strategy directory is gone.

Add SSO, the easy way

Everything in this story is something the platform already does. Start with the quickstart and have a working sign-in this afternoon.

What’s your enterprise story?

Tell us what the checklist is costing your team and we will give you a straight answer on fit.