Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    Product map

    View as Markdown

    This page lists everything Keryn offers and says, for each product, how far along it is. No status here is written by hand. Each one is read from the same two sources as the rest of the site: the capability manifest behind the capability table and the artifact registry behind the download page. When a product’s status changes there, it changes here.

    Keryn is in pre-release, so a status describes a surface, not a promise about every build.

    Status Meaning
    Available In the latest release of that surface, and named by a Keryn Web screen or a CLI command. For an app or a package: its channel is live in the registry.
    Available in part Some of the product is in the latest release of that surface. The line under the product names the rest.
    Preview In pre-release builds or behind a flag.
    Next release On the main branch, not in the latest release.
    Coming The app is built and its channel is not open yet.
    Planned Not built.
    Not offered The app has no channel that Keryn publishes to. The download page gives the reason for each channel.
    Live A page or site you can open now.

    A surface that is not named has nothing stated for it. That is not a plan. The latest CLI release is a pre-release build for design partners; the install page says which builds exist and how to get them.

    • Keryn WebAvailable

      The scanner in a browser tab at keryn.app. Folders and files are read in the tab.

    • Keryn CLIComing

      Scans, policy gates, imports and exports in a terminal or a pipeline.

    • Editor, browser and desktop appsKeryn for VS Code, Keryn for JetBrains, Keryn for Chrome, Keryn for Firefox, Keryn Desktop, Keryn Container: ComingKeryn for Zed, Keryn Action: PlannedKeryn for Safari: Not offered

      The same engine in VS Code, JetBrains IDEs and Zed, in Chrome, Firefox and Safari, as a desktop app, as a container image and as a GitHub Action.

    • SDK, MCP server and skillsKeryn SDK, Keryn MCP, Keryn Skills: Available

      Thin clients that carry no engine: the Cloud API client, the MCP server and the agent skills.

    • Keryn CloudKeryn Cloud: Available in part

      The optional hosted service: accounts and organizations, scans of an address you type, the hosted MCP endpoint, the audit trail, data export and deletion.

      Keryn Cloud, preview: Enterprise single sign-on and directory provisioning.

    Every app runs the same engine on your machine or in your pipeline. Keryn Cloud is the one hosted part, and it is optional. Apps and integrations has one row per app.

    • Static analysis (SAST)Keryn Web: AvailableCLI: Available in partEditors: Preview

      Pattern rules and data flow within and across source files, and Forge for compiled code.

      CLI, next release: Forge: analysis of compiled Java and .NET and other artifacts.

    • Dependencies and supply chain (SCA)Keryn Web: AvailableCLI: Available in part

      Lockfile inventory, licences and advisory matching; container images, SBOMs, fix proposals and supply-chain signals.

      CLI, next release: Container images, dependency SBOMs and fix proposals; Supply-chain signals (malicious packages, typosquats, install scripts).

    • SecretsKeryn Web: AvailableCLI: Available

      Committed credentials, redacted in every output.

    • Rules for Terraform that provisions AI services and for GitHub Actions and GitLab CI files, run as part of a scan. There is no separate command.

    • AI-BOM and agent inspectionKeryn Web: AvailableCLI: Available

      The models, SDKs, agents, tools and MCP integrations a repository uses, and its agent, skill and MCP configuration files.

    • Binary and model filesKeryn Web: AvailableCLI: Available

      Evidence from supported binary formats and model files met in a scan.

    • Web and API testing (DAST)Keryn Web: AvailableCLI: Next releaseKeryn Cloud: Available

      Passive checks of a running site, a scan of a target you own, and validated API test suites.

      Planned: Continuous DAST and offensive validation.

    • Keryn RuntimeCLI: Next release

      An agent inside the application: IAST reports where request input reaches a sensitive operation, RASP refuses a listed dangerous operation, and a request filter runs in front of the handler. Everything is off until you turn it on.

    • AI adversarial workbenchPlanned

      Interactive investigation of model behaviour, tool chains and prompt injection.

    Coverage lists what each kind of scan checks, and what Keryn does not do gives the measured limits.

    • Trust graph, policy and decisionsKeryn Web: AvailableCLI: Available

      The trust graph and attack paths, policy gates, the posture assessment, recorded risk decisions and evidence export.

    • Triage with a modelKeryn Web: AvailableCLI: Next release

      A model of your choice proposes a verdict and a summary for each finding. A person decides.

    • Report importKeryn Web: AvailableCLI: Available in part

      Read other scanners' reports into the same findings, outputs and gate, and bind offline evidence to an assessment.

      CLI, next release: Offline evidence import (ModelScan and Promptfoo results bound to an assessment; nothing is executed).

    • AI attributionCLI: Next release

      Which AI coding tools a repository is set up for and which commits declare them, with the evidence for each.

    • ASPMCLI: Next release

      Security posture across applications and over time: snapshots, comparison, an ordered work list and an estate report.

    • Every published rule with its metadata, by pack and taxonomy.

    • EvalsLive

      Measured results of each engine against reference tools and labelled benchmarks, with inputs, denominators and limits.

    • Courses, hands-on labs, flash cards, assessments and verifiable credentials for people who build and defend software that uses AI.

    • Open roles in AI security, security research, architecture, ML and data science, and security leadership, linked to the original posting.

    • The day's application and AI security developments for teams that build with AI.

    • Whether a result is good enough. A status says a product exists on a surface. The evals say how well each engine does and where it falls short.
    • Which build you have. Keryn Web and the installed apps are updated separately. Check the changelog for your build.
    • Anything about a product whose name is not a link. It has no guide on this site yet.