Best Practices · GitLab Well Architected

Features can differ by GitLab offering, tier, add-on, version, and status. Check the linked Docs pages.
Features can differ by GitLab offering, tier, add-on, version, and status. Check the linked Docs pages.
Six pillars help you improve how software moves from an idea to the people who use it. Start with the area you want to improve, consider the choices, and decide what fits your team. Use the linked recommendations and GitLab Docs when you're ready to put a decision into practice.
How to use Best Practices
Choose the area you want to improve, then use the guidance that helps with your question.
Learn the reasoning that anchors the pillar, including choices and tradeoffs to consider.
Explore practical approaches to the pillar's goals and how to apply them in your team.
Look at real settings and recent work, then decide what to improve next.
These areas follow the work rather than GitLab menu names. You may need guidance from more than one pillar. Together, they support a governed software factory: people, automation, and agents working with clear responsibility, current context, independent checks, and a way to recover. The guidance applies whether your next improvement involves AI or not.
Explore designs for particular GitLab workloads and the operational choices behind them.
Start with the outcome you need, then choose an approach that fits your responsibilities and available features.
Recommendations explain when particular approaches fit. The linked product documentation covers availability and setup.