Quasr
  • Introduction
    • Welcome to Quasr
    • Concepts
      • Flexible Authentication
      • User-Centric Privacy
      • Modern Development
    • Terminology
    • FAQs
  • Getting Started
    • Sign up with Quasr
    • Setup your tenant
      • Factor Configuration
      • Enrolling additional factors
      • Test with the Sample Client
      • Understanding Scopes & Scores
      • Setting up an API Client (M2M)
    • Connect your app
      • Hosted Login UI
      • Custom Login UI
      • Embedded Login UI
  • Account Administration
    • Introduction
    • Account & Billing
      • Metrics
    • Tenants
    • Usage & Statistics
    • Security
  • Tenant Administration
    • Introduction
    • Dashboard
    • Tenant Settings
    • Your Security
    • Accounts
      • Tenant Admins
    • Factors
      • Factors and Scoring
      • Username (ID)
      • Identity Provider (IDP)
        • Apple
        • Facebook
        • GitHub
        • Google
        • LinkedIn
        • Slack
      • Time-based One-time Password (TOTP)
      • One-Time Password (OTP)
      • Password
      • Secret
    • Controls
      • Configuration
      • Permissions
      • Consents
      • Rules
    • Attributes
      • Capturing Claims
      • Sourcing Claims
      • Viewing Claims
      • Searching Claims / Users
      • Sharing Claims
    • Extensions
      • Synchronous
      • Asynchronous
    • Tokens
      • Session Token (OAuth 2.0)
      • Access Token (OAuth 2.0)
      • Refresh Token (OAuth 2.0)
      • ID Token (OIDC 1.0)
      • Consent Token
      • Authorization Code (OAuth 2.0)
    • Hosted Login Page
    • APIs
      • Authentication API
      • Management API (GraphQL)
  • Legal
    • Terms of Service
    • Acceptable Use Policy
    • DPA & Subprocessors
  • More Info
    • Standards
    • Security
      • Vulnerability Disclosure
      • Wall of Recognition
    • Support
    • Status
Powered by GitBook
On this page
  • Identity as a Service (IDaaS)
  • How is Quasr different?
  1. Introduction

Welcome to Quasr

Quasr is a SaaS (Software-as-a-Service) company in the cybersecurity space, in particular in Customer Identity & Access Management (CIAM), however we like to refer to Quasr as a Customer Identity & Privacy Platform (CIPP).

Quasr allows developers to add authentication and privacy capabilities to their custom-made software without having to be security experts, while at the same time offering the best user experience (UX) to their end customers.

While Quasr encourages the use of and focuses on Passwordless authentication, it also supports traditional Password authentication.

Identity as a Service (IDaaS)

Identity as a Service (IDaaS) is a cloud-based application delivery model provided by a third-party provider (Quasr) to allow users to authenticate themselves towards an online service provided by IDaaS customers, ensuring that users are who they claim to be and giving them the appropriate access permissions to these online services and resources.

Identity & Access Management (IAM) is usually not a core competency of many businesses and it makes a lot of sense to delegate related tasks to an IDaaS, just like payment is often handled by a third-party payment provider in a very similar manner.

Getting Identity & Access Management (IAM) right, especially the customer- or consumer-facing side of it, which is also understood as Customer Identity & Access Management (CIAM) is key to any business, as friction during a customer on-boarding process can massively effect churn and loss of revenue.

With Quasr, we provide business and developers with the right tools and guides to implement secure and privacy-minded Customer Identity & Access Management (CIAM).

In the end, the consumer benefits from security, transparency and flexibility, giving them the power to consent, or not consent, to data collection by applications as well as the ability to freely choose their preferred authentication methods.

How is Quasr different?

  • focused on developers and DevOps through its API-first approach

  • focused on privacy by properly disconnecting personal data and built-in consent management

  • focused on user experience by allowing customers to bring their own UIs, designing their own user experience with as little as possible restrictions

  • focused on security by being opinionated and providing industry best-practice by default at no additional cost, but also understanding security is a balance with customer-side landscape and hence giving customers sufficient options to tune security to their needs

  • focused on scalability through its modern stateless and serverless architecture

  • EU-based and hosted out of the AWS EU central region (Frankfurt), combined with responsible use of a global CDN for improved performance.

NextConcepts

Last updated 2 months ago