How It Works

Enterprise

Merge enforcement that survives procurement. ShipGate sits in GitHub with documented permissions, predictable CI behavior, and exportable run records—not a six-month platform rollout.

What you buy

Pull-request outcomes on every commit, and structured exports for security and risk conversations. One Tier‑1 supported path — Next.js on GitHub — with everything else labelled best-effort until it is promoted, rather than quietly implied.

Enterprise is not the entry point. Scanning a repository is capped on free accounts, continuous CI is $50/month and included with every paid WholeStack plan, and Enterprise exists for the governance and contract terms on top. See the price list.

Security review

Expect data-flow answers, runner/permission scopes, retention, and failure modes (including rollback: disable the check). We do not lead with architecture diagrams—we lead with what runs in your org and what it produces.

Security overview →

Deployment

Default path: a GitHub Actions workflow on your own runners, asking only for read access to repository contents. Enterprise agreements may add SSO and SCIM, dedicated support, a written SLA, and VPC or dedicated deployment where contracted—scoped in writing, not implied.

Talk to us

Send deployment constraints, PR-gate / branch-protection patterns, and your security questionnaire—we respond with what we support today and what is on the roadmap.

Email team@shipgate.dev