One-click deploy
Deploy GitLab on your GRN.CLOUD cluster in one click — repos, merge requests, CI/CD, container registry and runners included. You keep admin on the instance; we keep the platform underneath it running. EU-owned, GDPR by default, on 100% renewable power.
No credit card required · Free during the Alpha phase · View pricing
The whole DevOps platform, on infrastructure that answers to Europe.
Git hosting, merge requests, issues, wiki, container and package registry, and CI/CD — one application, deployed from the marketplace by the official GitLab Operator.
Jobs run on your nodes, next to your data. Scale runners with the cluster instead of buying CI minutes, and never queue behind someone else's build.
Repositories and the database on block storage; LFS objects, CI artifacts and container images on S3-compatible object storage. €0.044/GB-month, and no egress tax.
GitLab sits on the same cluster your apps run on. Ship through the GitLab Agent for Kubernetes or Argo CD, with a review app per merge request.
Source code, CI logs and images stay on EU-owned infrastructure under Dutch jurisdiction. No US Cloud Act exposure, signed DPA, nothing phoning home.
Run it yourself with full admin, or hand install, upgrades, backup and restore, and runner capacity to our engineers as a managed add-on. Same instance either way.
GitLab, its runners, and GitOps — wired together on the cluster.
Hosted Git, merge requests & code review
.gitlab-ci.yml builds and tests on in-cluster runners
A live preview environment per merge request
Merge → the cluster reconciles itself to Git
The registry, the runners, the preview environments and the GitOps controller all run on the same managed platform. No CI server on the side, no glue to maintain.
Three ways in. Pick one; they end up in the same place.
GitLab custom
resource, the same way you manage everything else in the cluster.# 1. install the GitLab Operator from OperatorHub, then: $ oc apply -f - <<'EOF' apiVersion: apps.gitlab.com/v1beta1 kind: GitLab metadata: name: gitlab spec: chart: version: 8.x values: global: hosts: { domain: example.com } EOF # 2. or let your AI client do it over MCP $ claude mcp add --transport http grncloud \ https://mcp.grn.cloud/mcp
The questions an engineer actually asks.
The operator deploys the standard upstream GitLab chart — run the free Community Edition, or bring your own GitLab licence for Premium or Ultimate features. Either way the instance, its database and its object storage live in your namespace, on your cluster, under your admin account.
By default, yes — it is a self-service deploy, and you keep full control of the instance. If you would rather not, our engineers take over installation, version upgrades, backup and restore, and runner capacity as a managed add-on. Ask sales for a quote; nothing about the instance changes when you switch.
Yes. Standard GitLab backup and restore moves a whole instance; project export/import moves individual repositories with issues, merge requests and CI history. Our engineers will help you plan the cutover.
We charge no licence fee — you pay for the compute, storage and backup the instance actually uses, pay-as-you-go, with 10% off on annual commitment. Storage is €0.044/GB-month, backup €0.008/GB-month, and there is no per-GB egress charge. During the Alpha phase you get 10 vCPU and 32 GB of memory free to run it on. The managed add-on is quoted separately.
Deploy GitLab in one click and keep admin — or hand the running of it to our engineers.
100% renewable energy · EU data residency · No US Cloud Act exposure · No egress tax