# Partners

> Eight ways to work with Keryn, what each needs, and what exists today. Keryn is pre-release, so every partnership starts as a time-boxed pilot.

Source: https://keryn.dev/partners/

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](https://keryn.dev/partners/terms/), then [become a partner](https://keryn.dev/partners/apply/) or write to [keryn@keryn.dev](mailto:keryn@keryn.dev). Nothing is sent to you unprompted.

## Partner types

| Type | Who it is for |
|---|---|
| [Offensive-security platforms](https://keryn.dev/partners/offensive-platform/) | Pentest, attack-simulation and attack-path platforms that want source-grounded evidence behind every path. |
| [Other scan providers](https://keryn.dev/partners/scan-provider/) | SAST, DAST, SCA and AI-security scanners that want an evidence and decision layer, or an engine and feed. |
| [Agencies, consultancies and MSSPs](https://keryn.dev/partners/agency-mssp/) | Consultancies and managed-service providers that run AI and application security reviews for clients. |
| [OEM and white-label embedders](https://keryn.dev/partners/oem-embedder/) | Products that want Keryn analysis inside them, under their own brand where agreed. |
| [Design partners and pilots](https://keryn.dev/partners/design-partner/) | Teams shipping AI features, agents or MCP servers who will give written feedback in return for early access. |
| [Resellers and referral partners](https://keryn.dev/partners/reseller-referral/) | Channel partners that resell Keryn credits or introduce customers who buy from Keryn directly. |
| [Technology and ecosystem integrations](https://keryn.dev/partners/technology-integration/) | CI/CD, ticketing, SIEM, ASPM and identity vendors that want a first-class Keryn integration. |
| [Training and workforce partners](https://keryn.dev/partners/training-workforce/) | Training platforms and employers that want AI-security engineering content and labs. Exploratory. |

## How the pieces fit

Diagram: 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.

Read [deployment models](https://keryn.dev/partners/deployment-models/) for who operates each model, how organisations, SSO and billing map, and what is real, partial or planned.

## What you can integrate with today

| Surface | Status |
|---|---|
| [CLI](https://keryn.dev/docs/reference/cli/) with JSON output and exit codes, [CI](https://keryn.dev/docs/guides/ci/) | Available in pre-release builds |
| SARIF and CycloneDX AI-BOM export ([formats](https://keryn.dev/docs/reference/formats/)) | Available |
| Import of Burp, ZAP and HAR captures ([DAST guide](https://keryn.dev/docs/guides/dast/)) | Available |
| [Keryn Cloud](https://keryn.dev/docs/cloud/): organisations, an API with organisation keys, credits | Optional service, bounded scans first |
| [Air-gapped use](https://keryn.dev/docs/guides/air-gapped/) | Documented |
| [`@keryn/sdk`](https://keryn.dev/docs/reference/sdk/) TypeScript client and types | See [Download](https://keryn.dev/download/) for npm availability |
| [`@keryn/mcp`](https://keryn.dev/docs/reference/mcp-tools/) 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](https://keryn.dev/download/) for npm availability |
| [Cloud API OpenAPI document](https://keryn.dev/docs/reference/api/) and [JSON schemas](https://keryn.dev/docs/reference/schemas/) | Available |
| Partner console, custom domains, per-partner branding | Not built; scoped per agreement |

See [capabilities and availability](https://keryn.dev/docs/concepts/capabilities/) for what each part of Keryn does today and what is planned, and [evaluation results](https://keryn.dev/evals/) for measured limits, including where Keryn is weak.

## What every pilot includes

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](https://keryn.dev/partners/terms/) page. Contract terms are drafted per partner and reviewed by counsel before signature. See also the [sub-processors](https://keryn.dev/subprocessors/) list.
