Local-first GitLab CI Studio

Design pipelines visually. Keep the YAML honest.

Pipeline Studio pairs a draggable dependency graph with a real `.gitlab-ci.yml` editor, local linting, scenario-aware rule filtering, and exportable layout metadata.

Launch the Editor Start from Templates

Round-trip sync: YAML ↔ graph
Rendering target: 150 jobs
Storage model: Browser + sidecar

Visual Pipeline

Drag, connect, lint

150 jobs smooth

install

build

node_modules/

lint

test

eslint-report.json

deploy_preview

deploy

preview-url.txt

YAML

workflow:
  rules:
    - if: '$CI_COMMIT_BRANCH == "main"'

lint:
  stage: test
  needs: [install]

deploy_preview:
  stage: deploy
  needs:
    - job: lint
      artifacts: true

Why this exists

CI/CD editors should not force you to choose between speed and precision.

Pipeline Studio treats the YAML as a first-class artifact, preserves unsupported sections, and still gives you a high-context graph for stages, needs, dependencies, artifacts, rules, and layout metadata.

Dual surface editing

Move between a YAML editor with completion and a graph canvas with draggable job windows.

Local linting

Catch cycles, missing needs, invalid stages, artifact gaps, and unsupported visual constructs without a GitLab account.

Scenario filters

Preview branch, tag, and pipeline-source conditions through scrollable rule controls at the bottom of the workspace.

Templates

Start from real pipeline shapes instead of an empty canvas.

View all templates

Best for npm libraries and frontend apps.

Node Release Pipeline

Install, lint, test, pack, and release a Node.js package with artifact reuse.

Open in editor Learn more

Best for containerized services.

Docker Service Pipeline

Build container images, run security scans, and promote deploy jobs with manual gates.

Open in editor Learn more

Best for polyglot monorepos.

Monorepo Matrix Pipeline

Run selective tests for multiple services with rules and explicit downstream dependencies.

Open in editor Learn more

Best for teams adopting GitLab CI/CD catalog components and reusable template libraries.

Component-Driven Pipeline

Include CI/CD catalog components with spec:component context interpolation, parallel matrix builds, and OIDC id_tokens.

Open in editor Learn more

Best for monorepos with orthogonal build targets and child pipeline orchestration.

Child Pipeline with Run Keyword

Use the run: keyword to define child pipelines inline, with parallel matrix strategies and OIDC identity tokens.

Open in editor Learn more

Best for projects with compliance scanning, code review apps, and granular conditional includes.

Advanced Security & Review Pipeline

Conditional security scanning with rules:exists, include:rules, retry on exit codes, and environment stop jobs.

Open in editor Learn more

Search-ready content

Guides and glossary pages built for discoverability.

Browse guides

7 min read

Needs vs Dependencies in GitLab CI

Understand execution edges, artifact transfer, and how to model both relationships visually without breaking YAML fidelity.

GitLab CIArtifactsPipelines

Read guide

6 min read

Choosing Docker Images and Job Layouts

Balance Docker image reuse, stage planning, and readable node layouts when your pipeline grows beyond a simple build-test-deploy flow.

DockerImagesPipeline Design

Read guide

5 min read

How to Lint GitLab CI Locally

Catch missing dependencies, cycles, and unsupported visual-editor constructs before you commit a broken `.gitlab-ci.yml`.

LintingYAMLDeveloper Workflow

Read guide

FAQ

Can I edit raw `.gitlab-ci.yml` and keep the graph in sync?

Yes. The text editor is the canonical source, and the graph updates through a local worker so the UI stays responsive.

Does this connect to GitLab or require an account?

No. Version one is local-first, runs without a GitLab login, and does not call GitLab APIs.