Software Developer at a hospitality company with 11-50 employees
Real User
Top 20
Jul 7, 2026
My main use case for FusionAuth is maintaining a highly congruent multi-cloud and enterprise platform. We are currently running a distributed microservice architecture and process high-volume security vulnerability data across AWS and GCP. Because of the sensitive nature of the data, our system requires absolute control over the data and strict deployment isolation. That is why we chose FusionAuth's self-hosted and dedicated deployment models. I wanted to offload identity management from our core logic to solve two specific challenges: B2B multi-tenancy with strict RBAC and machine-to-machine authentication, since our backend heavily relies on decoupled micro-background workers. A specific example of how FusionAuth is used day-to-day in my setup is that we have deployed the multi-cloud enterprise platform, where we scan the cloud accounts of our users to handle B2B multi-tenancy for our clients and machine-to-machine authentication for our decoupled microservices. Whenever our background workers scan results through BullMQ, which is our messaging queue, they need to process cross-cloud scan results to our main server backend. We need a highly secure way to authenticate those internal servers, and FusionAuth centrally issues these M2M tokens while handling the strict RBAC policies we define.
Find out what your peers are saying about FusionAuth, Okta, One Identity and others in Customer Identity and Access Management (CIAM). Updated: July 2026.
Customer Identity and Access Management (CIAM) enhances security and user experience by efficiently managing customer identities. It ensures controlled access to resources while protecting customer data.Organizations leverage CIAM to provide seamless and secure access to digital services, safeguarding user identities and data against unauthorized access. This technology is crucial for businesses looking to build trust with customers, manage authentication, and personalize user...
My main use case for FusionAuth is maintaining a highly congruent multi-cloud and enterprise platform. We are currently running a distributed microservice architecture and process high-volume security vulnerability data across AWS and GCP. Because of the sensitive nature of the data, our system requires absolute control over the data and strict deployment isolation. That is why we chose FusionAuth's self-hosted and dedicated deployment models. I wanted to offload identity management from our core logic to solve two specific challenges: B2B multi-tenancy with strict RBAC and machine-to-machine authentication, since our backend heavily relies on decoupled micro-background workers. A specific example of how FusionAuth is used day-to-day in my setup is that we have deployed the multi-cloud enterprise platform, where we scan the cloud accounts of our users to handle B2B multi-tenancy for our clients and machine-to-machine authentication for our decoupled microservices. Whenever our background workers scan results through BullMQ, which is our messaging queue, they need to process cross-cloud scan results to our main server backend. We need a highly secure way to authenticate those internal servers, and FusionAuth centrally issues these M2M tokens while handling the strict RBAC policies we define.