Auth Gateway
Labelbox · Sr. Web Engineer and Designer
Secure demos without Auth0 tickets
Overview
Every new internal demo with customer data used to mean IT time on granular Auth0 permissions — and many FDEs don’t live in Auth0 day to day. Auth Gateway removes that bottleneck: register a domain in lbx-auth, install the npm package, and get a secured path into demos. It also backs customer products like Evals so security is part of the default workflow, not a ticket queue.
Context
Customer-data demos stalled on IT Auth0 permissions. FDEs needed a default secure path, not a ticket per app.
How it evolved
lbx-auth domain registration plus a private npm package — install once, gate demos consistently with RBAC/JWT/OAuth behind a shared SDK.
Where it is now
Default for internal products and customer-gated Evals when environments need customer data quickly.
What it delivered
Self-serve domain registration + npm install replaces repeated Auth0 permission tickets for each new app
Built for FDE velocity — secure demos with customer data without needing deep Auth0 expertise
Adopted across internal products and customer-gated Evals
How it ships
Wrapped Auth0/RBAC/JWT/OAuth behind a private package so teams share one auth path instead of copying config
lbx-auth registration keeps domain allowlisting explicit while the install experience stays simple
Unblocks demo and POC shipping when GTM and FDEs need customer-facing environments quickly
Surfaces
lbx-auth · private npm package · internal products · Evals
Stack
Team
Platform ownership; consumed by FDEs and internal product teams