Works with · Ellipsis

Does an Ellipsis review count for SOC 2?

No. Ellipsis posts review comments on each push from a bot account; it is not an approval by a qualified person other than the author. PSCO reads its comments and adds the named Officer.

How Ellipsis reviews

Ellipsis reviews each push to a pull request and posts comments with suggested fixes, following the style rules you configure.

What it cannot do

Ellipsis cannot be the independent human approver an auditor is looking for. SOC 2 CC8.1, ISO 27001 A.5.3, PCI DSS 6.2.3.1 and SOX program-change controls all assume a qualified person other than the author approved the change and understood it. A bot account posting "Approve" is a review record, not an accountable person, and as of mid-2026 no auditor reports accepting it as standard practice.

How PSCO reads its output

Ellipsis comments become findings on the Officer’s packet by path and line.

Recognized asbot logins
ellipsis-dev[bot]Per-push review comments

Two-step setup

Keep Ellipsis.

Keep Ellipsis on.

Add PSCO.

Install the PSCO GitHub App, pick the repos in scope, and add psco/approved and one approval from @psco-officers to branch protection.

The shared-model tip

Point it at the same model the Officer uses.

Point Ellipsis at the same rulebook the Officer uses. Add the model’s rules to ellipsis.yaml or reference psco.model.yaml from it. Keep the sensitive paths, required checks and forbidden patterns identical in both places so the robot and the human check the same rules, and so the Officer's packet shows the AI's findings next to the clause they map to.

psco.model.yamlv1 · customer-owned
frameworks: [soc2, iso27001]
sensitive_paths:
  auth/**: deep
  infra/**: deep
required_checks: [ci, tests, sast, secrets]
forbidden: [hardcoded_secret, tls_verify_off]

Keep Ellipsis. Add the human who signs.

Connect GitHub and PSCO detects the reviewers already on your repos. Your price comes from your real PR history.