Use case

Social login without registering OAuth apps

AscendKit's OAuth proxy lets you ship social login without registering your own OAuth apps for each provider. Shared OAuth credentials are brokered through the proxy, so Google, GitHub, and LinkedIn sign-in work immediately, and you can switch to your own provider apps later when you want full branding.

How it works

  1. 1. Enable a provider
    Turn on Google, GitHub, or LinkedIn in the portal — no OAuth app registration required to start.
  2. 2. Ship social login
    Drop in the social-button components; sign-in is brokered through the OAuth proxy using shared credentials.
  3. 3. Bring your own apps later
    When you want fully branded consent screens, swap in your own provider credentials without changing your app code.

FAQ

Do I have to create a Google or GitHub OAuth app to start?

No. The OAuth proxy uses shared credentials so social login works immediately. You can register your own apps later for branded consent screens.

Which providers are supported?

Google, GitHub, and LinkedIn are supported today, both through the OAuth proxy and with your own provider credentials.

Start with one API key

Auth, email, surveys, and journeys share one user record, so you ship this without stitching vendors together.

Start free