Skip to content

Enterprise

Higher limits today. A straight answer on the rest.

Enterprise is the hosted reviewer on an annual contract: no hourly review ceiling, larger pull requests, a signed DPA and a person who works through your security questionnaire. SSO/SAML, audit log export, self-hosting, air-gapped deployment, EU data residency and zero-retention mode are not built yet. If you need one, tell us which and by when — that is what decides the order we build them in.

annual contract, seat minimum applies.

Controls

What exists, and what does not yet.

The left column is enforced by the same code that enforces every plan’s limits. The right column has entitlement flags in our code and no working feature behind them, which is exactly why it is printed separately.

Available today

  • No hourly review ceilingLive

    Reviews are not rate-limited per hour, and pull requests of up to 2000 changed files are reviewed rather than skipped — enforced by the same code that enforces every plan's limits.

  • Every review depthLive

    quiet, balanced, thorough — set per repository in .superdiffs.yaml, so a payments service can run deeper than a docs site.

  • A signed DPALive

    The Data Processing Addendum with standard contractual clauses, and the subprocessor list it points at, with 30 days notice before that list changes.

  • Help with your security reviewLive

    Your questionnaire answered by a person, from the trust center and the security documentation — not a portal.

  • Admin-only settingsLive

    Only admins of your GitHub organization can change billing and review settings in the dashboard.

Not built yet

  • SSO / SAMLRoadmap

    Sign-in is GitHub OAuth today. SAML with your identity provider is planned, not built.

  • Audit log exportRoadmap

    Not built. There is no export of commands and setting changes to a SIEM yet.

  • Self-hosted and air-gappedRoadmap

    Not available. The intended design — your network, your model endpoint, no callback to us — is on the self-hosting page, marked as not yet available.

  • EU data residencyRoadmap

    Not available. Processing and storage cannot be pinned to a region by contract yet.

  • Zero-retention modeRoadmap

    The switch exists in the entitlement table; the enforcement path is not finished. Until it is, nothing is sold as zero-retention.

  • Uptime SLARoadmap

    Not offered yet. We have not run at enough load to set a number that is not invented for a procurement form.

Deployment

Hosted today. Self-hosted and air-gapped later.

Only the hosted service exists. The other two columns are the design we intend to build, published so you can tell us whether it would satisfy your security team — not because you can deploy it.

Deployment options compared
DeploymentHostedSelf-hosted (planned)Air-gapped (planned)
AvailabilityAvailable todayNot available yetNot available yet
Where reviews executeOur service, with a disposable sandbox per reviewYour Kubernetes or VMsYour network, with no outbound access
Who runs the modelOur model provider account (Anthropic)Your provider account, under your contractYour Bedrock, Azure or on-premise model
Code we keepCode snippets stored with findings, deleted on uninstallNone — it stays in your databaseNone — it stays in your network

Security architecture

What your code touches, and what touches your code.

The summary your security reviewer will ask for. The long version, with the subprocessor list and retention windows, is in the trust center.

  1. 01

    Each review runs in a disposable sandbox

    Your repository is checked out into a single-use microVM that is destroyed when the review ends. The only credential that crosses into it is a single-repository, one-hour, read-only token. Tokens that can post comments stay outside the sandbox and never enter it.

  2. 02

    The app cannot push to your code

    Contents are read-only. Write access covers pull request conversations and check runs, nothing else. There is no code path by which the reviewer commits to a branch, closes a pull request, or changes a setting.

  3. 03

    Instructions come from people, not from diffs

    Bot commands are honored only from identities with write access, checked against the GitHub permission API on every command. Text in a code comment, a diff or a dependency README is data — delimited as untrusted and stripped of invisible and unicode-tag characters before a model sees it. A pull request description can carry one command, ignore, which can only stop a review.

  4. 04

    Everything posted goes through an outbound filter

    Image channels, foreign links and raw HTML are removed from comments on a path the poster cannot bypass, and credentials are redacted from anything we post. A prompt-injection attempt in a vendored file cannot turn our comment into an exfiltration channel.

  5. 05

    Model provider retention is the provider’s default, for now

    Prompts go to our model provider through its API, on terms under which API data is not used for training. No zero-retention amendment has been executed, so the provider’s published retention applies until one is — and the trust center will name it when it exists. A zero-retention mode for our own systems is planned, not built.

  6. 06

    Uninstall deletes the code-derived data

    Removing the app deletes the evidence snippets, suggested patches and learnings we hold for that installation, in one transaction that writes an erasure record. Review metadata is kept for usage history; the retention table says for how long.

Procurement

What we have, and what we do not.

Vendor pages usually list only the first half. Both halves are below, because you will find out anyway and it is cheaper for everyone if you find out now.

What we can hand you today

  • A Data Processing Addendum with standard contractual clauses, published and ready to sign.
  • A maintained subprocessor list, with 30 days notice before it changes.
  • Security questionnaires answered by a person, from the trust center and the security docs.
  • Incident notification commitments in the DPA: without undue delay, and within 72 hours of confirmation.
  • Annual billing through Paddle, our merchant of record, which issues the invoices and handles sales tax.

What we do not have yet

We are a young company and the compliance shelf is not full. We would rather lose a deal than put a badge on this page that an auditor has not issued.

SOC 2
No audit has started and no report exists. Type I is planned after beta; the trust center describes the controls in the meantime.
Third-party penetration test
Not done yet. If a current report is a hard requirement, tell us your deadline in the form below and we will tell you plainly whether we can meet it.
Zero-retention terms and an uptime SLA
Neither exists yet: no zero-retention amendment is executed with our model provider, and we do not offer an SLA before we have run at load.
Customer references
We have no logo wall and will not manufacture one. What we can offer instead is our published benchmark, misses included, and a live status page.

Contact

Tell us what you need it to satisfy.

Requirements, deadlines, the reviewer you are replacing and why it annoyed you. We will come back with a straight answer about fit — including when the answer is that we are not ready for you yet.

  • A person replies, usually within one business day.
  • No drip sequence, no demo gate on the docs, no calendar ping-pong.
  • Smaller team? The design partner program may fit better.

Compliance requirements, timelines, the reviewer you are replacing.

Goes to the founders, not a sequence. We do not sell or share what you type here.