Skip to main content

Overview

The LoginRadius Identity Platform is built to support global enterprise needs for security, scalability, and compliance. A key part of this flexibility comes from the ability to choose the right tenant model and environment setup.

LoginRadius offers both multi-tenant and single-tenant deployments (cloud or on-premise), with the option of private, fully dedicated instances for organizations in highly regulated industries. These deployment models are supported by a globally distributed infrastructure across AWS and Microsoft Azure, ensuring high availability, disaster recovery, and fast response times.

What is a Tenant in LoginRadius?

In the LoginRadius platform, a tenant refers to a logically isolated instance (also known as LoginRadius Sites) of the LoginRadius Platform that contains all the configurations, policies, and data specific to an organization.

  • Each tenant is provisioned with its own dedicated database instance, ensuring strict data separation.

  • A tenant defines the identity workflows, authentication methods, integrations, security features, and branding for that organization.

  • Multiple Tenants(e.g., Development, Staging, Production) can be created to support the full application lifecycle.

This tenant-based architecture ensures that each organization using LoginRadius maintains isolation, security, and control, whether it is part of a multi-tenant or single-tenant deployment.

Data Centers

LoginRadius maintains data centers in the Americas, Europe, and Asia-Pacific, with DNS-level traffic management for:

  • Global load balancing

  • Low-latency performance

  • Automatic failover between regions

Our infrastructure uses active redundancy to ensure service continuity. If one data center becomes unavailable, traffic is automatically redirected to another region or cloud provider within seconds.

To know more about this, refer to the Data Region documentation

Tenant Models

ModelDescriptionIdeal ForBenefits
Multi-TenantShared infrastructure with logical isolationStartups, cost-sensitive deploymentsCost-effective, centralized updates
Single-TenantDedicated app and DB per customerRegulated or customization-heavy enterprisesPredictable performance, stronger isolation
Private DeploymentFully isolated cloud environmentFinance, Healthcare, GovFull control, maximum compliance

Environment Lifecycle

Each tenant can have multiple environments aligned with the software development lifecycle:

  • Development
    Used for early-stage integration, configuration, and API testing. This system provides sandbox capabilities without affecting production data.

  • Staging/Pre-Production
    Mirrors production settings for final validation, performance testing, and quality assurance.

  • Production
    The live environment serves end-users, backed by SLAs for uptime, availability, and security.

Every environment is logically and physically isolated, preventing cross-environment data contamination.

Architecture and Reliability

Disaster Recovery and Failover

  • Redundant servers within each data center prevent downtime during node failures.

  • Data centers within each region act as failovers to each other.

  • In the event of a regional outage, LoginRadius can fail over from Azure to AWS within 30 seconds at the DNS level.

Scalability

  • Auto-scaling ensures servers never exceed 40% load capacity.

  • New servers are automatically provisioned when thresholds are reached, allowing real-time scaling to handle billions of requests per day.

Database Isolation

  • Every customer is provisioned with a dedicated database instance to guarantee strict data isolation.

  • Database backups occur on a defined schedule:

    • Incremental every 6 hours

    • Daily full backups

    • Weekly full backups

Performance

  • Authentication API response times: 50–200 ms at the server level.

  • End-to-end login flow: 250–600 ms, depending on user connection.

  • Global infrastructure ensures requests are routed to the nearest data center for minimal latency.

Choosing the Right Model

  • Multi-Tenant: Best for cost efficiency, startups, or enterprises that want rapid access to features with minimal overhead.

  • Single-Tenant: Suitable for enterprises requiring customization, predictable performance, and stricter compliance controls.

  • Private Deployment: Recommended for organizations in regulated sectors that demand maximum control, isolation, and compliance guarantees.

Best Practices

  • Maintain separate Dev, Staging, and Production environments for safe testing and controlled releases.

  • Align your tenant model with regulatory requirements (GDPR, HIPAA, PCI DSS, etc.).

  • Regularly perform load and failover testing to validate high availability commitments.

  • Continuously monitor API response times and server utilization to plan for scaling.