Serverless extensibility allows third-party code to be securely executed within a Software as a Service (SaaS) product using serverless functions. This provides benefits over traditional webhooks by handling hosting and monitoring, and allowing custom code to be created and run directly within the SaaS product using an inline code editor. Serverless extensibility benefits both customers by lowering costs and barriers to customization, and SaaS providers by improving customer retention and enabling new integration possibilities. However, concerns remain around ensuring custom code is properly versioned, debugged and secured to prevent issues like vendor lock-in.

1. Serverless Extensibility
from Within
Glenn Block, Auth0 Extend (@gblock)
glenn.block@auth0.com

2. 1990s – 2000s: Extensibility was easier
when it was your servers
https://www.flickr.com/photos/darkseed/41932055

4. 2006: Cloud and SaaS changed everything
(and brought new challenges)
https://www.azernews.az/media/pictures/data_center_150614.jpg

5. 2007: Webhooks revolutionized the web
"The idea here is to create new
infrastructure. New opportunities. I've
been thinking a lot about the
possibilities of a web hook enabled
web, and it makes me really excited."
Jeff Lindsey

6.  The SaaS doesn't have to build the customizations
 The doesn't have to host them
 Code runs completely isolated and secure from the SaaS and from other
customers
 Customers can choose any language / stack to implement
 Relatively straightforward to implement*
SaaS
Webhook
Endpoint
Webhook invocation
Webhooks revolutionized Saas Extensibility
Continue
Asynchronously

9. Webhooks also brought pain….to the customer
 The customer has to build it. A Webhook is
a service.
 The customer has to host it
 The customer has to run and monitor it
 The customer has to pay for it

10. 2015: Serverless
https://www.flickr.com/photos/jeepersmedia/13943819389

11.  The customer still has to build it, but Webhooks are much easier to implement
 The Serverless provider is the host
 The customer has to monitor it
 The customer has to pay for it
SaaS
Serverless
Provider
Webhook invocation
Serverless functions are
an evolution for Webhooks
Continue
Asynchronously

12. But for SaaS extensibility,
the costs still inhibit their usage

13. 2017 - Serverless Extensibility, The next frontier

14. Serverless Extensibility, extensibility from within
Serverless Extensibility
A SaaS product directly invokes a Serverless
platform to handle runtime execution of 3rd party
extensions

15. Serverless Extensibility
SaaS
Serverless
Provider
Webhook invocation
Synch or Asynchronous
In product
Code Editor
SaaS Product

16. Serverless Extensibility
 Hook points within the product for extensibility
 An in-line code editor for creating extensions
 Templates for common extensions
 A Serverless runtime for securely executing 3rd
party code

17. Twilio

18. Auth0

19. Stamplay

20. http://www.plexure.com/plexure-blog/2017/6/1/going-
serverless-on-azure
Plexure

21. https://auth0.com/extend

22. Serverless Extensibility
Customer Benefits
Quicker ramp up.
More approachable / does not need to be a traditional developer
No need to worry about hosting or signing up for a separate account
The SaaS handles monitoring
They pay little to nothing

23. Serverless Extensibility
SaaS Benefits
All the benefits of Webhooks
Experience can be more tailored to the needs of the customer
Higher retention / stickier customers
Can even enable sales engineers / help closing deals
Greater support visibility

24. Serverless Extensibility
Concerns
Not every customer wants to code
Lack of visibility, code getting scattered (lost), "Dude, where's my
function?"
Versioning
Debugging
Security
Vendor lock-in

25.  Serverless Extensibility: https://auth0.com/blog/why-is-serverless-
extensibility-better-than-webhooks
 Auth0 Extend:https://auth0.com/extend
 ZERO CRM:https://github.com/auth0/extend
 Twilio functions: https://www.twilio.com/functions
 Stamplay: https://codeblocks.stamplayapp.com
 Plexure: http://www.plexure.com
Where to learn more

26. Thanks!
Glenn Block, Auth0 Extend (@gblock)
glenn.block@auth0.com