Connecting Users

BlueNexus provides flexible ways for applications to connect users to the BlueNexus platform, depending on how you manage authentication in your app.

There are three main integration models, each suited for different levels of control and user experience:

1. "Sign In" with BlueNexus (Use BlueNexus accounts as the authentication solution for your app)

2. "Connect" BlueNexus (Allow your existing users to connect their BlueNexus accounts in your app)

3. White-Label Integration (Programmatically create and manage BlueNexus accounts for your users)

This guide explains each model, their typical use cases, and example implementation patterns.

Important: Learn about Account Sovereignty to ensure you select the integration model most appropriate for your level of regulatory compliance risk.

1. "Sign In" with BlueNexus

Use BlueNexus as your identity and authentication provider

In this model, BlueNexus handles all user authentication for your application. You add a “Sign in with BlueNexus” button to your login page, and BlueNexus manages user identities, credentials, and OAuth tokens. This is similar in function to "Sign in with Google".

Use Case

You want to delegate all user management, authentication, and identity storage to BlueNexus. Your users log in directly through BlueNexus, and your application receives tokens representing their identity and permissions.

Benefits

• Simplifies user management — BlueNexus stores credentials and handles security.

• Users can reuse existing BlueNexus accounts across multiple integrations.

• Fastest setup for new apps or apps without an existing authentication system.

• Users retain full sovereignty of their account and can revoke / delete their account from your application at any time.

Learn how to implement "Sign In" with BlueNexus.

2. "Connect" BlueNexus

If your app already has its own user authentication system (email/password, Google login, etc.), you can allow users to connect their BlueNexus account from a settings or integrations page.

In this model, your application owns the user identity, but BlueNexus is connected to provide AI and service integrations.

Use Case

You already have a user base and want to give them access to BlueNexus-powered features without changing your login system.

Benefits

• Users maintain their own accounts and credentials within your app.

• Adds BlueNexus capabilities as an optional integration.

• Simple OAuth 2.0-based setup with minimal backend work.

• Users retain full sovereignty of their account and can revoke / delete their account from your application at any time.

Learn how to implement "Connect" BlueNexus.

3. White-Label Integration

In the white-label model, your app creates and manages BlueNexus accounts behind the scenes for your users. Your users never see or interact with the BlueNexus login page — all communication happens server-to-server.

This is ideal for deeply integrated applications that want to embed BlueNexus functionality natively, while keeping the user experience fully branded.

Use Case

You want BlueNexus to power AI and integrations inside your platform, but your users should never leave your environment.

Benefits

• Seamless, branded user experience — no external redirects.

• Fine-grained control over user data and account creation.

• Best suited for large platforms embedding BlueNexus as a backend service.

Learn how to implement White-Label Integration.