Skip to content

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

    Cloud data, retention and limits

    View as Markdown

    Per organization: its members and their sign-in identities, the domains added with their verification token and when each was verified, and for each scan what was asked for, when, a summary and the report, plus an audit trail of who changed access, settings and data. The data is in a Postgres database at Supabase, in a private schema only the Cloud API reaches, with row-level security per organization: an organization reads its own rows only. Scans run on Vercel.

    Nothing from your machine is kept, because nothing from your machine is sent: not code, local scan results or posture answers. See Keryn Cloud.

    • Scans and their reports are kept for the organization’s retention period: 365 days unless an admin sets another (1 to 730 days, Account > Data). Older ones are removed automatically, and a restore from an older backup does not bring them back.
    • You can delete any scan, or remove any domain, from the Cloud page. Deleting your scans does not reset your rate limit: the limit counts a separate log.
    • Admins can download everything held for the organization and delete all of its hosted evidence from Account > Data; the deletion is recorded and says when the last backup holding the data expires. To close the organization or delete your account, write to security@keryn.dev from the address you signed in with.
    • A stored report is cut at 450 KB (the findings that fit are kept, the rest is counted and the limitation is stated in the report). An organization keeps at most 500 cloud scans and 20 domains.
    Limit Value
    Scans per account 20 an hour on the free plan; more with Team or a contract. The Cloud page shows yours
    Scans across all accounts 600 an hour
    Domain verifications per account 10 an hour
    Ownership checks (before a port check or a non-default port) 30 an hour
    Active scans 3 a day per verified domain and 3 a day per resolved address
    One scan 45 seconds in all
    The demo MCP server (/demo/mcp, no account) 60 requests a minute per IP address, then HTTP 429 until the minute ends
    The health check (/api/health, no account) 120 requests a minute per IP address

    The account limits are reserved before any work starts, on a log you cannot edit, so parallel requests do not get around them. The two limits without an account are enforced by the hosting firewall, in front of Keryn Cloud.

    Keryn’s servers will not turn a scan into an attack on a private network or an amplifier:

    • Every host is resolved through a lookup that refuses non-public addresses at the moment the connection is made, so a name that later resolves to a private address (DNS rebinding) is refused. Redirects are followed by hand and checked again.
    • Targets are host names, not IP addresses, on ports 80 and 443 unless the domain is verified.
    • Response bodies, request time and the number of items in an MCP list are capped.
    • Only email-confirmed accounts are served, and sign-in uses a PKCE flow so a crafted link cannot sign you into someone else’s account.
    • The service was reviewed in two rounds of testing before release; the fixes are covered by tests in the product’s repository.

    A cloud scan reports what Keryn’s servers observed from outside at one moment. It is not a certificate, a compliance determination or a penetration test of the target.