OpenAna + GitLab

Code, CI/CD and security on GitLab - repositories, pipelines and issues.

Live connectionSource control

Ana + GitLab

What Ana does with it.

Ana reads repositories, opens branches and pull requests, and follows your review rules.

01
Merge requests with tests and context
02
Pipeline failure diagnosis and fixes
03
Issues picked up and closed with evidence

Setup

Connected in four steps.

1
Connect
Open Integrations in Ana and connect GitLab with a scoped token, OAuth app or service account.
2
Scope it
Start read-only and choose which projects, repositories or accounts Ana can see.
3
Set the rules
Decide which actions need approval and who approves them - Ana’s guardrails enforce it.
4
Put it to work
Ana uses GitLab in investigations, fixes and reports, and every action is logged.

In practice

Playbooks that use GitLab.

Software

Upgrading a framework across dozens of services

A major framework or runtime version is going end-of-life and it touches every service. Ana plans the migration, upgrades each service in its own branch, fixes what breaks, and hands your team small, tested pull requests instead of one terrifying diff.

Read the playbook →

Software

Burning down a stale bug backlog

Every team has a backlog of real but low-priority bugs that never win a sprint. Ana triages them, reproduces the ones that are still real, fixes them with tests, and closes the rest with evidence.

Read the playbook →

Used by

Ana’s engineers

Software →Security →SRE / DevOps →

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with GitLab, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.

Guardrails →Trust center →

FAQ