Home/Security
Security and trust

What we hold, what we do not, and what we are not going to imply.

ArcRelease is early. The security posture below is stated exactly as it stands today, including the parts that are unfinished — because a claim you find out is untrue in a questionnaire costs more than the claim was ever worth.

SOC 2: audit in progress

Built to SOC 2 controls with the Type II audit in progress. We do not hold a Type II report and will not say we do until we have one in hand. What ships today helps you evidence your own SOC 2 change-management controls.

ISO 27001: audit in progress

Built to ISO 27001 controls with the certification audit in progress rather than complete. No certificate, no claim. Any vendor asserting both certifications at pre-launch is telling you something about how carefully the rest of their product was built.

Never in your deploy path

No runners, no agents in your build and no plugin in your pipeline. If ArcRelease is unavailable, your deploys still ship. That is an architectural property, not a promise.

Read-scoped access, no code writes

Read access to issues, PRs, commits, deployments, monitors and alerts, plus narrow write access for comments, notifications and change records. It never asks for write access to your code, branches or workflow files.

Named owners and recorded overrides

Every gate carries one named owner rather than a group or a shared mailbox. Overrides are permitted and recorded with a reason and a person, because a control nobody can override becomes one everybody routes around.

Regional framing, honestly scoped

ArcRelease reads release metadata: tickets, commits, deployments, alerts and approvals. It does not ingest customer personal data, which is the honest boundary for a DPDP Act 2023 or GDPR conversation. Data residency options are being finalised for general availability.

FAQ

Security, answered.

Not yet, and anyone claiming otherwise at this stage is worth a second look. ArcRelease is built to SOC 2 controls and the Type II audit is in progress. We will not say we hold a report until we do.

No. It holds no deploy credentials and asks for no write access to code, branches or workflow files. It reads what your tools emit and writes advisory comments and change records only.

Stop guessing at go/no-go.

Tell us about your release process. Connect your stack in ten minutes, run a Gaja preflight on a real release, and see the reasons behind the verdict.

See the platform

Free plan · ten minute setup · we reply in one to two business days