Skip to content

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

    Agencies, consultancies and MSSPs

    View as Markdown

    A repeatable AI-security service line with evidence clients can check. Keryn is pre-release; every partnership starts as a time-boxed pilot.

    Clients ask about AI features, agents and MCP servers and want evidence, not opinions. Building a repeatable toolchain and evidence format yourself costs more than the first engagements earn.

    • Repeatable AI and application review: scan locally or in Keryn Cloud; findings with proof levels, an AI-BOM, a trust graph and recorded risk decisions.
    • Evidence packets a client’s security team can verify: inputs, versions, coverage, and what was not analysed.
    • Cheap re-runs: unchanged code costs nothing, so quarterly checks stay inexpensive.
    • Client isolation: one organisation per client, your consultants as members, SSO and SCIM where the client needs them.
    Agency and MSSP integration A consultancy runs Keryn locally or in Keryn Cloud for each client: one organisation per client, consultants as members, evidence packets as the deliverable. Partner environment Integration surface Keryn Consultantsdelivery team Client deliverablereport + evidence packet Client IdPoptional SSO, SCIM Keryn Web, CLI, desktoplocal first One org per clientmembers, API keys, spend cap keryn-export/1 importlocal results into the org Keryn Cloud orgcredits, receipts, audit Evidenceproof levels, coverage, decisions SSO, SCIM solid: real dashed: partial dotted: roadmap
    • Keryn Web, the CLI or the desktop app in the client’s environment; import keryn-export/1 into the client’s organisation afterwards.
    • CI configuration for recurring checks; SARIF into the client’s own tooling.
    • Organisation API keys per client project for scripted delivery.
    Surface Status
    Local scanning and evidence export Available
    Organisation per client, members, SSO, SCIM, spend caps Available in Keryn Cloud
    Partner console and multi-organisation view Not built
    Reports without Keryn attribution Sales-led private label; attribution stays until agreed in writing

    See deployment models for who operates what.

    • 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.

    Start on the standard plan, then buy credits at a partner rate by annual commit: Silver $2,500 per year (10 percent off list), Gold $10,000 (20 percent), Platinum $25,000 and up (30 percent). Referral of 15 percent on first-year purchases applies to clients you introduce who buy from Keryn directly. Private label is available as an add-on at 15 percent of your commit, minimum $3,000, and is the only tier where Keryn attribution can be removed, by written contract. See partner terms. Contracts are drafted per partner and reviewed by counsel before signature.

    Days Keryn You
    1-5 Agree service line and first segment; create agency organisation Name delivery lead and one pilot client
    6-12 Training: scan, triage, decisions, evidence export Run on a sample repository; draft report template
    13-20 Review the draft report against Keryn’s claim guidance (shared at enablement) Deliver the first engagement to the pilot client
    21-27 Collect usage and time per engagement; fix gaps Retro: what would the client pay for?
    28-30 Decide commercial terms for scale Same

    Exit criteria: One delivered engagement with client sign-off on the evidence; credits per engagement recorded; no unauthorised-scope incident.

    Your delivery lead, one pilot client and the first service you want to offer.

    Become a partner or write to keryn@keryn.dev.