> ## Documentation Index
> Fetch the complete documentation index at: https://cobalt-55-abhishek.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# SDKs

> Official Refold SDKs for client-side and server-side integration.

Refold provides native SDKs that handle authentication, third-party app interaction, end-user configuration, and integration delivery — so you can ship native integrations without building the plumbing yourself.

This page covers what each SDK does, when to choose it, and where to install it.

## Choose your SDK

<CardGroup cols={2}>
  <Card title="React SDK" icon="react" href="https://github.com/gocobalt/react-cobalt-js">
    **Pre-built UI.** Drop the Refold connect modal and auth flow directly into a React app. The fastest path to a working integration in production.
  </Card>

  <Card title="JavaScript SDK" icon="js" href="https://gocobalt.github.io/cobalt-js/">
    **Headless.** A framework-agnostic client for building a fully custom integration UI in any web app.
  </Card>

  <Card title="Node SDK" icon="node-js" href="https://github.com/gocobalt/cobalt-sdk">
    **Server-side.** Recommended for production: more control, tighter security, and the ability to design the entire end-user experience from your backend.
  </Card>
</CardGroup>

***

## Client-side SDKs

Use a client-side SDK when the integration UX lives in the browser — for example, an in-app "Connect to Salesforce" button that opens a connect modal.

<CardGroup cols={2}>
  <Card title="React SDK" icon="react" href="https://github.com/gocobalt/react-cobalt-js">
    Pre-built React components and a turn-key connect modal. Wire it up in minutes with `<RefoldConnect />`.
  </Card>

  <Card title="JavaScript SDK" icon="js" href="https://gocobalt.github.io/cobalt-js/">
    Headless client for vanilla JS, Vue, Svelte, or any frontend stack. Build the UI you want; the SDK handles auth, tokens, and event firing.
  </Card>
</CardGroup>

**When to pick client-side:**

* You want users to authenticate against third-party apps directly from your frontend.
* You're prototyping or shipping a self-serve integration flow.
* You want the fastest time-to-first-integration.

## Server-side SDK

Use the server-side SDK when integrations are orchestrated from your backend — recommended for production.

<CardGroup cols={1}>
  <Card title="Node SDK" icon="node-js" href="https://github.com/gocobalt/cobalt-sdk">
    Programmatic access to linked accounts, workflows, events, and the rest of the Refold API from a Node.js server. Pairs with whatever frontend you build.
  </Card>
</CardGroup>

**When to pick server-side:**

* You want full control over the connect flow and credential storage.
* You're building enterprise-grade integrations that need server-issued tokens.
* You want to keep API keys off the client and orchestrate workflows from trusted infrastructure.

***

## What's next

<CardGroup cols={2}>
  <Card title="Quick start" icon="play" href="/legacy/quickstart">
    Wire up your first integration end-to-end in five minutes.
  </Card>

  <Card title="API reference" icon="code" href="/legacy/api-reference/overview">
    Full reference for the REST API the SDKs are built on.
  </Card>
</CardGroup>