Merge enforcement that survives procurement. ShipGate sits in GitHub with documented permissions, predictable CI behavior, exportable run records, and the contractual terms your InfoSec and legal teams need.
ShipGate holds no SOC 2 or ISO 27001 certification and this page claims none. What it can give your reviewers instead is the written security packet below and a gate whose behaviour you can read in your own CI logs.
Free web scans are capped. ShipGate CI is $50/month and is already included with every paid WholeStack plan. Enterprise is priced per contract. See the full price list.
| Feature | Repository scan | ShipGate CI | EnterpriseCustom |
|---|---|---|---|
| Manual repository scans | Unlimited | Unlimited | Unlimited |
| Static gates per scan | 17 | 17 | 17 |
| Per-gate results with severity counts | |||
| Advisory verdict: CLEAR / BLOCKED / UNVERIFIED | |||
| The "WholeStack / Readiness Advisory" check on every pull request | |||
| Evidence bound to the exact commit | |||
| Persisted verdict history + ShipGate dashboard | |||
| Runs on your own GitHub Actions runners | |||
| SSO — SAML 2.0 or OIDC | |||
| SCIM 2.0 directory sync | |||
| Signed audit-log export | |||
| Role-based access control | |||
| VPC / dedicated deployment | Where contracted | ||
| SLA + dedicated support | Custom, in contract | ||
| Price | $0 / forever | $50 / mo | Contact sales |
Not a roadmap slide. These are live capabilities for Enterprise contracts — scoped in writing, not implied.
Enterprise sign-in runs through SAML Jackson: a SAML 2.0 or OIDC connection per workspace, verified email domains, group-to-role mapping, and enforcement that can be required for the whole workspace.
Provision and deprovision through your directory. Okta and Azure AD have named connectors; anything else connects as generic SCIM v2. Directory groups map onto workspace roles.
Export the audit log as an NDJSON bundle with a manifest, a hash chain, and an HMAC signature — so the export can be re-verified later instead of merely trusted. Retention is configurable per workspace.
The supported path is the ShipGate workflow on your own GitHub Actions runners, requesting only read access to repository contents. VPC or dedicated deployment is available where contracted — scoped in writing, not implied.
Enterprise agreements carry a written SLA: response targets, escalation path, and a named support channel. The numbers are negotiated per contract, so this page does not publish an uptime figure it has not agreed with you.
Data-flow description, runner permission scopes, retention settings, failure modes including how to roll the check back out of the merge path, and written answers to your InfoSec questionnaire.