Choose a Product

Swig has four product surfaces. Choose the one that matches how your app will integrate.

Quick routing

If you are trying to…	Start here
Understand the on-chain protocol and repo layout	Swig Protocol
Integrate directly with Swig wallets from TypeScript or Rust	Swig Protocol SDK
Prepare wallet operations behind an API key and sign them client-side	Swig Developer SDK
Add OAuth, email OTP, or SMS OTP login flows	Swig IDP SDK

Product map

Swig Protocol

The on-chain wallet system in swig-wallet.

• Use it when you need to understand permissions, sessions, recovery, or program behavior.
• Start at Protocol.

Swig Protocol SDK

Direct TypeScript and Rust integrations with the protocol.

• Use it when your app talks to Swig wallets directly and controls its own authority or signing flows.
• Start at Protocol SDK.

Swig Developer SDK

Hosted transaction preparation through the developer portal and @swig-wallet/developer-sdk.

• Use it when you want the backend to prepare wallet creation, transfers, swaps, or recovery flows and the client only signs what it must sign.
• Start at Developer SDK.

Swig IDP SDK

Login-provider SDKs in swig-idp-sdk.

• Use it when you need OAuth or OTP sign-in that creates Swig sessions for web or Expo apps.
• Start at IDP SDK.

Relationship between the four

• The Swig Protocol is the on-chain foundation.
• The Swig Protocol SDK integrates with that protocol directly.
• The Swig Developer SDK uses hosted backend services to prepare and operate on Swig wallets through API-key access.
• The Swig IDP SDK handles end-user identity and session bootstrap for login-provider flows.