Story
GitLab
NexonNexon Adopts GitLab for Environment Provisioning
Nexon, a communication services organization in South Korea, uses GitLab Issues from GitLab to support environment provisioning for platform engineers.
Value results
| Category | Value result |
|---|---|
| Capability | Named workflow replaces ad hoc routing for infrastructure as code |
| Capability | Environment provisioning stays visible to adjacent teams through GitLab Issues |
| Capability | Platform engineers work from the same GitLab Issues record for infrastructure as code |
Story
Inside Nexon, environment provisioning used to depend on whoever still had the latest file. That pattern is common in communication services groups working out of South Korea. Platform engineers needed a system that would still make sense after the original project team moved on.
Nexon uses GitLab Issues 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 Nexon 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.
