Auth that gets crypto.
Wallets and the chats your users actually use.

Every other platform makes you pick.

The wallet-first auth platforms ship Sign-In With Solana but skip the consumer providers your community already lives on. The consumer-first platforms ship Discord and X but treat wallets like a side feature. You end up either telling your crypto-native users to make an email account or telling your mainstream users to install a wallet.

Synq is the only identity platform built around the assumption that those are the same users.

Every method crypto communities actually use

Pick which methods to enable per Brand. Reorder them in the modal so the highest-converting option shows up first. Every method emits the same standards-compliant OIDC tokens — your backend code never branches on which one the user picked.

How Synq compares for web3

Live snapshot of which platforms ship each method today. Synq is the only identity platform with the full web3 + consumer + enterprise matrix on a real OIDC issuer.

Both competitor and partner — and that's by design.

Matrica is the closest match to Synq on the consumer-web3 method matrix. It's also a provider Synq integrates with — "Sign in with Matrica" is one of the methods on every Synq modal. The right way to think about it: Matrica is the consumer profile(the source of truth for a user's linked Solana identities). Synq is the developer platform (the OIDC issuer your code talks to, the multi-Brand console your team operates, the audit log your security team queries). Most web3 teams need both — and they compose cleanly.

One profile, every wallet they own.

Most platforms make users pick a single wallet and treat that address as their whole identity. Synq treats wallets as connections on a single user — link the hot wallet, link the cold wallet, link the trading wallet. Your app sees the union of all of them on every sign-in. Onchain decisions that depend on holdings (gated drops, premium tiers) get the full footprint, not a single-address snapshot.

SDKs that match the stack

React for the web, React Native for mobile, the Solana Mobile bridge for Android dApps, and a Node verifier you can drop into any backend. Every method works the same way across all five — wallet sign-in just flips the provider string.

import { SynqProvider, useSynq } from '@synqid/react'
import { SignIn } from '@synqid/react/ui'

export default function App() {
  return (
    <SynqProvider
      issuer="https://api.synq.id"
      clientId={import.meta.env.VITE_SYNQ_CLIENT_ID}
      redirectUri={`${window.location.origin}/auth/callback`}
      theme="dark"
    >
      <Root />
      <SignIn />          {/* shows every method your Brand enabled */}
    </SynqProvider>
  )
}

function Root() {
  const { requestSignIn, signInWithWallet } = useSynq()
  return (
    <>
      <button onClick={() => signInWithWallet()}>Sign in with Solana</button>
      <button onClick={() => requestSignIn()}>Pick a method</button>
    </>
  )
}

No proprietary SDK. No lock-in. No exit cost.

Synq is a full OpenID Connect provider. Wallet sign-in goes through the same standards path as Google sign-in — your backend verifies RS256 access tokens against JWKS with any JWT library. Refresh, revocation, JWKS rotation, the discovery doc, the introspection endpoint: all spec-compliant.

Replacing Synq would be a JWKS swap and a DNS change. Not a rewrite. That's the kind of freedom that should be built into the platform layer your product depends on, and it's exactly what wallet-first proprietary widgets don't give you.

Built for the apps your community ships