# RiskOS™ SDK Overview

RiskOS™ provides two client SDK families that feed signals into your evaluation workflows. Both support iOS, Android, React Native, and Web, and both return a token your backend includes in RiskOS™ API requests.

## Choose your SDK

[Predictive DocV SDKs](https://help.socure.com/riskos/docs/docv-sdks#/)  
Capture and verify government-issued identity documents and selfies through a built-in camera UI. Use when your workflow needs document or biometric verification.

[Digital Intelligence SDKs](https://help.socure.com/riskos/docs/digital-intelligence-sdks#/)  
Collect device and behavioral signals through transparent background fingerprinting. No UI is presented to the consumer. Use to add device risk to any workflow.

## Which SDK do you need?

| If you need to… | Use |
| --- | --- |
| Verify a driver's license, passport, or other identity document | Predictive DocV SDKs |
| Capture a selfie for biometric comparison | Predictive DocV SDKs |
| Assess device reputation, location, or VPN usage in the background | Digital Intelligence SDKs |
| Add a session risk signal without showing any UI to the consumer | Digital Intelligence SDKs |

Many workflows use both: Digital Intelligence runs on every session, while your app launches DocV when a document check is needed.

## Before you integrate

- Get your SDK key from the **Developer Workbench** in the RiskOS™ Dashboard. See [API and SDK Keys](https://help.socure.com/riskos/docs/integration-guide-authentication#/).
- Review the [Integration Guides](https://help.socure.com/riskos/docs/integration-guides#/) for your use case to see how the SDK fits into the end-to-end evaluation flow.
- Check the [Socure SDK Release and Maintenance Policy](https://help.socure.com/riskos/docs/maintenance#/) for version support timelines before you pin a version.