Launch Video Library · Devtools · Launch · 2026

WorkOS Passport Launch

WorkOS introduced Passport to eliminate single sign-on friction and Airlock for enterprise-managed authorization on MCP servers.

What WorkOS shipped

WorkOS introduced Passport to eliminate single sign-on friction entirely, alongside Airlock for enterprise-managed authorization on MCP servers. Unveiled during the init() 2026 event, the presentation targets the cumulative hours engineering and product teams lose to repetitive authentication.

Moving beyond traditional SSO, Passport registers the device itself—in this case, a Mac—to handle authentication seamlessly in the background. The addition of Airlock extends this access model to AI agents, allowing tools like Claude to securely query connected integrations including GitHub, Snowflake, and Datadog.

How the motion works

When structuring a technical walkthrough like the Passport device enrollment, pacing dictates engagement. Relying on a sharp hard-cut to bypass loading screens or progress bars keeps the viewer anchored to the actual user input. Moving from the initial problem statement directly into the Mac registration interface without transitional fluff maintains the demo's momentum.

Demonstrating a 'zero-click' automatic sign-in feature presents a unique visual challenge: the primary selling point is an absence of friction. A deliberate punch-in on the configuration toggle—comparing the disabled and enabled states—can direct the eye precisely to the functional change. This technique ensures the audience registers the underlying mechanics before watching the seamless Notion login.

For the Airlock segment featuring Claude, managing hold-time is the primary variable. As the AI queries backend integrations like GitHub, Linear, and Datadog, holding the frame just long enough for the viewer to parse the generated output balances comprehension against the overall run time. Treating text generation as a visual element requires strict timing to prevent the demo from dragging.

What to steal from it

  • Use a hard-cut to remove loading states and keep technical walkthroughs strictly focused on user actions.
  • Employ a subtle punch-in to draw attention to small UI changes, especially when demonstrating automated or invisible background processes.
  • Manage hold-time carefully when showing AI-generated text, ensuring viewers can read the output without slowing the overall demo pace.
  • Contrast the 'before' and 'after' states explicitly in the UI to make invisible features like automatic sign-in feel tangible.

Want a video like this for your product?

Impractical cuts one from a single prompt — the same motion craft, in about twenty minutes.