Security · Rayrun
Log in

Security

The controls Rayrun runs today. The third parties that see workspace data. Where Rayrun stands on SOC 2 and HIPAA.

Controls

Ten claims, each with the mechanism behind it.

  • Credentials are encrypted per workspace

    Every workspace has its own data-encryption key. Rayrun holds the wrapping key separately. A stored credential is never sent to a browser, not even to the admin who entered it.

  • Or Rayrun holds nothing at all

    A workspace can keep its credentials in its own AWS account. Rayrun stores a pointer and no key, so a copy of its database grants nothing.

  • Reading a secret is an audited event

    One audited routine reads secrets. It records who read what, and why. Settings forms never show a stored secret again.

  • Tool definitions are held, not trusted

    A tool definition is approved once. A changed version waits until somebody reviews the diff. A definition with instructions to the model is never approved automatically.

  • Content is scanned both ways

    Detectors read both directions for secrets, personal data, and instructions written to the model. A match in a result is masked; a match in an argument stops the call.

  • Every call has one searchable record

    Every call records who made it, which policy and definition version applied, and what came back. The record can stream to your SIEM in signed batches.

  • Execution is contained

    Hosted hooks and code run in a sandbox with no ambient capability. Outbound requests pass an SSRF guard with a size cap and a deadline.

  • Access follows your directory

    OIDC and SAML 2.0 single sign-on. SCIM 2.0 provisioning. Access granted by directory group. Removing somebody revokes their tokens, sessions, and clients at once.

  • Your provider can authorize clients

    A client that already signed somebody in through your provider exchanges that sign-in for an endpoint token, with no consent screen. Its policy decides who gets one, and they still have to be a member here.

  • Published servers keep customers contained

    Each publication is its own authorization server, so a customer’s token works nowhere else. A call that needs approval is decided by the customer who made it, after a fresh sign-in.

In depth: credentials, tool definitions, access, and publishing.

Sub-processors

The third parties that process workspace data for Rayrun. The infrastructure is audited. The software on top of it is not.

SOC 2 and HIPAA

Rayrun holds no SOC 2 report and signs no business associate agreement.

Rayrun is a bootstrapped, one-person company. At this size, an audit would buy a certificate, not better security. The money goes into the engineering above, on infrastructure that is itself audited. Both are planned as the business grows. This page will say so when they arrive.

Do not send protected health information through Rayrun. Without a business associate agreement, it cannot be processed lawfully. If your review requires a SOC 2 report, Rayrun does not meet it today.

Reporting a vulnerability

Email security@ray.run. It reaches the person who can fix it, not a queue.