Story
GitLab
LemtransLemtrans Uses GitLab Security for Infrastructure as Code
Lemtrans, an information technology organization in the United States, uses GitLab Security from GitLab to support environment provisioning for platform engineers.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Platform engineers work from the same GitLab Security record for infrastructure as code |
| Capability | Infrastructure as code can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for infrastructure as code |
Story
Inside Lemtrans, environment provisioning used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of the United States. Platform engineers needed a system that would still make sense after the original project team moved on.
Lemtrans uses GitLab Security from GitLab as the working layer for infrastructure as code. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. The practical change is simple: environment provisioning has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Lemtrans gets from GitLab is a durable place to run environment provisioning and a way for platform engineers to see the same infrastructure as code at the same time.
