Skip to content

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

    Partners

    View as Markdown

    Keryn is pre-release. Partnerships start as time-boxed pilots with a written question, success criteria and a decision date. OEM, white label, private label and headless deployments are offered, scoped with you per agreement. Each page below says what exists today and what does not, so nothing is sold as built that is not.

    Read the partner terms, then become a partner or write to keryn@keryn.dev. Nothing is sent to you unprompted.

    Type Who it is for
    Offensive-security platforms Pentest, attack-simulation and attack-path platforms that want source-grounded evidence behind every path.
    Other scan providers SAST, DAST, SCA and AI-security scanners that want an evidence and decision layer, or an engine and feed.
    Agencies, consultancies and MSSPs Consultancies and managed-service providers that run AI and application security reviews for clients.
    OEM and white-label embedders Products that want Keryn analysis inside them, under their own brand where agreed.
    Design partners and pilots Teams shipping AI features, agents or MCP servers who will give written feedback in return for early access.
    Resellers and referral partners Channel partners that resell Keryn credits or introduce customers who buy from Keryn directly.
    Technology and ecosystem integrations CI/CD, ticketing, SIEM, ASPM and identity vendors that want a first-class Keryn integration.
    Training and workforce partners Training platforms and employers that want AI-security engineering content and labs. Exploratory.
    Keryn deployment models Seven deployment models arranged by who operates them. Local, self-hosted and OEM run in the customer or partner environment. SaaS, dedicated cloud, white label and private label run on Keryn Cloud. Headless API access spans both. Dashed borders are partial, dotted are roadmap. Customer or partner operates Keryn operates (Keryn Cloud) Self-hostedCLI + keryn-server on loopback,air-gapped guide OEMengine embedded in a partnerproduct; sales-led Private labelpartner delivers under its nameon Keryn Cloud orgs LocalCLI, desktop, web tab,extensions, CI. Free. Headless / API-only/api/v1 + organisation keys@keryn/sdk, @keryn/mcp, @keryn/skillsCLI --json, SARIF, CycloneDX keryn-export/1opt-in file; import into a KerynCloud org. Nothing uploads by default. SaaSaccount UI, API, credits,SSO, SCIM Dedicated / private cloudsingle-tenant Keryn Cloud White labelpartner-branded service onKeryn Cloud; sales-led solid: real dashed: partial dotted: roadmap

    Read deployment models for who operates each model, how organisations, SSO and billing map, and what is real, partial or planned.

    Surface Status
    CLI with JSON output and exit codes, CI Available in pre-release builds
    SARIF and CycloneDX AI-BOM export (formats) Available
    Import of Burp, ZAP and HAR captures (DAST guide) Available
    Keryn Cloud: organisations, an API with organisation keys, credits Optional service, bounded scans first
    Air-gapped use Documented
    @keryn/sdk TypeScript client and types See Download for npm availability
    @keryn/mcp MCP server (15 tools, stdio and streamable HTTP) Built and tested; on npm and the MCP registry once the owner publishes
    @keryn/skills: eight agent skills See Download for npm availability
    Cloud API OpenAPI document and JSON schemas Available
    Partner console, custom domains, per-partner branding Not built; scoped per agreement

    See capabilities and availability for what each part of Keryn does today and what is planned, and evaluation results for measured limits, including where Keryn is weak.

    1. One question the pilot answers, written down before day one.
    2. Success criteria with a measure and a threshold each.
    3. A data-handling statement: where analysis runs, what, if anything, is uploaded, and how it is deleted. Keryn does not upload by default.
    4. Written authorisation for any active testing.
    5. A decision on day 30: convert, extend or stop.

    Commercial terms for partners are on the partner terms page. Contract terms are drafted per partner and reviewed by counsel before signature. See also the sub-processors list.