---
slug: "/docs/v1/integration-guide/choose"
title: "Choose your language and app type"
description: "Stage 5: choose your language and app type with a clear outcome, verification steps and one next action."
section: "Integration Guide"
order: 20
audience: "all"
level: "beginner"
last_updated: "2026-10-20"
version: "v1"
related: []
draft: false
layout: "guide"
---
## What you will do
Choose one programming language and one place where access is enforced.
Choose Desktop app, Web / SaaS backend, CLI tool, Plugin / extension, or manual issuance. Select your language at [Choose your path](/docs/v1/start/choose-your-path). The guide supports four official SDKs and ten REST client routes.
| 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](/docs/v1/start/glossary#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](/docs/v1/start/glossary#official-sdk) 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](/docs/v1/integration-guide/install)