Your infrastructure. Your workflow. Let’s make it fit.
A scoped Null Review rollout alongside your existing GitLab and SSO.
One service. Two ways to start.
Self-hosted means you control the deployment and its data. Enterprise adds an agreed implementation and operations scope: architecture, security, integrations and acceptance. It is not a different engine or a mandatory move to a Null-hosted cloud.
| Self-hosted evaluation | Enterprise implementation | |
|---|---|---|
| Deployment | Your engineer follows the docs | Joint topology and rollout plan |
| GitLab / SSO / MCP | Configured by your team | Integration with your environment |
| Acceptance | Against an agreed checklist | E2E, permissions, recovery and load in scope |
| Terms | Package and license by request | Scope, pricing and support by agreement |
What we agree before starting
- GitLab version and edition, runner, organization count and roles.
- OIDC/Keycloak, certificates, networks and source-code handling rules.
- An available model, budget and provider usage policy.
- One initial repository, historical MRs and usefulness criteria.
- Resources, backups, monitoring and accountable owners.
Tell us about your team.
Tell us which GitLab you run, your repository and MR volume, approved model options and pilot owner. No code or credentials are needed for the first conversation. Public pricing, SLA and a production-availability date have not been announced; terms are agreed before work starts.
Discuss an Enterprise pilotCheck readiness first