Embedded vs hosted login

This sign up and integration guide includes instructions on how to integrate Frontegg using hosted login. Instead of hosted, you can use embedded login.

Embedded and hosted login both come with the same pre-built but highly customizable login box and robust set of authentication functionality.

The main difference is that embedded login allows you to embed the login box into your code, whereas with hosted login you host the login box on Frontegg servers.

With embedded login, you import one of our software packages into your application and then use components, links, and subdomains to handle authentication for you with. You actually embed the login box into your code. When your customers click a button on your application to log in or sign up, your application handles authentication.

📘

Embedded Login Limitations

Embedded login operates using cross-site authentication using cross-site http-only cookies. For this to operate flawlessly on modern browsers (which block 3rd party cookies by default) it is required to set up a custom domain on the Frontegg workspace settings.

With hosted login, Frontegg hosts the authentication. When your customers click a button on your application to log in or sign up, your application redirects the user to the login page hosted by frontegg. The user is then authenticated and redirected using Open ID connect protocol back to your application.

This mode is extremely useful if your application is protected using standard API gateways such as Kong or NGINX

An additional very popular use case is when the login dialog is used by multiple applications and you want to share the user pool. In these use cases, hosted login will be a perfect choice.

Want to move forward?

Read our guides to learn how to add Frontegg to your app.