Pricing says 'call us'. That is a huge bummer. Basically means I won't invest the time to use this. Keep in mind I'm already an auth0 customer.
You might have seen Graphcool's launch yesterday where they announced 'inline functions'. Graphcool is running its users' code on their behalf right in the hot code path of their mutation pipeline. This means they're able to run untrusted code in an isolated and low-latency manner and at scale.<p>You may have seen something similar before in Auth0 Rules [1]. That the two share similarities is no coincidence! Auth0 Rules and Graphcool's 'inline functions' use the same Webtask technology behind the scenes.<p>We packaged up this technology to provide the first and only 'Extensibility as a Service' offering called Auth0 Extend [2]. Auth0 Extend builds on the familiar webhook model but removes the friction webhooks impose on user; no more standing up and managing servers just to handle webhook invocations. Auth0 Extend makes it trivial to transform a platform's webhook integration into an in-platform custom code editing experience.<p>1: <a href="https://auth0.com/docs/rules" rel="nofollow">https://auth0.com/docs/rules</a>
2: <a href="https://auth0.com/extend" rel="nofollow">https://auth0.com/extend</a>
So... a business model around signed mobile code..? Neat, but I have many questions regarding safety: confinement, isolation, termination, resource management, etc. Shunting code around is the easy part... it's preventing code from doing bad/dangerous things that's hard. Need more info.
Can someone explain to me in simple term. What kind of thing is this Auth0 extend, and why would i need this compared to service like heroku, zeit now, or something else?
Why do I see callbacks for completion instead of Promises in 2017? Promises are included in ES6 spec [0].<p>[0]: <a href="https://www.ecma-international.org/ecma-262/6.0/#sec-promise-constructor" rel="nofollow">https://www.ecma-international.org/ecma-262/6.0/#sec-promise...</a>