# OEM and white-label embedders

> Products that want Keryn analysis inside them, under their own brand where agreed.

Source: https://keryn.dev/partners/oem-embedder/

**Put AI and application security analysis inside your product.** Keryn is pre-release; every partnership starts as a time-boxed pilot.

## The problem

Your product shows customers a security posture but has no engine behind AI and agent risk. Building one is a multi-year effort.

## What Keryn gives you

- A contract-versioned engine and rule set with machine-readable outputs, so your product reads results without scraping text.
- Release evidence with every build: manifest, SBOM, provenance and verification output.
- Local processing and no telemetry by default, so customer source never has to leave their environment.
- Conformance fixtures so your upgrade CI catches contract changes before your customers do.
- Branding options from powered-by through private label to white label, agreed in writing.

## How it connects

Diagram: OEM embedder integration. An OEM partner embeds the Keryn engine or calls the hosted API from its own product, pins a contract version, and keeps its own customers, UI and billing.

- Embed the engine through the CLI with JSON output and SARIF, or call the hosted customer API with @keryn/sdk and one organisation per end customer.
- Pin the contract version, not only the application version.
- Use `@keryn/mcp` for your own agents.

## What is available today

| Surface | Status |
|---|---|
| Contract-versioned CLI outputs, SARIF, CycloneDX | Available |
| Hosted API with organisation keys | Available, bounded scans first |
| `@keryn/sdk`, JSON schemas, conformance fixtures | See [Download](https://keryn.dev/download/) for npm availability |
| Packaged embeddable library | Not built; sales-led engineering |
| White-label branding, custom domain, partner admin | Not built; scoped per agreement |
| Signed, notarised release artefacts | Pending |

See [deployment models](https://keryn.dev/partners/deployment-models/) for who operates what.

## Proof you can check

- Parity: on a public corpus Keryn's findings agree with the reference engine (Semgrep CE 1.157.0) on 10,306 of 10,306 findings, with one extra (receipt 2026-11-02).
- Detection: recall is 0.34 on 582 real-fix pairs, published with its denominator and its gaps (scoreboard 2026-10-28).
- Known fixes: 3,156 signatures in the known-fix database (2026-10-28).
- Local first: the CI copy-paste run made no network attempts (2026-11-02).
- Every evaluation suite, with inputs, denominators and limits, is at keryn.dev/evals.

## Commercial terms

Annual agreement: a platform licence of $40,000 per year per field of use (contract-version support, second-line support in business hours, upgrade assistance), plus an optional hosted credit commit at the Platinum rate from $25,000. Private label adds 15 percent of your annual commit (minimum $3,000); white label adds 25 percent of the platform licence (minimum $15,000) and is scoped against the branding features still to be built. See partner terms. Contracts are drafted per partner and reviewed by counsel before signature.

## First 30 days

| Days | Keryn | You |
|---|---|---|
| 1-7 | Qualification call; field of use and redistribution scope; evaluation agreement signed | Name architecture and legal owners |
| 8-15 | One invocation mode and one output path in a partner sandbox | Run the partner smoke example in their runtime |
| 16-23 | Pin the contract version; rehearse an upgrade | Ingest outputs; report gaps |
| 24-30 | Written scorecard and go or no-go; no production claim | Same |

Exit criteria: Evaluation passes on a clean-room install; nothing called integrated without live acceptance; counsel-reviewed commercial agreement before anything ships to a partner customer.

## What we ask of you

Your architecture owner, the field of use, and one invocation mode for a paid technical evaluation.

[Become a partner](https://keryn.dev/partners/apply/?track=oem-embedder) or write to [keryn@keryn.dev](mailto:keryn@keryn.dev).
