KDPika Licensing
Sign inStart freeWhat you will do
Choose one programming language and one place where access is enforced.
| App type | Where the check belongs |
|---|---|
| Desktop | Inside the app; valuable online operations also need server authorization. |
| Web / SaaS backend | On your authenticated server, before protected work. |
| CLI / developer tool | In the tool process, with private per-user state. |
| Plugin / extension | In its trusted process; a browser extension needs a backend for valuable server actions. |
| Just issue keys | Use manual issuance or a verified store route in Stage 12; no SDK is required to send a key. |
Four official SDKs are distinct from ten REST projects. JavaScript here means Node.js or Electron main, not a browser SDK. Unlisted languages use HTTPS/JSON and a conforming signature verifier.
Expected result
Your chosen language follows you through code examples and links.
If it does not work
Language and app-type choices organize examples; they do not create unsupported framework integrations. No browser-only check protects a SaaS backend.
Stage checklist
- I know where my protected action runs.
- I chose an official SDK or accepted the extra REST verification work.
Next steps
Continue to Stage 6: Install and configure
You are here: Stage 5 of 14.