# Design partners and pilots

> Teams shipping AI features, agents or MCP servers who will give written feedback in return for early access.

Source: https://keryn.dev/partners/design-partner/

**Shape Keryn on your own repositories, with credit to start.** Keryn is pre-release; every partnership starts as a time-boxed pilot.

## The problem

You ship AI features, agents or MCP servers and have to defend them to your own customers. Evidence is thin and tools were not built for it.

## What Keryn gives you

- A starter credit of $10 (1,000 Keryn Credits, 90 days) for every new organisation, plus another $10 with a design-partner code, so you hold $20.
- Local scanning stays free with or without credit.
- Direct access to the team and influence on what ships next.
- Honest documentation of what Keryn does not do.

## How it connects

Diagram: Design partner integration. A design partner installs Keryn, scans its own repositories locally, adds the CI config and optionally uses a hosted starter credit, then gives written feedback.

- Install the CLI or open Keryn Web; first result in minutes.
- Add the CI configuration; optionally create a Keryn Cloud organisation and import exports.
- SSO and SCIM when you ask for them.

## What is available today

| Surface | Status |
|---|---|
| Local scans, CI, AI-BOM, trust graph | Available (pre-release) |
| Starter credit and design-partner code | Available |
| scans in Keryn Cloud | Bounded; sandbox builds, pentests and active testing on unverified domains are excluded from the credit |
| Signed and notarised installers | 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

No fee for the evaluation. A paid pilot, if you want one, is fixed-term and credited against what follows. Contracts are drafted per partner and reviewed by counsel before signature.

## First 30 days

| Days | Keryn | You |
|---|---|---|
| 1-3 | Kickoff, data-handling agreement, success criteria written down | Sponsor, technical owner, representative repository |
| 4-10 | Onboarding checklist: install, first scan, CI, organisation and roles | Run on the real repository; log every confusion |
| 11-20 | Weekly review; fix the top three blockers | Triage findings; record decisions |
| 21-27 | Measure against criteria; collect written feedback | Fill the feedback form |
| 28-30 | Decision: convert, extend or stop | Same |

Exit criteria: Criteria in the signed plan met or explicitly missed; written feedback received; permission to cite the partner recorded either way.

## What we ask of you

A named sponsor, one real use case, a representative repository, an hour a week for 30 days, and written feedback at the end.

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