When to use each
Stay on Nylon-managed apps
You are prototyping, you have not started platform review, or you publish for a handful of your own brands.
Bring your own keys
Your users must authorise your brand, you need throughput that is not shared, or compliance requires a direct platform relationship.
How it works
1
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.
2
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.
3
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.
4
Publish
Requests are signed with your app’s token, so platform quota is counted against you rather than shared across tenants.
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.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.