# Apps and integrations

> Every Keryn surface in one table, what it is for, what leaves your machine, and whether it is released, built but not published, or still in development.

Source: https://keryn.dev/docs/guides/apps/

## Goal

Pick the Keryn surface that fits where you work, and know before you install it what it does with your code, whether it is released, and which guide covers it.

## One engine, many surfaces

Every surface below runs the same scanner and shows the same findings with the same proof levels. They differ in where you meet the result. Almost all of them run on your machine or in your own pipeline, and no surface uploads code or findings to Keryn by default. Two integrations, the GitHub App and the Slack review adapter, talk to third-party services by design; their pages say exactly what crosses that line.

## Availability

| Artifact | Id | Version | Status |
|---|---|---|---|
| Keryn for Chrome | - | 0.5.2 | Coming |
| Keryn CI Templates | - | 0.5.2 | Coming |
| Keryn CLI | - | 0.5.2 | Coming |
| Keryn Container | - | 0.5.2 | Coming |
| Keryn Desktop | dev.keryn.desktop | 0.5.2 | Coming |
| Keryn Editor Configs | - | 0.5.2 | Coming |
| Keryn for Firefox | - | 0.5.2 | Coming |
| Keryn Action | - | 0.5.2 | Planned |
| Keryn for JetBrains | dev.keryn.jetbrains | 0.5.2 | Coming |
| Keryn MCP | - | 0.1.1 | Available |
| Keryn Relay | - | 0.5.2 | Planned |
| Keryn for Safari | dev.keryn.safari | 0.5.2 | Not offered |
| Keryn SDK | - | 0.1.0 | Available |
| Keryn Skills | - | 1.2.1 | Available |
| Keryn for VS Code | - | 0.5.2 | Coming |
| Keryn for Warp | - | 0.5.2 | Coming |
| Keryn Web | - | 0.5.2 | Available |
| Keryn Workbench | dev.keryn.workbench | 0.5.2 | Planned |
| Keryn for Zed | - | 0.5.2 | Planned |

For channel details and verification steps, see [download](https://keryn.dev/download/). The [product map](https://keryn.dev/docs/concepts/products/) shows the whole product line, not only the apps.

## The surfaces

| Surface | Use it to | Guide |
|---|---|---|
| Keryn Web | scan a repository, folder or zip in a tab | [Keryn Web](https://keryn.dev/docs/guides/web-app/) |
| Keryn CLI | scan, gate, export, in a terminal or any pipeline | [Install](https://keryn.dev/docs/start/install/) |
| Keryn Container | run the CLI where only containers are allowed | [CI](https://keryn.dev/docs/guides/ci/) |
| Keryn Desktop | the web scanner in a native window, Deep included | [Desktop](https://keryn.dev/docs/guides/desktop/) |
| Keryn Workbench | team mode of the desktop app: scheduled scans, signed outputs | [Desktop](https://keryn.dev/docs/guides/desktop/) |
| Keryn for VS Code (`keryn.keryn`) | diagnostics, AI-BOM and change view in VS Code, Cursor, Windsurf | [Editors](https://keryn.dev/docs/guides/editors/) |
| Keryn for JetBrains (`dev.keryn.jetbrains`) | findings, AI-BOM tool window and change review in IntelliJ-based IDEs | [Editors](https://keryn.dev/docs/guides/editors/) |
| Keryn for Zed | diagnostics from the language server in Zed | [Editors](https://keryn.dev/docs/guides/editors/) |
| Keryn for Warp | `keryn` commands as Warp workflows | [Editors](https://keryn.dev/docs/guides/editors/) |
| Neovim, Helix, Sublime Text, Emacs, Kate configs | the language server in other editors | [Editors](https://keryn.dev/docs/guides/editors/) |
| Keryn for Chrome (also Edge) | AI stack and trust scan of the page in the current tab; scan a public GitHub repository | [Browser extensions](https://keryn.dev/docs/guides/browser/) |
| Keryn for Firefox (`keryn@keryn.dev`) | the same, in Firefox 140 or later | [Browser extensions](https://keryn.dev/docs/guides/browser/) |
| Keryn for Safari (`dev.keryn.safari`) | the same, in Safari | [Browser extensions](https://keryn.dev/docs/guides/browser/) |
| Keryn Action | the scan as a GitHub Actions step | [CI](https://keryn.dev/docs/guides/ci/) |
| CI templates (GitLab, Azure Pipelines, Jenkins, Bitbucket) | the scan in other CI systems | [CI](https://keryn.dev/docs/guides/ci/) |
| GitHub App | commit-bound pull request checks of what a change adds | [GitHub App](https://keryn.dev/docs/guides/github-app/) |
| Keryn Review for Slack | review recorded security evidence in Slack and request a rerun | [Slack](https://keryn.dev/docs/guides/slack/) |
| Agent skills (`/keryn-review`, `/keryn-diff` and five more), `@keryn/skills` | use the CLI and the MCP server from Claude Code and Codex | [Keryn Skills](https://keryn.dev/docs/guides/keryn-skills/) |
| MCP audit and guard | list the MCP servers your AI clients start, put a policy in front of them | [MCP guard](https://keryn.dev/docs/guides/mcp-guard/) |
| Language server (`keryn lsp`) | one server behind every editor integration | [Editors](https://keryn.dev/docs/guides/editors/) |
| Keryn Cloud | scan a website, a host's AI services or a remote MCP server from Keryn's servers | [Keryn Cloud](https://keryn.dev/docs/cloud/) |

Every row except Keryn Cloud runs on your machine, in your own CI runner, or in your browser tab. Keryn Cloud receives only the address you type, never your code or results.

## What each kind of surface sends

- **Web, Desktop, CLI, container, editors, Warp, Zed, CI adapters**: the scan reads files locally and nothing is sent anywhere. The exceptions are calls you start yourself: fetching the public repository you named from its host, a GitHub token you enter, or a connector button you press. JetBrains' `npx` mode may download a package, and only when you choose that mode.
- **Browser extensions**: the extension requests the page you are looking at, as an anonymous visitor, or the public GitHub repository you named from `codeload.github.com`. Nothing about the visit is reported to Keryn.
- **GitHub Action**: runs on your runner and talks to GitHub only for the outputs you switch on (code scanning upload, comment, commit status).
- **GitHub App**: GitHub delivers pull request events to a server you host, and that server calls the GitHub API to start your workflow and write a Check. The scan itself runs in your Actions runner. Details, including what the Check contains, on the [GitHub App page](https://keryn.dev/docs/guides/github-app/).
- **Slack review adapter**: Slack delivers slash commands to a server you host. A card is posted to a channel only when you enable writes and a person presses **Share in this channel**. Details on the [Slack page](https://keryn.dev/docs/guides/slack/).

The full list of network calls is on the [privacy page](https://keryn.dev/privacy/), and the design rule behind it is [local by design](https://keryn.dev/docs/concepts/local-only/).

## What you just proved

You can name, for any Keryn surface, whether it is released or only built, where it runs and what it may contact. The availability table uses the same artifact registry as the [install page](https://keryn.dev/docs/start/install/).

## Next

- Start in a terminal: [install](https://keryn.dev/docs/start/install/).
- Start in a browser with no install: [Keryn Web](https://keryn.dev/docs/guides/web-app/).
- Gate pull requests: [CI](https://keryn.dev/docs/guides/ci/).
