Auth0 Marketplace.
Auth0's extensibility used to be a pile of internally-managed one-offs. I led the technical strategy and execution that turned it into a centralized, partner-driven Marketplace on an API-first architecture—and grew the catalog from roughly twenty integrations to several hundred.
From internal one-offs to a self-service ecosystem.
- Fragmented, internally-managed extensions
- Disparate mechanisms per integration
- No partner self-service
- ~20 catalog entries
- Extensibility was a story, not a platform
- One centralized, partner-driven Marketplace
- API-first architecture across every entity
- Templates & recipes for fast partner onboarding
- Open-source integration repositories
- Hundreds of integrations, discoverable in-product
Model the marketplace as first-class entities.
Every one of these became a first-class, API-first entity—built in Go, Node.js, and React over MongoDB and PostgreSQL, with Kafka moving events and gRPC/Fastify wiring services together. Partners stopped filing tickets and started shipping.
Grew the integrations catalog from roughly twenty entries to several hundred, improving partner adoption and in-product discoverability.
Introduced templates and pre-built recipes that accelerated partner adoption of Auth0 Actions within authentication flows.
Architected support for open-source integration repositories so partners could build, maintain, and evolve integrations in the open.
Influenced cross-functional investment in the Actions/Webtask runtime, unlocking Flexible User Journeys and complex identity verification.
// Catalog growth (~20 → hundreds) is the number I'll stand behind publicly; other adoption figures live inside Auth0.