Delivery platform operations

One managed git server service, the right platform choice

Assistance operates GitLab, Gerrit, Gitea, or Forgejo as a scoped managed git server. We help choose the right option, define the operating boundary, connect runners or verification systems, and keep platform ownership explicit.

GitLab, Gerrit, Gitea, and Forgejo are platform options inside one managed service—not separate promises with different operating models.

Request a git server assessment Compare platform options

On-request / scoped service

Managed Git Server is scoped around your platform option, review workflow, identity provider, hosting model, backup and upgrade needs, runner or verification integration, and ownership boundaries.

View scope info

Platform choice before commitment

We compare GitLab, Gerrit, Gitea, and Forgejo against your review model, CI/CD needs, identity provider, hosting constraints, and migration path before recommending a target.

Operated service boundary

Provisioning, upgrades, backups, monitoring, access integration, runner or verification connectivity, and incident handling are scoped before Assistance accepts operational responsibility.

Runner-aware delivery platform

GitLab runners, Gerrit verification workers, Gitea Actions runners, and Forgejo Actions runners are designed with labels, scopes, token handling, private-network access, and troubleshooting paths documented.

Service playbook

From problem to operating evidence

Main content is structured like a case study: context first, scoped work next, then the operating changes and evidence a team can use after handoff.

Service briefWhen this service fitsPlatform optionsWhat Assistance operatesOwnership boundaries

Managed Git Server is the customer-facing service for Assistance-operated source control and code review platforms. Instead of selling GitLab, Gerrit, Gitea, and Forgejo as unrelated standalone services, we treat them as implementation options within one managed delivery-platform engagement.

Start with the Managed Git Server option guide when the platform decision is not yet settled. Use this service when you need Assistance to operate the selected git server after the decision is made. In the infrastructure taxonomy, Managed Git Server sits with facilitated local-development services alongside managed runners and team collaboration tooling, not as a platform infrastructure option.

Case-study lens

Scoped

Problem, responsibility, and handoff boundaries before implementation.

Evidence

Dashboards, runbooks, reviews, and operating records over borrowed logos.

Outcomes

Conservative summaries focused on observable operational improvement.

EvidenceSection 01

When this service fits

Runbooks, dashboards, reviews, and handoff material make the work auditable.

Need	What we assess
Private or self-hosted source control	Repository count, growth, LFS/packages, SSH/HTTPS access, backup expectations, and migration source
A specific review model	Merge requests, pull requests, Gerrit patch sets, submit requirements, protected branches, and approval policy
CI/CD close to the git server	GitLab Runner scopes, Gitea/Forgejo Actions labels, Gerrit verification adapters, caches, artifacts, and private-network jobs
Clear platform ownership	What Assistance operates, what customer teams own, escalation paths, maintenance windows, and evidence expectations
Controlled hosting	Customer cloud, Assistance-managed environment, Kubernetes, dedicated infrastructure, or migration/takeover model

Operating modelSection 02

Platform options

Responsibilities, response paths, and technical changes are made explicit before work starts.

Option	Best fit	Runner or verification pattern
GitLab	Teams that want source control, merge requests, CI/CD, packages, registry, and security workflows in one integrated platform	GitLab Runner at project, group, or instance scope with tags, protected runners, executors, caches, artifacts, and deployment profiles
Gerrit	Teams that need change-based review, patch sets, labels, submit requirements, and governed submission	Jenkins, Zuul, Tekton, or custom adapters consume Gerrit events and report verification labels or comments back to Gerrit
Gitea	Teams that want a lightweight private forge with pull requests, issues, packages, and Actions	Gitea Actions self-hosted runners with explicit `runs-on` labels, scoped registration tokens, and workflow validation
Forgejo	Teams that prefer a community-governed self-hosted forge with a Gitea-family workflow	Forgejo Actions runners with version-specific compatibility checks, scoped tokens, and documented private-network profiles

Use the Managed Git Server option guide for the detailed comparison between GitLab, Gerrit, Gitea, and Forgejo. This service page describes the managed operating model after an option is selected.

OutcomeSection 03

What Assistance operates

Expected changes are framed as practical operating improvements, not unsupported guarantees.

Area	Included when scoped
Platform runtime	Installation, sizing, storage, DNS, TLS, SSH/HTTPS endpoints, SMTP, and secure baseline configuration
Lifecycle	Version planning, upgrades, plugin or extension compatibility checks, maintenance windows, rollback notes, and validation
Reliability	Backups, restore procedures, monitoring, alerting, capacity review, certificate checks, and incident triage
Identity and access	SSO/OIDC/SAML/LDAP integration support, group mapping, admin roles, service accounts, and access-review evidence
Runner or CI integration	GitLab Runner, Gitea Actions, Forgejo Actions, or Gerrit verification-worker connectivity with documented scope and troubleshooting paths
Migration or takeover	Assessment of existing repositories, configuration, users, runners, backups, and cutover risks before Assistance accepts operations

EvidenceSection 04

Ownership boundaries

Runbooks, dashboards, reviews, and handoff material make the work auditable.

Responsibility	Assistance	Customer team
Platform operations	Operate the agreed git server runtime, backups, upgrades, monitoring, access integration, and incident process	Approve scope, access, budget, maintenance windows, and production-impacting changes
Repository governance	Configure branch protection, labels, submit requirements, permissions, and integrations when included in scope	Own repository content, code ownership, approval policy, release decisions, and user lifecycle decisions
CI/CD and runners	Operate agreed runner or verification infrastructure and document labels, scopes, token handling, and escalation	Own build logic, tests, secrets used by workflows, release criteria, and application failures
Security and compliance support	Maintain scoped hardening, TLS, audit logging support, access evidence, and vulnerability response for the platform surface	Classify data, approve access, manage internal policy, and define compliance evidence requirements

Operating modelSection 05

Onboarding workflow

Responsibilities, response paths, and technical changes are made explicit before work starts.

Assess — Review repositories, current platform, review model, identity provider, hosting constraints, backup posture, runner requirements, and migration risks.
Choose — Compare GitLab, Gerrit, Gitea, and Forgejo using the option guide and select the target platform or takeover path.
Design — Define topology, access model, backup and restore process, monitoring, upgrade cadence, support model, runner or verification integration, and ownership boundaries.
Provision or take over — Deploy or stabilize the selected platform, configure TLS, SSH, mail, identity, backups, observability, and runner or CI integration.
Operate — Maintain runbooks, schedule upgrades, review incidents, validate restores, adjust capacity, and update runner profiles as requirements change.

Next stepSection 06

Decision points and common questions are made explicit so follow-up work is scoped cleanly.

Managed Git Server option guide — compare GitLab, Gerrit, Gitea, and Forgejo before choosing a platform
Managed Runners — operated CI/CD runner capacity for GitLab, Gitea, Forgejo, Gerrit verification systems, and other platforms
GitLab runners — GitLab Runner scopes, tags, executors, protected runners, caches, and troubleshooting
Gitea Actions runners — Gitea Actions runner labels, tokens, and workflow validation
Forgejo Actions runners — Forgejo Actions runner labels and version-specific compatibility checks
Runner troubleshooting — triage queued, unmatched, offline, or private-network-blocked jobs
Managed Infrastructure — supporting infrastructure add-ons around a broader managed-services engagement

Request a managed git server assessment. We will review your review workflow, repositories, identity setup, hosting constraints, runner needs, and operating boundary before recommending GitLab, Gerrit, Gitea, Forgejo, or a migration/takeover path.

Request a git server assessment →

Ready to get started?

Book a quote review or talk to an engineer.

View scope info

How we compare

Feature	DIY / In-House	Us	Enterprise Vendor
Platform choice	You evaluate	GitLab, Gerrit, Gitea, or Forgejo assessed	Vendor-specific
Hosting model	You design	Scoped to customer cloud, managed environment, Kubernetes, or takeover	Vendor-dependent
Review workflow fit	You configure	Mapped before platform selection	Platform-dependent
Runner or verification integration	Self-managed	Included where scoped	Vendor-dependent
Backups and restore runbooks	Your team	Included where scoped	Vendor-managed
Operational overhead	High	Scoped Assistance ownership	Vendor-dependent
Custom domain

Pricing

Flexible scopes available. if you need custom terms or bundled service pricing.

On-request scope

Quoted