Technology and ecosystem integrations
Connect your platform to Keryn evidence and decisions. Keryn is pre-release; every partnership starts as a time-boxed pilot.
The problem
Section titled “The problem”Your users want security evidence and release decisions in the tools they already run, not another dashboard.
What Keryn gives you
Section titled “What Keryn gives you”- SARIF files that code-scanning and CI integrations consume.
- A release decision (Go, Go with accepted risk, Hold) with the chain behind each Hold, and hand-off to GitHub or GitLab issues, one per chain.
- A customer API with organisation keys, and HMAC-signed audit export batches.
- Enterprise SSO (OIDC, SAML) and SCIM provisioning per organisation.
- Integration-ready contracts: a published OpenAPI document, JSON schemas for decisions, scope and results, and exit codes documented per command.
How it connects
Section titled “How it connects”- Consume SARIF and CycloneDX from the Keryn CLI.
- Call the customer API with @keryn/sdk.
- Receive signed audit-export batches.
- Federate identity through OIDC or SAML, and provision through SCIM.
What is available today
Section titled “What is available today”| Surface | Status |
|---|---|
| SARIF and CycloneDX | Available |
| SSO (OIDC, SAML) and SCIM | Available in Keryn Cloud |
| Audit export with HMAC signature | Available |
| Customer API with organisation keys | Available; OpenAPI at keryn.dev/openapi/keryn-cloud.json |
| Issue hand-off from the Decision Desk | Planned (Decision Desk phase 4) |
| CI templates for other platforms | Built; green runs on each platform pending |
| GitHub Action | Built; not published yet (release qualification pending) |
| Webhooks | Not built |
Integration reference
Section titled “Integration reference”| Surface | Contract | Authentication | Status |
|---|---|---|---|
| Findings | SARIF 2.1.0 from the CLI, with stable rule ids, locations and fingerprints | none (a file) | Available |
| AI inventory | CycloneDX AI-BOM | none (a file) | Available |
| Customer API | /api/v1 described by keryn.dev/openapi/keryn-cloud.json; Idempotency-Key on submit |
Authorization: Bearer <organisation API key>, scoped, project-restricted, expiring |
Available |
| Audit export | Batches of up to 100 events, HMAC-SHA256 X-Keryn-Signature over the exact body, Idempotency-Key per batch; the receiver verifies the signature and deduplicates event ids |
shared secret | Available |
| Single sign-on | OIDC with PKCE, or SAML with signed assertions; the email domain is proved by DNS; IdP origins are allow-listed by the operator | the customer’s IdP | Available |
| SCIM | SCIM v2 at /api/auth/scim/v2, one token per directory connection; users and groups; members only, never admins; deactivation ends membership and sessions |
per-connection token | Available |
| Issue hand-off | One issue per chain or chokepoint, deduplicated by fingerprint, issue URL written back to .keryn/decisions.yml; a --dry-run prints the payloads |
the person’s own token | Planned |
Typical integrations we would build or support first
Section titled “Typical integrations we would build or support first”- Code scanning and CI: SARIF into GitHub code scanning and equivalent GitLab, Jenkins, Azure and Bitbucket jobs.
- Identity: an OIDC or SAML connection and a SCIM directory for an identity provider, tested with a non-admin account and a deactivation.
- Security data platforms: a receiver for the signed audit export, and the customer API for results and usage.
- Ticketing: the Decision Desk hand-off to GitHub or GitLab issues when it ships. Keryn does not build a tracker.
How an integration is validated
Section titled “How an integration is validated”- Fixture validated: your side runs our fixtures in your CI and the mapping loses no id, location or fingerprint.
- Live partner validated: a real tenant accepts and processes the output, with the exact request and response kept as evidence.
- Listed: only after step 2. A fixture pass is never described as a production integration.
See deployment models for who operates what.
Proof you can check
Section titled “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
Section titled “Commercial terms”No fee. We list integrations that pass a live joint test, and agree co-marketing case by case. If you also resell or refer, the reseller and referral terms apply. Contracts are drafted per partner and reviewed by counsel before signature.
First 30 days
Section titled “First 30 days”| Days | Keryn | You |
|---|---|---|
| 1-5 | Agree the surface and the contract; share fixtures and the OpenAPI document | Technical contact and a test tenant |
| 6-15 | Fixture test; fix mapping gaps; for identity, test a non-admin sign-in and a deactivation | Run fixtures in their CI; confirm field mapping |
| 16-25 | Live test on a real tenant; keep the request and response as evidence | Acceptance evidence |
| 26-30 | Write-up and listing decision; agree co-marketing if any | Same |
Exit criteria: Live acceptance evidence recorded; claim stated at its true strength.
What we ask of you
Section titled “What we ask of you”The integration surface you want, a technical contact and a test tenant.
Become a partner or write to keryn@keryn.dev.