andres

I’ve been at Auth0 since 2017. I’m currently working as a Product Manager for the Auth0 FGA and OpenFGA products. Previously, I worked in the teams that owned the Login and MFA flows. 
I spent my entire 20+ year career building tools for developers, wearing different hats. When I'm not doing that, I enjoy spending time with my family, singing in a choir, cooking, or trying new kinds of local cheese.

Product Manager

Andrés Aguiar

Auth0 FGA achieves unprecedented scalability, paving the way for global authorization systems.

We believe that [Auth0 Fine Grained Authorization](https://fga.dev) (FGA) will fundamentally change how applications are going to be built over the next decade. At Okta, we aim to solve authorization for both application builders and workforce IT administrators, and FGA is a key piece of that strategy.

Scalability is crucial when designing a global-scale authorization system. It must be capable of delivering the performance and capacity expected from top-tier cloud services, like modern distributed databases. An authorization system capable of supporting a global scale must:

- Be highly available,
- Scale to support the most visited websites in the world,
- Provide low latency, as every millisecond you spend in authorization will impact the application’s overall latency,
- Be able to store a very large amount of data.

This [Google Zanzibar](https://research.google/pubs/pub48190/) paper describes how Google achieves those goals. We built FGA with these goals in mind, and our early tests of the Auth0 FGA validated that it could handle anything our beta and early access customers could throw at it.

As FGA gained traction among customers, we realized that we needed to push FGA even further to prove out this scale. 

So, we decided to run a test with **1 million Requests per Second (RPS)** and **100 billion relationship tuples** to evaluate how the system behaves. 

## Auth0 FGA Primer : Model + Relationship Tuples

When implementing authorization using Auth0 FGA, you need to define an authorization model that describes the different entities in your system that are relevant when making authorization decisions and provide the data required to instantiate the model in the form of relationship tuples.

For example, in the model below, we define groups that can contain users, documents that can have an owner, and viewers that can point to specific users or all members of a specific group:

```yaml
type user
type group
 relations
 define member : [user]

type document
 relations

 define owner : [user]
 define viewer : [user, group#member]
```

Relationship tuples would look like:

| user | relation | object |
| ---------------------- | -------- | ------------------- |
| user:anne | member | group:marketing |
| user:peter | owner | document:sales-plan |
| group:marketing#member | viewer | document:sales-plan |

FGA defines an API method called `Check()` that will let you ask the system if a user is related to an object in a specific way. 

For example, we can call `Check(user:anne, viewer, document:sales-plan)` and we’ll get `“{ allowed: true }”` as a result, given `anne` is a member of the `marketing` group, and their members are related to the `sales-plan` document as viewers.

If you want to learn more, check out how to model with Auth0 FGA [here](https://docs.fga.dev/modeling).

## Modeling Authorization

When using FGA, the performance characteristics of a specific implementation will depend on the authorization model and relationship tuples in the system. 

The flexibility of FGA means that customers with varying use cases, traffic, and business models are able to harness the full power of FGA. In initial implementations, we’ve seen that customers with a Business-to-Business (B2B) use case tend to have more complex models but with far fewer active users and less traffic. And we’ve seen that customers with a Business-to-Consumer (B2C) use case tend to have less complex requirements but with more data, active users, and traffic. We decided to target these B2C use cases for our performance testing since these are the businesses that are more likely to require a scale of 1 million RPS and 100 billion tuples.

We modeled a social network where users can post content and other users can interact with it. One example of this would be publishing a tweet and commenting on it. The model is described below:

```yaml
type user
 relations
 # Users can have followers, can block specific users, 
 # and can decide if they are visible to all users or just to their followers
 define _self: [user]
 define follower: [user]
 define blocked: [user]
 define visibility: [user:*, user#follower]
 define viewer: visibility but not blocked
 # User profiles can be viewed by the user itself or by the users who have access to their profile
 define can_view: _self or viewer

type content
 relations 
 # Content is owned by the user that published it
 define owner: [user]

 # The content can be visible for anyone or just their followers, for users that are not blocked, and by the owner itself
 define visibility: [user:*, user#follower]
 define viewer: visibility but not blocked from the owner
 define can_view: owner or viewer

type interaction
 relations
 # Content iterations (e.g., comments) have a creator and a content piece as their parent
 define creator: [user]
 define parent: [content]
 # interactions can be viewed if the user can view the creator's profile and the content itself or if they are the creator of the interaction
 define viewer: can_view from creator and can_view from parent
 define can_view: creator or viewer
```

After defining the model, we had to decide how to distribute the relationship tuples in the system. We decided to use a [Pareto distribution](https://en.wikipedia.org/wiki/Pareto_distribution) where:

- 20% of users are generating 80% of content, and 80% of users are generating 20% of content
- Similarly, 20% of users are doing 80% of the interaction, and 80% of users are doing 20% of the interaction

The tests focused on the `Check()` endpoint because this endpoint is the one that will be called more often and have the most impact on the customer's applications. We checked if a user is able to view specific content, a specific user profile, or a specific interaction (e.g., `Check(user:john, can_view, interaction:1)` ).

## Modeling User Activity

Another critical decision point on how to perform the test was how to model user activity.

FGA has a cache that is set to 10 seconds. If we decide that a very small set of users is going to be active, we’d be able to serve all the requests from the cache. That would make it very easy to misrepresent the test results, as serving everything from memory would only happen in very specific use cases and won’t take into consideration the execution paths that require database access. 

We decided to run the tests in three ways:

- Disabling the caches
- With a 50% cache ratio, which seems realistic based on what we observed as an average ratio across all of our customers.
- With a 75% cache ratio, assuming that for a specific customer, ratios can be higher.

## One Million RPS and Beyond

We were very happy with the results and achieved the outcome we hoped for with only minor tweaks to the product.

We allocated three weeks to complete it, and most of the time was spent on generating the dataset, importing them into the database, and making sure we could launch all the clients that called FGA API. 

We completed the test run in just two days without any significant adjustments in our code. 

The tests ran for over 10 minutes and got 1.05M RPS. The images below are from our DataDog dashboard when we ran the tests with 0% cache ratio:

![Request rate received in FGA performance test](https://images.ctfassets.net/23aumh6u8s0i/2aWUERQeZCzKOa7FZUHB3O/cbd911fbacf051c2683221b78e032ca2/fga-rps-performance.png)

![Latency in FGA performance test](https://images.ctfassets.net/23aumh6u8s0i/D14o99yPNCvvNpFlDMDk9/c11f56a116346ee36e0980b48157eed4/fga-latency-performance.png)

The metrics above show that 50% of the calls were completed in up to 11.9 ms, 95% were completed in less than 19.5 ms, and 99% of them were completed in less than 38.5 ms.

We incrementally increased the load while executing the test, and we saw the number of FGA instances increase linearly, maintaining the latency within the same range. We felt confident that we could go way beyond 1M RPS, but we had to stop somewhere 🙂.

When running the tests with caching, the latency decreased significantly, and the number of Auth0 FGA nodes running too:

<style>
 table {
 width: 100%;
 border-collapse: collapse;
 font-size: 15px;
 }
 table, td, th {
 border: 1px solid;
 }
 table th {
 background-color:#eeeee4;
 }
 td {
 padding: 5px;
 text-align: center;
 }
</style>

| Cache Ratio | RPS per Auth0 FGA Instance (ECS Fargate 16 vCPU 32GB) | P95 Latency |
| ----------- | ---------------------------------------------------- | ----------- |
| 0% | 3,500 | 19.5 ms |
| 50% | 6,000 | 9.4 ms |
| 75% | 18,000 | 5 ms |

## Auth0 FGA and You

We were thrilled to have tangible proof that FGA can support the global scale it was designed for. FGA provides a highly flexible, highly available, and scalable solution to implement authorization, supported by a company that is a trusted leader in the identity space.

You can try Auth0 FGA today by signing up for an evaluation account [here](https://fga.dev). If you want to use it in production, you can apply to our Limited Early Access Program by reaching out to your technical account manager or account executive.

Getting Unlimited Scalability with Auth0 Fine Grained Authorization

shiven_ramji

Shiv is an experienced product executive and builder obsessed with creating beautiful products. He is the President of Customer Identity at Okta, managing a $1B ARR business and overseeing the company’s product, data, security, and technology strategy and execution. Before Auth0 and Okta, Shiv was the SVP of Product at DigitalOcean, leading DigitalOcean’s products, pricing, and partnerships. Additionally, Shiv has held product leadership positions at global brands, including Amazon, NBCUniversal, LiveIntent, and The Nielsen Company. Shiv was the recipient of the 2023 Top Global CPO Award by the Products That Count community. 

Beyond his current corporate focus, Shiv is deeply committed to fostering entrepreneurship and innovation, particularly in Africa. He is an active angel investor and startup advisor and also serves on the boards of [Products That Count](https://productsthatcount.com/) and [Aiven.io](http://Aiven.io).

President, Auth0

Shiven Ramji

Over the last 6 months, Okta has delivered capabilities designed with security, scalability, and resiliency in mind. Read about what we delivered and our future roadmap.

Our teams have been heads down and focused on delivering capabilities that empower our customers to continue to provide seamless customer experiences and power their SaaS ambitions. As we are now halfway through the calendar year, I wanted to reflect on the capabilities we have delivered and give you a glimpse of what's to come next. 

## Unveiling New and Improved Product Features

We strive for innovation and resiliency in our work since we know it translates into direct value for our customers. Over the past six months, our teams have worked across domains to deliver capabilities meticulously designed with security, scalability, and resiliency in mind.

### Flexibility Focus

We continue to double down on improving our customers' ability to build great user experiences within consumer apps. The team has persistently strived to provide a flexible way to build identity flows. In the past few months, we've launched a few enhancements to support this goal further.

* [Passwordless support on New Universal Login](https://auth0.com/docs/authenticate/passwordless/passwordless-with-new-universal-login) allows users to provide an email address or phone number and receive a one-time password (OTP) to complete authentication.
* [Additional email provider support](https://auth0.com/changelog#3yVUYwYINRo7edOw8tP7kG) (Azure Communication Service & Microsoft Modern Auth) enables customers to use Outlook on Microsoft 365 or the recently released Azure Communication Services as preferred authentication methods.

### SaaS Excellence

With a keen eye for enhancing user experiences and elevating customer satisfaction, we continue to make strides that redefine and advance SaaS excellence. To that end, the teams have released several new features:

* [PKCE and attribute mapping are available on OIDC and Okta Workforce Connections](https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/configure-pkce-claim-mapping-for-oidc), allowing customers to build more secure connections between Auth0 and your connected identity provider. With attribute mapping, you can sync more attributes from your IDP into your Auth0 tenant.
* [Improved Login Flow for SaaS Users](https://auth0.com/docs/manage-users/organizations/login-flows-for-organizations) includes options for tying identifier first Home Realm Discovery to Connections with IdP domains associated with Organizations and a New Universal Login Prompt that displays when configured for end users with multiple organization memberships. 
* [Organization Name support for launching Login flows](https://auth0.com/docs/manage-users/organizations/configure-organizations/use-org-name-authentication-api), making Organizations easier to use by enabling the Organization Name to launch login flows via the Authentication API.

### Making Security Easy

At the core of everything we do is the desire to make security seamless and straightforward. Safeguarding data should be uncomplicated yet foolproof. Our latest releases offer protection and make it intuitive, empowering our customers and their users to navigate the digital world without compromise.

* [Security Center is now available on Converged Platform](https://auth0.com/docs/secure/security-center), a new security feature that provides real-time monitoring of potential security events.
* [Bot Detection Slider for Bot Detection](https://auth0.com/docs/secure/attack-protection/bot-detection#use-bot-detection-slider) provides the ability to adjust the level of friction of the "When Risky" setting on our Bot Detection model.
* [Bot Detection is Now Integrated with Friendly Captcha and hCaptcha](https://auth0.com/docs/secure/attack-protection/bot-detection#configure-bot-detection), supporting additional Captcha Providers and their capabilities. 
* [Teams: Security Policies - SSO Enforcement Early Access](https://auth0.com/docs/get-started/tenant-settings/auth0-teams#configure-security-policies), providing the option to mandate login to Teams and Manage Dashboard through the organization's enterprise IdP.

### Developer Experience

Our Developer Experience teams built the following enhancements with intention, care, and a complete developer experience in mind. With streamlined workflows and a suite of tools, developers quickly translate their application experience vision into reality.

* [Node 18 is now available for Actions, Rules, and Hooks](https://auth0.com/changelog#2xzzvhZDXiRbThfc7XsfO). You can start using Node 18 in your tenants' settings and/or when creating new Actions in the Auth0 Manage Dashboard.
* [Auth0 Terraform Provider V1 - BETA](https://auth0.com/changelog#515sGCwZW2u6bD06rzS1uC), with the v1 release, managing your Auth0 resources using Terraform has never been easier. 
* [Auth0 Management API](https://auth0.com/docs/api/management/v2) launched, which includes numerous new features and enhancements for the UI experience.
* [Teams: Security Policies - SSO Enforcement](https://auth0.com/docs/get-started/tenant-settings/auth0-teams#configure-security-policies), allowing you to mandate login to Teams and Manage Dashboard through the organization's enterprise IdP.

### Customer Delight

We obsess over giving customers the complete capabilities to deliver a delightful customer experience. Every interaction and every touchpoint is an opportunity to elevate the customer journey. Our latest achievements stand as a testament to our dedication to not only meeting but exceeding the expectations that define customer delight.

* [Guardian App Localization](https://auth0.com/docs/secure/multi-factor-authentication/auth0-guardian): The Guardian app is available as an authenticator to deliver push notifications to a user's pre-registered device (mobile phone or tablet) and supports English - US (en-us), French - Canada (fr-ca), French - France (fr), Portuguese - Brazil (pt-br), and Spanish - Argentina (es-ar).
* [Universal Login: New Language Support](https://auth0.com/docs/customize/internationalization-and-localization/universal-login-internationalization): Six new languages are now available as supported translations for Universal Login: Basque: eu-ES; Catalan: ca-ES; Galician: gl-ES; Norwegian: no; Norwegian Nynorsk: nn; and Welsh: cy.
* [Custom Domains in Guardian SDKs](https://auth0.com/changelog#7brExNHNLtHshVHvayBm6L), building your users' confidence that they are providing their credentials to the proper party. Custom Domains allow authentication to happen within the context of your brand.

The [Auth0 Changelog](https://auth0.com/changelog) has the full details and documentation on these updates and serves as the real-time release center. 

## Looking Forward to the Next Half

We've made good progress on delivering our roadmap and have steadily released capabilities that help our customers deliver seamless and secure experiences for their customers. 

A big thank you to all of our teams, and looking forward to penning another post full of releases in the next six months. 

[Oktane](https://www.okta.com/oktane/) is just around the corner, where we'll pull back the curtain on what's still to come! Registration is now open, and we hope to see you there.

Unveiling New and Improved Product Features — 6 Month Lookback

leonardo

Leonardo is a Senior Software Architect at Okta, working on the new Auth0 platform and cutting-edge product features. He is a seasoned technical leader with 17 years of experience in a wide range of segments, from enterprise to SaaS systems. As an Apache committer, he has contributed to various open-source projects. He is a self-learner, passionate about new technology, and has spoken at several developer events.

Senior Software Architect

Leonardo Zanivan

Replatforming to enhance agility, productivity, scalability, reliability, and security.

**TL;DR:** Auth0’s private and public cloud offerings are converging on a single platform to deliver an increase in business agility, developer productivity, scalability, reliability, and security for our customers and Auth0 by using industry-leading tools and fully automated operations.

Initially, Auth0 evolved our public and private cloud offerings as separate platforms because we could go fast and innovate on the public cloud and then work through the greater performance, compliance, and control expected by our private cloud customers. But over time, this led to feature discrepancies and, frankly, just wasn’t that efficient to maintain, scale, or innovate.

So we began an ambitious replatforming project. How could we re-architect all of Auth0 into a single platform? Could we support deployments on both Amazon Web Services (AWS) and Microsoft Azure? What about increasing geo-failover options? And we needed to continue our 99.99% SLA across both public and private clouds.

Let’s not forget that private cloud customers may also require extra add-ons like data residency, private links, and dedicated performance. This post will walk you through our approach to rearchitecting Auth0 to address those challenges.

## The Convergence Starting Point

While both platforms worked exclusively on AWS cloud, the private cloud was not using cloud-native solutions. It had three tiers — Basic, Perf, and Perf+ — available as environment sizes. These were selected based on the number of users and requests per second, versus an elastic scalable public cloud environment shared by multiple customers. The main difference is that private deployment usefully isolated and dedicated resources in any region. In comparison, public deployment uses shared resources for multiple customers in specific regions (United States, Europe, Japan, and Australia).

Our public cloud saw new features delivered on a weekly basis, but due to limited automation, our private cloud required high-touch operations for upgrading to new releases that rolled out on a bi-weekly cadence. 

Requirements for private cloud deployments set it up as a superset of the public cloud offering that already guarantees a 99.99% SLA, with a track record of 99.99+% over the last three years. This was across three availability zones and a geo-failover for regional redundancy and availability.

But we knew we also wanted to include extra add-ons like private links, [PCI compliance](), and meet the customer requests for [Azure Cloud]() support.

## New Cloud-Native Architecture

On a high level, the new cloud-native architecture delivers an increase in business agility, developer productivity, scalability, reliability, and security for our customers and Auth0 by using industry-leading tools and fully automated operations.

It closes the gap between Auth0 public and private deployments by packaging all the product features in a single software version and making them available depending on the customer subscription and add-ons. 

The ideation for the new platform is based on the following premises:

* **Multi-cloud: **AWS and Azure cloud support through a common interface
* **Container orchestrated:** use of container images instead of installing packages
* **Stateless**: scalable and replaceable by design
* **Immutable**: run only trusted code and configuration
* **Fully automated:** provisioning, upgrades, and decommissioning are done by machines
* **GitOps:** enhanced DevOps, push code and safely reproduce it thousands of times  

This removes the worry about the underlying infrastructure, allowing Auth0 developers to place their focus on our customers. This can be represented by the layers in the box below:

![Aplication Layer](https://images.ctfassets.net/23aumh6u8s0i/3yX9TOMT8XC0UPPKK6N57h/41dbdb93833d8c2e20e7c2be1bb445ef/88133_Private_Cloud_Campaign_Auth0.png)

* **Infrastructure layer**: It builds the infrastructure using AWS and Azure cloud services such as networking, virtual machines, key management, load balancers, container repositories, Kubernetes, and managed datastores (Mongo, PostgreSQL, Redis, Kafka).
* **Interface layer**: [Terraform](https://www.terraform.io/) is used for bootstrapping the infrastructure using code on different clouds. [Vault](https://www.vaultproject.io/) is used for platform secrets management and [Kubernetes](https://kubernetes.io/) as de-facto technology for application runtime along with custom plugins to describe services manifest, configuration, and secrets using the platform control plane component. [Argo CD](https://argoproj.github.io/cd/) is a GitOps continuous delivery tool used for applying for new software releases while [Argo Workflows](https://argoproj.github.io/workflows) is used for orchestrating the provisioning, upgrades, and decommissioning steps. This layer also contains integrations and agents for managing service discovery/DNS, logs, metrics, security audit, and datastores.
* **Application layer**: It is where the containers run. The Auth0 Identity Platform is built to allow multiple stacks with different sets of containers deployed accordingly to their usage. Auth0 products, PoP, Control Plane, and Central Services use a promotion pipeline for validating new releases and configurable release schedules. Everything is managed by control plane API and developers interact with the new platform CLI or Hub (web interface). One might wonder how identity is managed to access Kubernetes resources, it uses [Pomerium with Auth0 Identity Provider](https://www.pomerium.com/docs/identity-providers/auth0.html), dogfooding our own product.

Before we go deep into the technical details, the blog [A Primer on the New Private Cloud Platform](https://auth0.com/blog/a-technical-primer-of-auth0-s-new-private-cloud-platform/) provides more details about the Space, PoP, Control Plane and Central components of the new platform.

## The Components—A Ten Thousand Foot View

The diagram below demonstrates the main components of the platform and its links, including data flows and cloud regions. Internal services and network details are omitted.

![The Components—A Ten Thousand Foot View](https://images.ctfassets.net/23aumh6u8s0i/2bmBmIoidTViCeyw2dInNB/26a1c8a5cd9ac8a556488585edbb35d4/Arquitecture.png)

**Edge Network**: The global network provider, used by Auth0 for DNS, edge computing, CDN, DDoS protection, web application firewall, custom domain certificates, and speed-up end-user experience.

**Space**: Customer environment containing the dedicated application and datastores resources, deployed in any cloud region, maintaining security and data residency through tight access control for operators. Datastores use dedicated private networks isolated from the applications. New application deployments spin a whole new application cluster containing the new version and then slowly switch the traffic using a 'canary deployment' strategy. In addition to that, 'Data Shield' component is responsible for receiving a variety of data such as application logs and then scrubbing it, removing any PII or sensitive information. Only the clean logs are ingested and clean data is forwarded to Auth0 data analytics and detection & response teams for monitoring the system. The customer data never leaves the cloud region (e.g. Azure EastUS).

**PoP**: Point of presence of the platform in a given cloud region (same as the Space), required to host the container registry of software stacks used by the Kubernetes cluster. This component runs a set of shared services to support the platform, including the OpenSearch stack used by operation engineers to troubleshoot issues. It also runs regional services, shared between Spaces to support platform operations, such as forwarding data analytics, and internal Auth0 system supporting services requiring low network latency for fulfilling requests. It is important to note though that PoP doesn't have access to the Spaces network, it acts as a regional endpoint.

**Central & Control Plane**: A region in the European Union (EU) where the control plane services are deployed. They are internal to Auth0 operators and are used to interact with the customer Spaces and PoPs. It is secured by Zero Trust model and manages platform secrets and metadata using Terraform, Vault, and Argo. In addition to the control plane services, the central component is also designed to run other completely isolated application stacks to host global services accessible by customers and support engineers.

**Auth0**: The analytics aggregated data is sent to Auth0 headquarters and other global systems such as DataDog and Snowflake to be consumed by internal teams in many different departments, such as business analytics, customer support, and engineering teams. The data is categorized into different levels of access and doesn't identify any customer-sensitive information such as personally identifiable information (PII). The Detection & Response team is an exception and runs security software to analyze production traffic and usage patterns to actively detect & mitigate attacks.

## High Availability and Geo-failover

Auth0 guarantees a 99.99% SLA for production deployments. On a high level, the infrastructure is fully redundant, and all components are deployed into multiple availability zones, using at least 3 availability zones (AZ) combined primary and secondary regions, either in clustered mode or standby replicas. 

For web applications, the traffic is distributed across multiple Kubernetes nodes using load balancing. For datastores, Mongo and PostgreSQL are considered the system of record, i.e. the authoritative source of data, deployed in the primary region with a writer and at least a reader node for splitting write/read traffic and replicating the data to a secondary (failover) region in real-time. The caching (Redis) and stream (Kafka) components are deployed using sharding and failover capabilities, always providing high availability for runtime and data.

As for central services, control plane, and PoPs, they also run on high availability infrastructure and have the ability to failover, while this process is executing or in case of temporary or permanent network connectivity issues, the Spaces continue functioning as expected without any disruption. Spaces are isolated from each other and are fault-tolerant to other tiers' failures. 

The geo-failover is a fully automated process and is manually triggered by an operator during incident response for disaster recovery in case a cloud region is fully or partially unavailable. The process redirects all the traffic to the secondary region (determined by the customer) which switches the DNS of the cluster ingress and promotes the secondary region replicas to become the primary writer; there's no dependency on the primary region for the disaster recovery to successfully execute. 

The target RPO (Recovery Point Objective) is less than a minute, the time period in which data and events can be lost due to the disaster recovery procedure. At the same time, the RTO (Recovery Time Objective) is less than 15 minutes for the amount of downtime tolerated during the disaster recovery process.

The process of failback (revert the failover) from the secondary to the primary region is the same and can be triggered once the situation resolves.

The diagram below shows the Auth0 deployment containing a primary and a secondary warm standby region with high available datastores, and for simplifying purposes other AZs running only applications are omitted:

![Azure servers](https://images.ctfassets.net/23aumh6u8s0i/7f96vQ2UJukSjYJYc5flNt/a406ca7bac6ad54dc5e2bfc75c754dd8/Azure_servers.png)

We are publishing a series of technical posts on how and why we replatformed. They’ll be linked at the bottom of this post as they publish and are also findable on our blog. If you have technical questions or ideas for future posts, please reach out to us via the [Auth0 Community](https://community.auth0.com/). (Our marketing team also tells us we would be remiss if we didn’t include a link to talk to Sales so that is [here](https://auth0.com/contact-us), too.)

The Architect’s View of Auth0’s New Private Cloud Platform

kaycie-east

As PR Manager, Kaycie supports public relations and global communications efforts for Auth0 in the AMER region. When not promoting the Auth0 brand, Kaycie can be found hiking, traveling, or searching for the next best bite to eat.

PR Manager, AMER Region

Kaycie East

New private cloud deployment option offers customers greater choice, scalability, and reliability

**BELLEVUE, Wash. – Oct. 13, 2021 –** The [Auth0 Identity Platform](https://auth0.com/), a product unit within Okta (NASDAQ: OKTA), today announced the launch of the [Auth0 Identity Platform on Microsoft Azure](https://auth0.com/cloud/azure). The launch gives customers the ability to choose Azure as their cloud deployment option from Auth0. The addition of Azure as an Auth0 private cloud platform option unlocks a secure cloud deployment option for organizations seeking strategic fit with their technology stack, supporting regional data residency capabilities and higher control over customer data.

Today, organizations moving to the cloud and selecting a [Customer Identity and Access Management (CIAM)](https://auth0.com/blog/what-is-ciam/) solution require significant control over sensitive customer data and may require local data residency capabilities. They often have to make a hard choice of selecting either a CIAM solution that supports their product differentiation goals or one that meets their technical requirements and regulatory needs. Auth0’s modern identity platform eliminates the need to choose by providing organizations with tools designed to support security, compliance, and data residency needs that may apply to them across multiple regions globally. The platform’s design can accelerate their time to value and go-to-market strategies to meet their long-term growth goals. 

Key benefits of the Auth0 Identity Platform on Azure include:

* **Technology Stack Alignment:** Organizations have the flexibility to choose Azure as their preferred cloud vendor for greater technology stack alignment with existing investments in Azure. 
* **Data Residency:** Improved data residency capabilities for Auth0 customers with Azure’s widespread geographic infrastructure.
* **Streamlined Experience with Private Cloud:** A modern, cloud-native platform built with a focus on security and compliance at every level. Organizations requiring data residency options can take advantage of periodic feature updates while maintaining control over the timing and the ability to roll back without the hassle of having to maintain them — resulting in faster time to market and a more seamless experience for organizations and their customers.

“As more applications move to the cloud and expand globally, organizations depend on their identity service to protect and manage access for their most critical users, applications, and data,” said Shiv Ramji, Chief Product Officer at Auth0. “The Auth0 Identity Platform on Azure can help unlock a secure and compliant cloud deployment experience for organizations seeking support across CIAM use cases. This is especially true for organizations in industries like retail or financial services where selecting vendors that are not competitive to their business is top priority, organizations operating in regions where certain cloud providers have higher geographic availability, and those that have existing technology investments in Azure.”

“Companies like Auth0 add value by integrating their solutions with Microsoft Azure,” said Mandana Javaheri, Global Senior Director, SCI Business Development at Microsoft Corp. “With Azure, Auth0 customers have ultimate performance capabilities and control over their environment without the hassle of maintaining it, allowing customers to focus more on their core business proposition.”

More detailed information on the Auth0 Identity Platform on Azure can be found on [Auth0’s blog](https://auth0.com/blog/auth0-on-microsoft-azure-as-a-private-cloud-deployment-option). Auth0 will discuss this offering in greater detail with Okta at Showcase21 taking place today, Oct. 13, 2021. To learn more, visit: [https://www.okta.com/showcase/register](https://www.okta.com/showcase/register) 

<include src="asides/AboutAuth0" />
### Media Contacts:

Global Communications 
Auth0 
[press@auth0.com](mailto:press@auth0.com) 

Matter Communications for Auth0 
[auth0@matternow.com](mailto:auth0@matternow.com) 

### Investor Contact:
Investor Relations 
[investor@okta.com](mailto:investor@okta.com)

Auth0 Identity Platform Now Available on Microsoft Azure

diegopoza

System Engineer, geek, foodie, technology lover, speaker.

Sr Manager, Developer Advocacy

Diego Poza

Hear from Auth0 customers how CIAM supports scalability and drives transformation

With people not only working but also shopping, banking, socializing, and receiving healthcare via digital platforms, identity management has become not just [a competitive advantage](https://auth0.com/blog/why-auth0-b2b-federation-is-your-secret-weapon-for-enterprise/) but a requirement. Organizations across industries need to manage identity in a secure, scalable, and seamless way. Part of the challenge is that identity is disseminated across multiple applications and devices, effectively making [identity itself the perimeter](https://auth0.com/resources/whitepapers/identity-perimeter). To satisfy user expectations and meet business needs in this new ecosystem, organizations are embracing third-party [identity-as-a-service (IDaaS)](https://auth0.com/blog/what-is-idaas/) solutions like Auth0.

At the core of the IDaaS space is [identity and access management (IAM)](https://auth0.com/blog/what-is-iam/), which involves authenticating users’ identities and controlling their access to online resources. A key enabler for organizations undergoing digital transformation, IAM encompasses:

* **Authentication**, or how you determine whether someone’s claimed identity matches their actual identity. [Multi-factor authentication (MFA)](https://auth0.com/multifactor-authentication) is increasingly recognized as the standard method of authenticating identity.
* **Authorization**, or the allocation of permissions to individual users or types of users. For instance, if an administrator leaves your organization, you can revoke their permissions; you can also add users or expand permissions according to your needs.

Typically, organizations have to manage identity for different types of users: customers, employees, and enterprise partners. Because each type of user has different priorities and expectations of your platform, each type demands its own carefully calibrated balance of convenience, privacy, and security. For example, your employees and contractors will probably put up with time-consuming, headache-inducing processes to get paid and access other benefits because they have few alternatives. Customers, on the other hand, have lots of choices, and if you can’t deliver a swift, effortless login experience, they’ll find one of your competitors who can.

[Customer identity and access management (CIAM)](https://auth0.com/blog/what-is-ciam/) platforms are built to optimize the balance between convenience, privacy, and security for each type of user. With the right CIAM platform, you can:

* Deliver a secure and frictionless login experience
* Guide compliance with data privacy laws
* Protect data assets against malicious intrusion
* Derive more specific, meaningful insights from customer data

Using four Auth0 customers as examples, let’s explore how CIAM can help you allocate resources more effectively, secure identity across your entire infrastructure, and deliver more value to your users. 

In [our new whitepaper](https://auth0.com/resources/whitepapers/ciam-transformation), we delve more deeply into each of these customer stories and suggest strategies for choosing and implementing the right CIAM platform. If you find this content useful, be sure to [download the full whitepaper](https://auth0.com/resources/) or check out some of our other [identity resources](https://auth0.com/resources/).

## Enable Expanding Use Cases

With 170 superstores across the UK, furniture retailer [Dunelm](https://auth0.com/case-studies/dunelm/) describes themselves as “product-obsessed.” In 2018, they began a massive digital overhaul of their existing internal infrastructure in favor of a modern, flexible cloud data platform that would transform the digital experience for their customers, employees, and external vendors.

> A key aspect of Dunelm’s [buy-rather-than-build](https://auth0.com/resources/whitepapers/build-vs-buy-for-b2b-evaluating-identity-management) approach to their digital infrastructure was replacing their in-house identity system with Auth0. This move has saved them significant time, effort, and staffing costs.

Initially, Dunelm planned to use Auth0 for straightforward customer authentication, but they soon incorporated the service into multiple business operations serving customers, employees, and partners.

From here, Dunelm plans to further expand its Auth0 use case and add more customer value through personalized, frictionless shopping experiences.

![CIAM](https://images.ctfassets.net/23aumh6u8s0i/5rQhP0U1KzmX0aJfsAuZh3/dbc28afb39fa3f557119114372a086bc/CIAM_ecommer_e_recorte1.png)

## Centralize Identity across Platforms

UK-based conditioning brand [Gymshark](https://auth0.com/case-studies/gymshark/) is one of the most recognizable functional training apparel brands in the world, with a social media following of 10+ million and customers in over 170 countries. During the development process for their conditioning app, Gymshark realized they needed a centralized authentication solution that worked across both their online and mobile applications. They had one major priority: a seamless customer experience.

While they briefly considered building their own solution, Gymshark ultimately decided to entrust Auth0 with their CIAM needs. With Auth0 handing IAM for customers and employees, Gymshark can focus on creating apps and other technology that advances their core mission. Auth0 is a critical enabler for Gymshark’s tech-powered, user-centric future. 

## Replatform and Eliminate Legacy Code

[Kiva](https://auth0.com/case-studies/kiva-implements-auth0-rules-mfa/) is an international crowdfunding nonprofit focused on expanding financial access to help underserved communities around the world thrive. Kiva had built their own authentication solution in-house over time, adding functionality when they needed it to meet business requirements, but they knew they needed to replatform to a microservice architecture with a dedicated identity service to support future growth.

With Auth0, Kiva was able to eliminate more than 22,000 lines of legacy code, freeing up engineering resources considerably and allowing the company to focus its efforts on core business functions rather than on managing identity. Investing in CIAM now also prepares Kiva for successful mobile implementation, which is key to their growth strategy. The bottom line: CIAM enables Kiva to shift and scale securely and with minimal friction. 

## Achieve Smooth Scalability

[TVNZ](https://auth0.com/case-studies/tvnz-cs/), New Zealand’s state-owned, commercially funded broadcaster, reaches more than two million New Zealanders every day. TVNZ also offers OnDemand streaming services that reach up to half of the country’s five million citizens with 2.5 million registered accounts. At a moment in history when a trustworthy news source is more important than ever, the broadcaster needed a CIAM partner who could help them rapidly scale, migrate users, and maintain their reputation.

When they signed on with Auth0 to handle authentication for their OnDemand streaming web and mobile platforms, TVNZ was faced with the task of migrating data for 2.5 million accounts. To avoid forcing all of their customers into a password reset, TVNZ opted for an automatic migration in which customer data was migrated only when a person logged in.

But another challenge lay ahead. TVNZ’s digital platforms faced unprecedented demand during the pandemic lockdown, with weekly streaming rates jumped by 50% and tens of thousands of users logging in more or less simultaneously to watch Prime Minister Jacinda Ardern’s daily addresses. With Auth0 handling their identity needs, TVNZ experienced “no real issues,” reported [Michael Robinson](https://www.linkedin.com/in/faceleg/?originalSubdomain=nz), Head of Digital Capability at TVNZ. Entrusting CIAM to Auth0 allows TVNZ to stay on mission and maximize the value of their development resources.

![CIAM](https://images.ctfassets.net/23aumh6u8s0i/1fjzGfRtdlHhMCsxgeDZdp/86223bf45b185cfa9ddee428eefa28b6/CIAM_ecommerce_recorte2.png)

## What Challenges Could CIAM Solve for You?

Is your login process so painless that customers barely register it? Do your customers trust you to handle their personal information? Do you have all the insights into customer behavior you need? Are you confident that your customer identity solution can scale in response to escalating demand without lags or outages? Unless the answer to all of these questions is an unambiguous “Yes!” (in which case, nice work!), investing in CIAM is a sound decision.

Ask yourself what your team could accomplish if they didn’t have to worry about managing customer identity and access. For a closer look at the customer stories we’ve summarized here, and to learn more about how CIAM can enable digital transformation at your organization, [download the whitepaper](https://auth0.com/resources/whitepapers/ciam-transformation).

<include src="asides/AboutAuth0" />

Four Ways CIAM Empowers Your Business

Enable agile scalability with customer identity and access management (CIAM)

In the last few years, identity has become a familiar concept to business decision-makers seeking to fortify their security, unlock efficiency gains, and outpace competitors.

[Customer identity and access management (CIAM)](https://auth0.com/blog/what-is-ciam/) is a set of solutions built to help organizations balance convenience, privacy, and security for every type of user who needs access to their platform. At Auth0, we’ve heard from our customers that investing in third-party CIAM solutions can benefit the entire organization, especially by:

* Providing a seamless, secure customer experience
* Protecting against expensive data breaches
* Guiding compliance with data privacy laws
* Gathering customer data into a single source of truth
* Increasing the success of digital transformation projects

Another major advantage to CIAM is that centralizing customer identity helps you build more scalable solutions — and scalability is both a benefit of and a requirement for the advantages listed above. Simply put, CIAM gives you the tools you need to scale identity quickly.

![The Business Value of Scalability](https://images.ctfassets.net/23aumh6u8s0i/BXZTiwu81LfqqP7O3yEmj/a66340c22f87e48739da621e7e46cdf6/02_B_power.jpg)

## The Business Value of Scalability

Scalability refers to a system’s ability to increase its capacity and functionality based on the evolving demands of its users. Your industry may be volatile, but scalable software allows your platform to remain stable in the face of infrastructure changes, updates, overhauls, and resource reductions/additions.

Laggard legacy systems are inflexible and resource-intensive to maintain, which for many companies is reason enough to prioritize digital transformation. Critically, legacy systems also fall short of modern scaling demand and user expectations. 

In contrast, building scalable solutions helps your organization increase predictability; trim maintenance and upgrade costs; and become more agile, so you can meet customers’ dynamic demands.

> Scalable software also shortens time-to-value. Your teams will bring products to market more quickly and deliver more value to your customers if they don’t have to worry about scaling your identity solution.

### Increase reliability

Scalable software systems increase reliability, so you can avoid outages and maintain continuous uptime. The ability to provide a smooth, consistent customer experience even in the face of demand spikes is a key competitive advantage enabled by CIAM. When circumstances like a major news broadcast or a big sporting event cause your platform to be flooded with requests, you don’t want to experience lags or outages. The bottom line: Lack of scalability leads to reduced reliability, which can drive users to another service. 

### Protect against data breaches

A scalable identity solution helps protect customer data from breaches and exposures that can occur as your organization scales. [A 2020 IBM-Ponemon study](https://www.ibm.com/security/data-breach) found that data breaches cost an average of $3.86 million per incident globally, with the number rising to $8.64 million on average in the United States. Breach-related costs include actual fines and reputation erosion that can lead to customers shifting to competing brands.

<include src="TweetQuote" quoteText="With CIAM, you can offer your customers the convenience of rapid authentication without introducing security vulnerabilities that make you more susceptible to a data breach." />

### Be ready for mergers and acquisitions

If you want to enhance your appeal as an acquisition target, or if you’re evaluating other companies to acquire, a solid CIAM strategy is critical. [Implementing CIAM before a merger or acquisition](https://auth0.com/blog/why-iam-is-essential-to-m-a-and-replatforming/) can prevent you from spending months integrating applications struggling to reconcile a high volume of user data, exposing security vulnerabilities, or introducing friction that drives customers away. 

CIAM goes a long way toward minimizing the disruption of M&A activity: before, during, and after integration. Managing post-M&A integration in-house is a difficult, time-consuming job that keeps your developers from devoting their full attention to your core solutions — which is more important than ever when you need to mitigate churn. [As Auth0 customer Cimpress discovered](https://auth0.com/case-studies/cimpress/), the right approach to customer identity management allows you to connect companies with divergent systems to your platform quickly and easily.

## How Does CIAM Enable Scalable Identity?

Identity touches every function of your business. Typically, organizations have to manage identity for different types of users: customers, employees, and enterprise partners. Each user type has different requirements for your platform depending on how they use it. CIAM not only helps you provide the right balance of convenience, privacy, and security to each type of user; it also gives you superior insight and a single source of truth to drive better strategic decision-making. 

### Give customers the frictionless experience they want

When a seamless customer experience is your first priority, scalability is an absolute requirement. And with customer-facing applications, ease of experience is everything. If your CIAM solution doesn’t scale, your users will abandon you for another service.

As a customer, you’ve probably experienced this impatience. If you’re trying to order dinner and your first-choice food delivery platform is overwhelmed and experiencing lags, you’ll switch over to another platform — and that platform might be your first choice from then on.

CIAM also allows companies to unify their login experience across apps, creating a consistent experience that benefits both user and brand. UK-based conditioning company [Gymshark](https://auth0.com/case-studies/gymshark/), an Auth0 customer, is a great example of how CIAM enables an exceptionally smooth, secure login experience across platforms. Gymshark needed a universal login solution that could authenticate customers across 15 different online stores and mobile apps. With Auth0, they’re able to manage access for 250,000 monthly users while securing their platform against [credential stuffing attacks](https://auth0.com/resources/whitepapers/credential-stuffing-attacks) and other threats to the login box.

### Cultivate customer trust with strong security

Your customers trust you to keep their personal information private; to be transparent and responsible with how you collect, store, and use their data; and to comply with regulations designed to protect customer privacy. CIAM enables you to uphold this trust as your solution scales, and your integration ecosystem expands.

Data privacy laws like [GDPR](https://auth0.com/docs/compliance/gdpr), [CPRA](https://auth0.com/blog/cpra-passed-what-s-changing-in-ccpa-2-0/), and [APPI](https://auth0.com/resources/whitepapers/amended-appi) require companies to understand how third-party providers manage the collection, use, and storage of data in their systems. CIAM solutions help guide compliance with these regulations, so you don’t lose sleep over non-compliance fines or expensive data breaches.

Implementing CIAM shows customers that you are literally invested in ensuring their privacy and security. Similarly, essential [certifications](https://auth0.com/docs/compliance) like HIPAA, CSA STAR, and ISO 27001/27018 also signify to customers and regulators that you’re not just claiming a strong security posture; you’re undergoing regular, rigorous security checks by an expert third party.

### Accelerate time-to-market and solve for future problems

Implementing CIAM lets your developers focus on supporting your core solutions instead of also having to manage identity in-house. As a result, you’ll bring products to market faster and deliver more value to your customers.

At Auth0, we recommend that companies make decisions around CIAM based not on where their business _is_, but on where they want it to be. You need identity management capable of scaling to meet future business needs, not just the pain points you encounter today. Where do you want your business to be in five years? How will that drive your scalability needs? Think strategically about your desired future state. If you get overly focused on the pain points you’re encountering right now; you may be inviting incompatibility and tech debt into your business infrastructure.

![Manage Identity Complexity with CIAM](https://images.ctfassets.net/23aumh6u8s0i/5jPq4nBdhF6cZtBAJYb2xM/2cafa607686a3a828b43b9d3161cdd8d/02_C_power.jpg)

## Manage Identity Complexity with CIAM

Since identity touches every aspect of your business, the functionality and scalability of your identity solution will tend to match the functionality and scalability of your organization as a whole. With CIAM, you can deliver the secure, frictionless experience your customers expect as you scale and integrate your ecosystem. That’s why many of our customers have opted to manage the complexity of identity with CIAM.

To learn more about how CIAM can help you reach your milestones, [get in touch](https://auth0.com/contact-us) with the experts at Auth0.

<include src="asides/AboutAuth0" />

How to Scale Quickly with Identity

ghazi-masood

I'm a seasoned business leader with nearly a 25 year track record in Sales running and managing teams of all sizes working in leadership positions for world class organizations.  Nowadays, you can find me at Auth0 leading all aspects of Revenue growth  for the Americas business.

Auth0 Vice President and General Manager, Americas.

Ghazi Masood

From scalability to CX, CIAM unlocks business-wide benefits

Customer experiences happen primarily online. If this wasn’t completely true for your business before 2020, it’s probably true now. Companies have come to understand that a seamless digital experience is no longer a competitive differentiator; it’s a baseline requirement.

Moreover, pressure-cooker economic conditions during the pandemic have shown that [companies that understand their customers’ needs on a deep level](https://digitally.cognizant.com/customer-identity-and-access-management-in-the-age-of-covid-19-codex5721/) are better-positioned to succeed. One way organizations are trying to do this is [customer identity and access management (CIAM)](https://auth0.com/blog/what-is-ciam/).

CIAM refers to a set of solutions intended to create the optimal balance between convenience, privacy, and security for each type of user. While [identity and access management (IAM)](https://auth0.com/blog/what-is-iam/) is focused on managing identity and access for employees and partners, CIAM centers on customers.

CIAM exists at the intersection of customer experience, security, and analytics. It enables a smooth onboarding/login experience to build customer loyalty and increase conversion rates, guides compliance with data privacy laws and empowers companies to prevent data breaches. Crucially, CIAM encompasses not only how companies control end-users’ access to digital assets but also how they collect, analyze, and store data related to those users.

## A Centralized Source of Truth

CIAM enables companies to compile siloed user data into a single source of truth that helps you make better strategic decisions. If your user data is disorganized, siloed, and inaccurate, you can’t generate a clear picture of your customers. Without clear insight into your users, you can’t offer highly personalized offers and product recommendations that drive additional revenue and create more value for your customers.

> Duplicate and siloed data also create barriers to compliance with data privacy laws. A centralized view of your customers gives you the tools you need to meet the requirements of laws like [GDPR](https://auth0.com/resources/whitepapers/GDPR-vs-CCPA) and [CPRA](https://auth0.com/blog/cpra-passed-what-s-changing-in-ccpa-2-0/).

### Can’t we build it ourselves?

Some organizations manage part or all of CIAM themselves, but that’s a big challenge, and it gets bigger as you scale. Given the complexity and dynamism of CIAM, forward-thinking companies are entrusting CIAM to one or more third-party [identity-as-a-service (IDaaS)](https://auth0.com/blog/what-is-idaas/) experts. Outsourcing CIAM to a third party is a wiser use of your resources than asking your developers to manage customer identity in-house. [Buying rather than building your CIAM solution](https://auth0.com/resources/whitepapers/ciam-buyers-guide) saves time and money, and it gives you the agility and expertise you need to respond to evolving use cases, new or updated privacy laws, and other variables that can make identity management more complicated.

## Business Benefits of CIAM

Centralizing user data on one platform unlocks company-wide benefits even beyond creating a single source of truth. Here’s an overview of the organizational rewards you can realize with CIAM.

### Scalability

On the list of advantages of CIAM, scalability is near the top. Unlike B2B and workforce identity solutions that support users with static access to preassigned applications, CIAM platforms must be able to support millions, even billions, of users. In addition, CIAM solutions must be able to scale in response to not only anticipated events (like the holiday shopping season or the World Cup) but also to unanticipated events that can dramatically increase demand (like [viewers eager for official updates during the pandemic](https://auth0.com/case-studies/tvnz-cs/)).

### Customer experience

When customer experience is a priority, features like [single sign-on (SSO)](https://auth0.com/docs/sso) and adaptive [multi-factor authentication (MFA)](https://auth0.com/learn/social-login/) help you deliver the frictionless CIAM experience your customers expect.

CIAM platforms also enable event-driven personalization tactics, such as progressive profiling, in which user data is collected incrementally in a series of interactions over time. The goal is to build a trusting, mutually beneficial relationship between the company and customers. Users recognize that by providing more information (such as rating a purchase or filling out demographic information), they can get more value in the form of personalized offers and relevant recommendations. And by cultivating the trust of their customers, companies ultimately realize more value in terms of both reputation and revenue.

### Security

Customer data is among your organization’s most prized assets. In the wrong hands, however, data becomes a liability. That’s why the best CIAM solutions have robust security features built to defend against malicious attacks on any front.

For many organizations, the login box is the front line of defense against [broken authentication attacks](https://auth0.com/blog/what-is-broken-authentication/) like [credential stuffing](https://auth0.com/resources/whitepapers/credential-stuffing-attacks). A CIAM solution with MFA and brute force protection is an important part of your defense strategy. MFA ensures that one stolen credential won’t allow automatic access to your users’ other accounts, while brute force protection keeps attackers from barraging your application with fraudulent login attempts that can crash your site.

### Privacy and compliance

Centralized user management is necessary to meet the reporting and erasure requirements of data privacy laws like [GDPR](https://auth0.com/resources/whitepapers/GDPR-vs-CCPA), [CPRA](https://auth0.com/blog/cpra-passed-what-s-changing-in-ccpa-2-0/), APPI, and LGPD. These laws are literally rewriting the rules for how organizations are permitted to collect, store, and leverage user data. CIAM helps you meet these legal requirements by enabling the encryption of sensitive data, controlling access to digital resources, and collecting data, and [managing consent](https://auth0.com/blog/what-you-need-to-understand-about-consent-management/) in compliance with applicable laws.

## Create More Value with CIAM

As organizations initiate and accelerate digital transformation projects to meet sky-high demand for digital services, CIAM is becoming indispensable across industries, from [retail](https://auth0.com/case-studies/dunelm/) to [tech-powered fitness](https://auth0.com/case-studies/gymshark/). 

In our whitepaper, we explore in depth the capabilities you should look for in a CIAM platform, from scalability and agility to personalization and compliance. You can also [reach out to the Auth0 team](https://auth0.com/contact-us?place=blog%20post&type=link&text=contact%20us) to learn more about how CIAM could benefit your organization.

<include src="asides/AboutAuth0" />

Why do you need CIAM?

auziros:jeana-tahnk

Jeana has been in the tech industry for 15+ years, both as a communications professional and writer. As Director of Global Communications at Auth0, she works with her internal team and external agencies to amplify the company's visibility worldwide and establish its leadership in the identity industry. When she is not working, she can most likely be found on a field watching one of her three kids playing sports, or cleaning up after her one-year-old retriever who chews everything.

Senior Director, Global Communications

Jeana Tahnk

Salesforce's Next Generation Identity demands the scalability, agility, and connected digital experiences that Auth0 offers

**BELLEVUE, Wash. – November 17, 2020 –** The [Auth0](https://auth0.com/) Identity Platform, a product unit within Okta, today announced it has been selected as the identity provider to power authentication for Salesforce Customer 360 Identity, its best-in-class consumer identity and access management (CIAM) technology, providing a single, trusted identity for more streamlined user management. Salesforce Customer 360 Identity will go into a pilot phase at the end of the year and will be generally available in early 2021. 

Salesforce Customer 360 Identity is one of four products that comprise [Customer 360 Truth](https://www.salesforce.com/products/platform/features/customer-360-truth/), a set of data and identity services that enable companies to build a single source of truth for relevant and lasting customer relationships. The leading CIAM, data management, customer data platform, and privacy tools available in Customer 360 Truth provides a unified customer view to maintain customer privacy, security, connect siloed data systems, and harness new digital business.

Driving the frictionless login experiences for all Customer 360 Identity users, Auth0 will provide a seamless signup to drive better conversions, the ability to scale to any size, and a single customer login across all users' digital properties, eliminating siloed data and providing a single source of truth for IT departments. 

"The need for digital transformation has reached new heights, challenging companies to deliver simple, connected, and trusted experiences online," said Patrick Stokes, EVP, Platform Shared Services at Salesforce. "Customer 360 Truth delivers just that. And, combined with Auth0, companies will be able to engage with their customers like never have before—authenticating millions of users quickly and securely."

"Customer data is the cornerstone of Customer Success and hinges on the ability to have a comprehensive view of your customers," said Nick Mehta, CEO of Gainsight. "As a customer of both Auth0 and Salesforce, I'm excited about their integration to help streamline how we access and map user data."

Auth0's deep developer roots and the ability to provide a superior pro-code developer experience offers a natural integration into Salesforce's platform. Auth0's platform provides the out-of-box experience that most customers need and also allows their developers to easily customize their login flows via code and the large library of integrations readily available from the Marketplace. 

"Persistent challenges B2C customers face&mdash;scale, needing a holistic view of the customer, and enhanced security&mdash;are consistent across the industry, especially with the urgent speed in which companies are prioritizing their transformation efforts," said Shiven Ramji, Chief Product Officer at Auth0. "We believe this need will intensify as more businesses are forced to transform and we look forward to working with Salesforce customers going through this process."

In July 2020, Salesforce Ventures was the lead investor in Auth0's $120 million Series F round, bringing Auth0's valuation to $1.92 billion and total capital raised to more than $330 million. 

<include src="asides/AboutAuth0" />

### Media Contacts
Global Communications 
Auth0 
[press@auth0.com](mailto:press@auth0.com) 

Hannah Carroll 
Matter for Auth0 
[auth0@matternow.com](mailto:auth0@matternow.com)

Auth0 Selected as Identity Vendor of Choice for Salesforce Customer 360 Identity

Tech platform supporting more than 13,000 local pizzerias nationwide relies on scalability and login security with Auth0

**BELLEVUE, Wash. – October 15, 2020 –** The [Auth0](https://auth0.com/) Identity Platform, a product unit within Okta, today announced that it has been selected as the sole identity and authentication provider for [Slice](https://slicelife.com/), the innovative tech platform powering America’s local pizzerias. Having recently closed a successful [round of Series C funding](https://blog.slicelife.com/slice-raised-43m-in-series-c-funding-to-power-local-pizza/), Slice will use Auth0’s platform to provide a secure login experience for Slice’s five million customers as it continues to scale. 

Slice transforms independent pizzerias with the specialized technology, data insights, and shared services needed to serve today’s digital-minded consumers. Its vast network of more than 13,000 local pizzerias enables these small businesses to compete against major corporate chains and form the nation’s largest marketplace for authentic pizza across 3,000 cities in all 50 states. 

As its network of pizzerias and customers continues to grow, Slice looked to Auth0 to provide authentication for its growing consumer base, already over five million users. After a thorough review of solutions, Auth0 was determined to be a much better fit for scale, security, and lower ongoing maintenance costs. Another big factor in selecting Auth0 was its ability to support bulk migration, eliminating the hassle for end-users to have to reset their passwords.

“Auth0 is the only identity management platform that offers the level of flexibility, security, and customization we need,” said Jason Ordway, CTO for Slice. “Our goal is to provide our users across the country with easy access to their favorite local pizzerias. Auth0 will be a great partner in enabling that while also setting us up for success for our continued growth.”

“Slice is transforming the pizza business, and is helping local businesses move online to keep up with today’s digital demands, especially during the pandemic,” said Ghazi Masood, SVP of Americas for Auth0. “We are thrilled to support Slice’s identity needs and help them seamlessly scale to continue expanding their network.” 

<include src="asides/AboutAuth0" />

### Media Contacts
Auth0 Global Communications 
[press@auth0.com](mailto:press@auth0.com) 

Matter for Auth0 
[auth0@matternow.com](mailto:auth0@matternow.com)

Auth0 Delivers Secure Authentication for Slice

Dirceu-Tiegs

What I enjoy the most about being an SRE at Auth0 is that it allows me to exercise different areas such as coding, architecture, writing, training, investigations, debugging, and incident response. It's great to be able to think deeply about all aspects related to reliability and then apply it to large-scale, real-world projects.

Site Reliability Engineering Team

Dirceu Tiegs

Learn more about how Auth0 architects its services to ensure scalability and high availability to handle more than 1.5 billion logins per month.

Auth0 provides authentication, authorization, and single sign-on services for apps of any type (mobile, web, native) on any stack. Authentication is critical for the vast majority of apps. We designed Auth0 from the beginning so that it could run anywhere: on our cloud, on your cloud, or even on your own private infrastructure.

In this post, we'll talk more about our public SaaS deployments and provide a brief introduction to the infrastructure behind [auth0.com](https://auth0.com/) and the strategies we use to keep it up and running with high availability. This is an updated version of the [2014 High Scalability post about Auth0's architecture](http://highscalability.com/blog/2014/12/1/auth0-architecture-running-in-multiple-cloud-providers-and-r.html).

A lot has changed since then in Auth0. These are some of the highlights:

- We went from processing a couple of million logins per month to 2.5 billion logins per month, serving thousands of customers, including [FuboTV](https://auth0.com/learn/sports-centric-streaming-service-fubotv-sees-50-roi-just-auth0s-security/), [Mozilla](https://auth0.com/blog/auth0-mozilla-partnership/), [InterMiles](https://auth0.com/learn/jetprivilege-case-study/), and more.

- We implemented new features like [custom domains](https://auth0.com/docs/custom-domains), [scaled bcrypt operations](https://auth0.engineering/bcrypt-as-a-service-9e71707bda47), vastly [improved user search](https://auth0.com/docs/users/search/v3), and much more.

- The number of services that compose our product in order to scale our organization and handle the increases in traffic went from under 10 to over 30 services.

- The number of cloud resources grew immensely as well; we used to have a couple dozen nodes in one environment (US), now we have more than a thousand over four environments (US, US-2, EU, AU).

- We doubled-down decided to use a single cloud provider for each of our environments and moved all our public cloud infrastructure to AWS.

## Core service architecture

![Auth0.com core service architecture](https://images.ctfassets.net/23aumh6u8s0i/2mden7W7brrYGv8LHDK2Lp/5347634d4197ae655555cf93b8209c2d/auth0-core-service-architecture)

The core service is composed of different layers:

- Core applications: Auto-scaling groups of servers running different services of our stack (authentication, management API, multi-factor authentication API, and much more).

- Data storage: Clusters of MongoDB, Elasticsearch, Redis, and PostgreSQL storing a variety of datasets for different applications and features.

- Transports/Queues: Kinesis streams and RabbitMQ, SNS, and SQS queues.

- Base services: Services for rate-limiting, bcrypt clusters, feature-flags, and more.

- Routing: AWS load balancers (ALB, NLB, and ELB from AWS) and some nodes running NGINX as a proxy.

## High Availability

In 2014 we used a multi-cloud architecture (using Azure and AWS, with some extra resources on Google Cloud) and that served us well for years. As our usage (and load) rapidly increased, we found ourselves relying on AWS resources more and more.

At first, we switched our primary region in our environment to be in AWS, keeping Azure as failover. As we began using more AWS resources like Kinesis and SQS, we started having trouble keeping the same feature set in both providers. As our need to move (and scale) faster grew, we opted to keep supporting Azure with a limited feature parity: if everything went down on AWS, we could still support core authentication features using the Azure clusters, but not much of the new stuff we had been developing.

After some bad outages in 2016, we decided to finally converge on AWS. We stopped all efforts related to keeping the services and automation platform-independent and instead focused on:

- Providing a better failover story inside AWS, using multiple regions and at least 3 Availability Zones per region.

- Increasing usage of AWS-specific resources like auto-scaling groups (instead of using fixed clusters of nodes), application load balancers (ALBs), and more.

- Writing better automation: we revamped our automation, completely embracing infrastructure as code using TerraForm and SaltStack to provision new Auth0 environments (and also to replace existing ones). This allowed us to grow from partially automated environments doing ~300 logins per second to fully automated environments doing more than ~3.4 thousand logins per second; using the new tooling makes it easier to scale up (and down, whenever it makes sense). The level of automation we achieved is not perfect but is allowing us to grow to new regions and create new environments in a much more convenient way.

- Writing better playbooks: with more time and focus, we saw that besides automation we also needed better playbooks in order to understand, manage, and respond to incidents related to our ever-growing mesh of services. This vastly improved scalability and reliability while also allowing us to onboard new employees faster.

<include src="TweetQuote" quoteText="Writing better automation let us grow from partially automated environments doing ~300 logins per second to fully automated environments doing more than ~3.4 thousand logins per second"/>

Let's take a look at our US environment architecture, for instance. We have this general structure:

![Auth0 US Environment Architecture](https://images.ctfassets.net/23aumh6u8s0i/4hGMwY5n4jk2aoJyyRAhjF/0ca131b596da7068aced34ca69fbbc5c/auth0-us-environment-architecture)

And this is the structure inside a single AZ:

![Auth0 Single Availablity Zone](https://images.ctfassets.net/23aumh6u8s0i/4EtOG7to5lHmyYnU5Q3aaC/a22b74fe7b0a58d0f54a78a6b801bbd2/auth0-single-availability-zone)

In this case, we use two AWS regions: us-west-2 (our primary) and us-west-1 (our failover). Under normal circumstances, all requests will go to us-west-2, being served by three separate availability zones.

This is how we achieve high availability: all services (including databases) have running instances on every availability zone (AZ). If one AZ is down due to a data center failure, we still have two AZs to serve requests from. If the entire region is down or having errors, we can update Route53 to failover to us-west-1 and resume operations.

<include src="TweetQuote" quoteText="We achieve high availability by running all services instances on every AWS availability zone"/>

We have different maturity levels for service failover: some services, like user search v2 (that builds a cache on Elasticsearch) might work but with slightly stale data; still, core functionality keeps working as expected.

In the data layer, we use:

- A cross-region cluster for MongoDB.

- RDS replication for PostgreSQL.

- Clusters per region for Elasticsearch with automated snapshot and restores running regularly to account for the lack of cross-region clustering.

We exercise failover at least once per year, and we have playbooks and automation to help new infrastructure engineers get up to speed on how to do it and what are the implications.

Our deployments are usually triggered by a Jenkins node; depending on the service we either use Puppet, SaltStack, and/or Ansible to update individual or groups of nodes, or we update our AMIs and create new autoscaling groups for immutable deployments. We have different types of deployments for new and old services, and this has been shown to be largely ineffective as we need to maintain automation, docs, and monitoring for something that should be unified.

We are currently rolling out blue/green deployments for some of the core services, and we intend to implement the same for every core and supporting service.

## Automated Testing

Besides unit test coverage on every project, we have multiple functional test suites that run in every environment; we run it on a staging environment before we deploy to production, and we run them again in production after finishing a deployment to ensure that everything works.

The highlights:

- We have thousands of unit tests in different projects.

- We use Pingdom probes that run every minute to check core functionality.

- We use a mix of Selenium and CodeceptJS-based functional tests before and after every deployment. The functional test suites test different API endpoints, authentication flows, identity providers, and much more.

<include src="TweetQuote" quoteText="Besides unit test coverage on every project, we have multiple functional test suites that run in every environment: staging before deploying to production and again in production after finishing deployment."/>

## CDN

Until 2017 we ran our own, custom-built CDN using NGINX, Varnish, and EC2 nodes in multiple regions. Since then, we transitioned to CloudFront, which has given us several benefits that include:

- More edge locations, which means less latency for our customers.

- Lower maintenance costs.

- Easier configuration.

There are a few downsides, like the fact that we need to run Lambdas to perform some configurations (like adding custom headers to PDF files and things like that). Still, the upsides definitely make up for that.

## Extend

One of the features we provide is the ability to run custom code as part of the login transaction, either via [_authentication rules_](https://auth0.com/docs/rules/current) or [_custom database connections_](https://auth0.com/docs/connections/database/custom-db). These features are powered by [_Extend_](https://goextend.io/), an extensibility platform that grew out of Auth0 and is now being used by other companies as well. With Extend, our customers can write anything they want in those scripts and rules, allowing them to extend profiles, normalize attributes, send notifications, and much more.

We have Extend clusters specifically for Auth0; they use a combination of EC2 auto-scaling groups, Docker containers, and custom proxies to handle requests from our tenants, processing thousands of requests per second and responding fast to variations of load. For more details about how this is built and run, check out this post on [how to build your own serverless platform](https://tomasz.janczuk.org/2018/03/how-to-build-your-own-serverless-platform.html).

## Monitoring

We use a combination of different tools for monitoring and debugging issues:

- CloudWatch

- DataDog

- Pingdom

- SENTINL

The vast majority of our alerts come from CloudWatch and DataDog.

We tend to configure CloudWatch alarms via TerraForm, and the main monitors we keep on CloudWatch are:

- HTTP errors from our main load balancers.

- Unhealthy instances in a target group.

- SQS processing delays.

CloudWatch is the best tool for alarms based on AWS-generated metrics (like ones from load balancers or autoscaling groups). CloudWatch alerts usually go to PagerDuty, and from PagerDuty to Slack/phones.

DataDog is a service we use to store and act on time-series metrics. We send metrics from Linux boxes, AWS resources, off-the-shelf services (like NGINX or MongoDB), and also custom services we have built (like our Management API).

We have many DataDog monitors. A few examples:

- Increase in response times in `$service` on `$environment`.

- Running out of space on `$volume` in `$instance` (`$ip_address`).

- Issue with `$process` on `$environment` / `$host` (`$ip_address`).

- Increase in processing time for `$service` on `$environment`.

- NTP drifting off / clock issue on `$host` (`$ip_address`).

- MongoDB replica-set change on `$environment`.

As you can see from the examples above, we have monitors on low-level metrics (like disk space) and high-level metrics (like MongoDB replica-set change, which alerts us if there was a change in the primary node definition, for example). We do much more and have some pretty sophisticated monitors around some services.

DataDog alerts are pretty flexible in their outputs and we usually send them all to Slack, sending to PagerDuty only those who should "wake people up" (like spikes of errors, or most things that we are sure that are having an effect on customers).

For logging we use Kibana and SumoLogic; we are using SumoLogic to record audit trails and many AWS-generated logs, and we use Kibana to store application logs from our own services and other "off-the-shelf" services like NGINX and MongoDB.

## The Future

Our platform evolved quite a bit in order to handle the extra load and the huge variety of use cases that are important to our customers, but we still have more room for optimizations.

Not only our platform grew, but our engineering organization increased in size: we have many new teams building their own services and are in need of automation, tooling, and guidance around scalability.
With that in mind, these are the initiatives in place for us to scale not only our platform but also our engineering practice:

- Build a Platform, PaaS style: As mentioned before, today we have different automation and deployment flows; this causes confusion and creates a barrier of entry for engineers as it's hard to experiment and scale up without touching too many repositories. We are developing a PoC for a platform (currently running on top of ECS) in which engineers can configure a YAML file and just deploy it to get computing resources, monitoring, logging, backups, and much more. All of that without having to configure it explicitly. This effort is in an early stage and might still change a lot (EKS?). However, we feel we are taking the right direction given our growing size and scalability constraints.

- Implement smoke tests for every new pull request: besides unit testing (that already runs on each new PR), we want to run integration tests on ephemeral environments wherever that's possible.

- Centralize our logging solution into just one provider. This might mean moving away from Kibana and using just SumoLogic, but we still need to evaluate feature set, data volume, and more.

- Automate metrics: Too much of our metric story is manual now: adding metrics-related calls to the code while deploying, and building dashboards and monitors using the DataDog interface. If we use a standard format and naming, we could do things like building dashboards/monitors automatically, extracting metrics from logs instead of explicitly adding calls to the code, and more.

- Ensure we have auto-scaling and blue/green deployments on every core service. This should come out-of-the-box from our new Platform, but while that is being built and tested we need to improve the scaling/deployment/rollback story for the core services that are still lacking in that regard.

<include src="asides/AboutAuth0" />

Auth0 Architecture: 5 Years In

37590801?s=460&v=4

A software engineer who dreams about non-electric sheep and autonomous vehicles and likes to champion security.

Software Engineer

Dan Arias

Learn how to build a mature service architecture for high availability by creating its topology progressively.

Progressive Service Architecture At Auth0

saravana-kumar

Guest Author

Saravana Kumar

Learn how utilizing identity solutions like Auth0 allows your engineers to focus on what matters most to your company - developing your SaaS product's unique features.

<div class="alert alert-info alert-icon">
 
 Forrester Consulting analysis determines that using Auth0 can yield a 548% ROI and $3.7M in identity-related savings. Read the full report: <a href="https://resources.auth0.com/forrester-tei-research-case-study/">Total Economic Impact of Auth0</a>.
</div>

---

**TL;DR**: In this article, we will explore some of the key technical considerations you have to make while building highly-scalable SaaS products. The idea is to show that it's better to use reliable PaaS (Platform as a Service) vendors available in the market instead of utilizing your valuable engineering resources on infrastructure requirements. As you will learn, this will make your engineers available to focus on what matters the most, the key features of your project.

<include src="TweetQuote" quoteText="Relying on battle-tested solutions allows your engineers to focus on what matters most to your company — the unique features of your SaaS products."/>

## Introduction

Before going into the details, I need to give you a short background of Document360, which will help you to understand the context of the article better.
 
[Document360 is a self-service knowledge base product](https://document360.io/) that helps you to create public or private product documentation. Take as an example [Auth0's own documentation](https://auth0.com/docs). Using Document360, you can easily build such product documentation.

![Document360 logo](https://images.ctfassets.net/23aumh6u8s0i/1EvAgNetdKQ85x3DI6FOtz/7c207131cb5d55a5cc6ad5b05cd9450d/document360_logo)
 
When the idea for Document360 was conceived at the end of 2017, one of the key decisions we have made was to build a solution to scale to unlimited users without any architectural changes. This means that the product has to serve 500 customers today and it shouldn't suffer big architectural changes to serve 500,000 customers in a few years down the line.
 
Architecturally, this requires a different level of thinking and infrastructure requirements when you are designing a system that's capable of 500 customers and 500k customers. You need to be careful you are not over-engineering the solution, which will end up being difficult to manage and very expensive.
 
For example, let's say you have the requirement to pick a video file from a storage location to do some processing (like creating a transcript) and to store the result in a third-party storage location. When you are looking at processing 5 video messages per day, the solution is pretty simple, but imagine if you are YouTube or Wistia and need to process 100,000+ videos per day. Then, this single piece of functionality will require significant architecture and infrastructure investment.
 
If you do not plan correctly and decide to build scalable components yourself, your valuable software engineering time will be spent on creating basic versions of those functionalities. The cloud Platform as a Service (PaaS) market has evolved significantly in the past 5-8 years and, today, there is a specialized offering for each piece of the puzzle. It might be a smart move to pick the required Lego blocks and assemble it together rather than building everything yourself.

## Core Services for Cloud Scaling

For Document360, there are five core pieces of the product that required cloud-scale thinking:

1. the Identity Management (user authentication) system;
2. an user-facing web application;
3. technical-writers-facing web application;
4. a search engine;
5. and data storage.

Before going into identity management, which is the core of this article, let's quickly take a brief look at the background about other scalable parts of the architecture.

### User-Facing and Technical-Writer-Facing Web Apps
 
These web applications are straightforward requirements. Both applications should be scalable, reliable, and fast to provide a great experience to both end customers and technical writers. We decided to use [Microsoft Azure Web Apps](https://azure.microsoft.com/en-gb/services/app-service/web/) as the core front-end facing technology with [Azure Traffic Manager](https://azure.microsoft.com/en-gb/services/traffic-manager/) to route the traffic to the closest location.

### Search Engine
 
For any self-service knowledge base product, a good search engine is the key. These days, people do not navigate through your structure, they will just go and hit that big search box to look out for answers. We need to make sure the search feature is robust and, again, scalable when 1000's of customers arrive. There is no point in building this in-house. As such, we decided to go with [Algolia as our search provider](https://www.algolia.com/).

### Data Storage
 
A document management product like Document360 is full of text documents, so we need a reliable storage (database) with fast read and write capabilities and that can also scale as we grow. For this feature, we decided to go with [MongoDB cloud as our data storage provider](https://www.mongodb.com/cloud).

## Identity and Access Management with Auth0

Now, let's get a bit deeper into the main part of this article: ["Identity Management as Service"](https://auth0.com/learn/cloud-identity-access-management/). Document360 got various types of users logging into the system. When you are building a public facing self-service knowledge base, your draft writers and editors need to safely login to the system to produce relevant content. In some scenarios, where the customer decided to keep their self-service knowledge base private to the organization, then the whole organizations need to securely login in.

![Managing Identity with Auth0](https://images.ctfassets.net/23aumh6u8s0i/56TDJXutAc7DPAGwcknHY9/0ce17a9352d60d4a5382acf67f55c2e4/p-dashboard-6fc11ba51b)

Out of the five core areas of Document360, getting the initial authentication part in a secure, reliable, and scalable part is the most important aspect. For this, we decided to go with [Auth0 to provide the initial login and user authentication for our product](https://auth0.com/).

There are few reasons why we decided to use Auth0 instead of custom building our own identity providers:

- **Enterprise-Ready**: Even though capturing credentials (username/password), validating them against your database, and issuing a validation token might look like a simple task, soon, everything get complicated when you look at the scale factor. It would have taken months for our developers to build [an identity solution with the B2C features that Auth0 provides](https://auth0.com/b2c-customer-identity-management). More than that, it would take years to reach the level of quality and security of what Auth0 can provide.
- **Hack-Proof**: These days, when you are building a SaaS product like Document360, you need to worry about the DDOS attack and identity hacking. Every now and then, there is something on the news saying that one of the top websites was hacked. As such, it's not worthing the risk for us to do it ourselves. A product like Auth0 deals with billions of identity validation every day will be [better equipped and more secure than any in-house solution that we come up with](https://auth0.com/security). Enabling functionalities like [breached password detection](https://auth0.com/breached-passwords) enables that our users data is secure..
- **Trivial to add more providers**: Initially, we are starting with a standard username/password for identity verification. However, our plan in later stages is to support more identity and [single sign on (SSO)](https://auth0.com/single-sign-on) capabilities. By using Auth0, we can rest assured that, when the time comes, we will be able to [easily support other identity providers like Azure Active Directory, LDAP, and social identities (like Facebook, Google, LinkedIn etc)](https://auth0.com/docs/identityproviders). With Auth0, this is more of a trivial configuration change rather than spending weeks building support for new identity providers.
- **Low cost**: If we put together the total investment required to build and manage an identity solution, we would be amazed. The effort and the investment will all add up pretty quickly because you will need specialized engineering resources blocked just for this feature and for the infrastructure requirement. By using Auth0, we save money by simply [paying based on our usage](https://auth0.com/pricing). That is, we pay more when we make more money.
- **Rules trigger on identity**: This is one of the cool features we take advantage of at Auth0. We have requirements like, whenever a new user signup, we need to notify the sales team. With Auth0, we achieved this by plugging in [the Zapier integration after a successful authentication](https://auth0.com/rules/zapier-new-user). This was trivial.
- **Single Sign On**: In the Document360 case, we have two different web portals. One for where the Technical writers produce knowledge base content and another one for user/customer facing website (public or private). When the customer decides to go private, then [a seamless Single Sign On experience](https://auth0.com/docs/sso/current) is required between both the portals. This is achieved seamlessly using Auth0.

<include src="TweetQuote" quoteText="By using Auth0, we save money by simply paying based on our usage. That is, we pay more when we make more money."/>

## Summary

If you are building a SaaS product today, you really shouldn't think about building things yourself. The modern way of building stuff is all about assembling the best solutions in the industry together and constructing a solid application. That's exactly what we have done in our case. The core parts of the business are running with the help of great products in the market and we act more or less like an orchestrator to assemble and create a beautiful music out of all these talents.

<include src="asides/AboutAuth0" />

## About the Author

Saravana Kumar is the Founder of [Document360](https://document360.io/), a product that helps your team create, collaborate, and publish a self-service knowledge base for your software with ease. Saravana is passionate about technology and he holds the famous Microsoft Most Valuable Professional title for 12 years in a row. He founded and scaled three other successful enterprise products ([BizTalk360](https://www.biztalk360.com/), [Serverless360](https://www.serverless360.com/) and [Atomic Scope](https://www.atomicscope.com/)) in the last 7 years.

"scalability"