> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Bring your own keys

> Run OAuth through your own platform app instead of Nylon's.

Every connection runs on **Nylon-managed OAuth apps** by default. There is nothing for you to register with a platform, no review queue to sit in, and token refresh is handled for you. Most teams never change this.

Bringing your own keys (BYOK) swaps the credentials Nylon signs with. Your endpoints, payloads and responses stay exactly the same — the only thing that changes is whose name appears on your users' consent screen and whose quota the requests count against.

## When to use each

<CardGroup cols={2}>
  <Card title="Stay on Nylon-managed apps" icon="circle-check">
    You are prototyping, you have not started platform review, or you publish for a handful of your own brands.
  </Card>

  <Card title="Bring your own keys" icon="key-round">
    Your users must authorise your brand, you need throughput that is not shared, or compliance requires a direct platform relationship.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="Create your platform app">
    Register an app with the network — a Meta app, an X project, a LinkedIn app. Set the redirect URI Nylon gives you and request the scopes for what you plan to publish.
  </Step>

  <Step title="Store the credentials">
    Add the client id and secret from the dashboard. They are encrypted at rest with a per-tenant key and are never returned by the API once written.
  </Step>

  <Step title="Connect accounts as normal">
    Nothing in your integration changes. Nylon runs the OAuth handshake against your app instead of ours, and the consent screen shows your name.
  </Step>

  <Step title="Publish">
    Requests are signed with your app's token, so platform quota is counted against you rather than shared across tenants.
  </Step>
</Steps>

## Per provider, not per account

Credentials are stored per provider. You can run Meta on your own app while LinkedIn stays managed, and change your mind later.

Nylon currently supports custom apps for Meta, X, LinkedIn, Pinterest, Bluesky, TikTok and Google. Meta covers Facebook, Instagram and Threads; Google covers YouTube and Google Business. Bluesky uses its HTTPS client metadata URL instead of a shared client secret. Mastodon remains managed by Nylon because its application credentials are specific to each server.

<Note>
  Removing your credentials falls a provider back to Nylon-managed apps. Existing connections keep working until their token expires, then re-authorise against the managed app on the next connect.
</Note>

Manage credentials from **Settings → BYOK** in the [dashboard](https://www.app.nylon.dev). Only team owners and admins can add, update or remove them.