<commit_before>---
title: "Customer Story: Charge"
author: GitLab
author_twitter: gitlab
categories: 
image_title: /images/blogimages/Charge-customer-story/person-on-phone.jpeg
---

We always like to hear how our customers are using GitLab. In this post we will share how [Charge](https://charge.co/), 
a telecommunications company uses GitLab. 

<!-- more -->

- **Industry:** Data-only telecommunications
- **Company Size:** 5
- **Development Team:** 5
- **Location:** San Francisco

## Overview

Charge, the San Francisco-based startup, is looking to change the way we pay for our phone 
service. They offer simple pay-as-you-go plans for data, text, and calls on LTE devices. Charge 
runs lean with a small team of five. This mighty team of five is working on a solution to rival the telecommunications giants. 
Their mission to provide simple mobile phone service that puts consumers in control is no small undertaking. 
With their ambitious goal in mind, they quickly realized that their team couldn’t afford any missteps.

![](/images/blogimages/Charge-customer-story/person-on-phone-2.jpeg)

Charge needed to find a distributed version control solution that would help improve their engineering workflow, speed up 
their development process, and withstand industry security requirements. After looking into a number 
of different tools across the market, the team decided that GitLab Community Edition was the 
best solution for their needs. Since Charge migrated to GitLab they have already 
seen decreased development times and increased confidence in the code they’re deploying.  

## Looking for a secure alternative<commit_msg>fix image extension<commit_after>---
title: "Customer Story: Charge"
author: GitLab
author_twitter: gitlab
categories: 
image_title: /images/blogimages/Charge-customer-story/person-on-phone.jpg
---

We always like to hear how our customers are using GitLab. In this post we will share how [Charge](https://charge.co/), 
a telecommunications company uses GitLab. 

<!-- more -->

- **Industry:** Data-only telecommunications
- **Company Size:** 5
- **Development Team:** 5
- **Location:** San Francisco

## Overview

Charge, the San Francisco-based startup, is looking to change the way we pay for our phone 
service. They offer simple pay-as-you-go plans for data, text, and calls on LTE devices. Charge 
runs lean with a small team of five. This mighty team of five is working on a solution to rival the telecommunications giants. 
Their mission to provide simple mobile phone service that puts consumers in control is no small undertaking. 
With their ambitious goal in mind, they quickly realized that their team couldn’t afford any missteps.

![](/images/blogimages/Charge-customer-story/person-on-phone-2.jpg)

Charge needed to find a distributed version control solution that would help improve their engineering workflow, speed up 
their development process, and withstand industry security requirements. After looking into a number 
of different tools across the market, the team decided that GitLab Community Edition was the 
best solution for their needs. Since Charge migrated to GitLab they have already 
seen decreased development times and increased confidence in the code they’re deploying.  

## Looking for a secure alternative
{'fraction_non_alphanumeric': 0.0682095006090134, 'fraction_numerical': 0.0018270401948842874, 'mean_word_length': 4.5210084033613445, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4627831', 'n_tokens_mistral': 857, 'n_tokens_neox': 786, 'n_words': 429}