Certificate Pinning SDKs for iOS, Android, Flutter and React Native
Integrate in Under 5 Minutes
One SDK per platform and a CLI for your pipeline, all fed by the same signed configuration. Pick your platform below; the developer documentation is the integration reference and is kept current with every release.
Choose Your Platform
Requirements and package coordinates at a glance. Each card links to the integration documentation, the API reference and the source.
iOS and macOS
TrustPinKit 6.3
- Requirements
- iOS 15+, macOS 13+, watchOS 8+, tvOS 15+, visionOS 2+. Swift 6.1, Xcode 16.3 or newer.
- Install
- Swift Package Manager: github.com/trustpin-cloud/swift.sdk. CocoaPods: TrustPinKit.
- Works with
- URLSession delegate, Alamofire adapter, system-wide URLProtocol.
Android and JVM
cloud.trustpin:kotlin-sdk 6.3
- Requirements
- Android API 25+, Kotlin 2.3.0+. JVM 11+ (hardened JAR on request).
- Install
- Maven Central: cloud.trustpin:kotlin-sdk:6.3.0, plus the trustpin-okhttp and trustpin-ktor adapters.
- Works with
- OkHttp, Retrofit, Ktor (OkHttp engine), or any client that takes an SSL socket factory.
Flutter
trustpin_sdk 6.3
- Requirements
- iOS 15+, Android API 25+, macOS 13+. Bundles the native iOS and Android SDKs.
- Install
- pub.dev: trustpin_sdk ^6.3.0.
- Works with
- Dio interceptor, pinned http client, validateConnection for custom transports.
React Native
@trustpin/react-native 6.3
- Requirements
- React Native 0.85+ (New Architecture), iOS 15+, Android API 25+, Node 22.11+.
- Install
- npm: @trustpin/react-native. Expo config plugin, or one native init call in bare projects.
- Works with
- fetch and XMLHttpRequest, validated natively before any JavaScript runs.
CLI
trustpin-cli 6
- Requirements
- macOS and Linux binaries (x64 and arm64). Homebrew tap trustpin-cloud/trustpin.
- Install
- brew tap trustpin-cloud/trustpin, brew trust trustpin-cloud/trustpin, brew install trustpin-cli; or download the binary.
- Works with
- GitHub Actions, GitLab CI, Jenkins, Azure DevOps, cron: refresh-certs, sign, jws --verify.
How does integration work?
The same four steps on every platform. The credentials your app ships are identifiers and a public key; the private key that signs your pin set never leaves the console or your own key store.
- 1
Create a project
Sign up, create a project, choose cloud-managed keys, Bring Your Own Keys or FIDO-protected keys, and add the domains to protect.
- 2
Publish the pins
Add pins in the dashboard or let the CLI stage them from the live certificate and Certificate Transparency, then sign and publish.
- 3
Ship the credentials file
Add the project's organization ID, project ID and public key to the app as a native config file. None of the three is secret.
- 4
Initialise and wire the client
One setup call, then the delegate, adapter or interceptor for your HTTP client. Every request is pinned inside the TLS handshake.
Step-by-step in the docs: project setup and deployment.
New to certificate pinning?
Read what certificate pinning is, why rotation breaks static pins, and what a dynamic pin set changes, then come back here for your platform.
Need more help?
The documentation covers project setup, every SDK and CLI option, embedded configurations for offline first launches, monitoring, troubleshooting and the API.
Ready to secure your apps?
Certificate pinning that mobile and security teams can rely on. Start free, then follow the docs for your platform.