---
title: Framework SDKs
description: Choose a Sudomimus framework SDK for server-side web login and sessions.
editUrl: true
head: []
template: doc
sidebar:
  order: 1
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

import { CardGrid, LinkCard } from "@astrojs/starlight/components";

Framework SDKs adapt Sudomimus Connect callbacks and the Session lifecycle to a framework's server routes, cookies, redirects, and request objects. They build on the API SDKs and use Connect directly. For other runtimes or direct API calls, [choose an API SDK by language](/en-us/sdk/overview/#api-sdks-by-language).

<CardGrid>
<LinkCard title="Next.js App Router" description="Route handlers and Server Component session access." href="/en-us/frameworks/nextjs/" />
<LinkCard title="React Router Framework Mode" description="Actions, loaders, and server-side session access." href="/en-us/frameworks/react-router/" />
<LinkCard title="Nuxt Node/Nitro" description="Nitro server routes and server-side session access." href="/en-us/frameworks/nuxt/" />
<LinkCard title="Django" description="Django views, sessions, callback handling, and token rotation." href="/en-us/frameworks/django/" />
</CardGrid>

All adapters require a CALLBACK ReturnRule that permits the configured callback URL. Production deployments also need a shared durable credential store; an in-memory store is suitable only for local development.

:::caution[Server-only credentials]
Keep the client-auth private key, refresh tokens, and returned access tokens in server-only modules and storage. Never pass them into browser components or serialize them into client-visible state.
:::

If your framework already has a mature OpenID Connect integration, you can use the [OIDC path](/en-us/oidc/flow/) instead. Use these adapters when you want Sudomimus Connect and its application rules directly.