Security architecture

Built for private code review.

Sigilix reads code only to review it, keeps tenant context separated, makes retained learning explicit by plan, and ties security claims to evidence you can inspect.

Processing

Scoped GitHub App

Retention

Plan-aware learning

Runtime

Ephemeral workers

Reports

SOC 2 / ISO in progress

01

Compliance

Honest status, no borrowed badges.

We do not present a certification before it exists. These programs are in flight, and this page will be updated when an audit report or certification is actually issued.

SOC 2 Type 2

AICPA Trust Services Criteria

Audit work is underway against Security, Availability, and Confidentiality. The Type 2 report is not issued yet.

In progress

ISO 27001

Information Security Management

Risk register, statement of applicability, and Annex A control mapping are being assembled toward certification. Not yet certified.

In progress

GDPR

Data protection program

Processing records, subprocessor disclosures, and enterprise data terms are aligned around GDPR principles.

In progress

02

Data path

In, reviewed, accounted for.

The review path is narrow on purpose. Raw code is used to produce the requested review; durable learning and durable output are governed separately.

Flow

01

GitHub pull request

Sigilix reads the diff, PR metadata, and limited surrounding context through the installed GitHub App.

02

Review orchestration

The worker builds the review packet, runs specialists, and keeps raw code in the review path only while the job executes.

03

Model inference

Prompts are sent for inference under provider terms that prohibit provider training on customer content.

04

Durable output

The review, verdict, and evidence are posted back to GitHub. Retained learning signals follow your plan and settings.

GitHub scopes

Pull requests

Read + review write

Fetch the change under review and post a single review response.

Repository contents

Read

Retrieve cited files and surrounding context needed to validate a finding.

Checks / commit status

Read

Use CI signals when triaging failures against the diff.

Repository contents

No write access

The hosted reviewer does not push commits or modify files.

Organization administration

Not requested

Sigilix does not need org settings to review code.

03

Controls

The guardrails that matter.

The security posture is intentionally boring: scoped access, separated tenants, auditable evidence, and no hidden broad permissions.

Data handling

Raw code stays on the review path.

Code is fetched for the requested review, processed through the review system, and discarded from the raw review path when the job completes. Durable outputs live in GitHub; plan-specific retained learning is redacted and governed by your settings.

raw review pathredacted learningGitHub-owned output

Tenant isolation

Each installation is partitioned.

GitHub credentials, review state, learned conventions, and organization settings are scoped per installation, organization, and repository. Retrieval for one tenant cannot draw on another tenant's context.

per-org credentialsper-repo statescoped retrieval

Encryption

Encrypted in transit and at rest.

Traffic to and between Sigilix services runs over TLS. Limited operational state, evidence manifests, account data, and retained learning are encrypted at rest by the underlying platform.

TLSencrypted at restplatform-managed keys

Secret handling

Secrets are treated as findings, not content.

The review system is designed to detect leaked credentials, so tokens and customer secrets are kept out of logs and are not echoed into review output.

secret scanningcontent-free logsredaction

Evidence

Findings need receipts.

Security claims are tied to cited code, deterministic evidence, or execution receipts. The goal is to make every merge-blocking recommendation inspectable by a human reviewer.

proof tierscited codeexecution receipts

Access controls

Least privilege by default.

Internal production access follows role-scoped credentials. Customer-side permissions start with the minimum GitHub scopes required to read a PR and post a review.

role-scoped accessleast privilegerevocable grants

04

Subprocessors

A small footprint.

Your code starts in GitHub. Sigilix runs the review on Cloudflare infrastructure and uses inference partners only for the review or answer you requested.

Source of truth

GitHub

Where your code already lives. Sigilix reads pull requests through scoped app permissions and posts reviews back.

Application infrastructure

Cloudflare

Runs the API, workers, storage, and isolation primitives that power review, agent, and learning systems.

Inference only

Model inference partners

Used to generate the review or answer you requested under terms that prohibit provider training on customer content.

Optional product paths

Stripe / Linear / connected apps

Used only when you enable billing, issue triage, or app integrations. Each integration is revocable.

Responsible disclosure

Found something?

Send security reports to security@sigilix.ai. We read every report and prioritize issues that affect customer code, credentials, or tenant isolation.