The use case: how GatsbyJS deploys CircleCI
Gatsby moved its CI from a previous, unreliable tool to CircleCI. It started with unit tests and a few checks and now runs a full end-to-end test suite and real-world application tests using Cypress on CircleCI.
In the customer’s words
Using CircleCI caused a marked jump in our confidence that we can merge our pull requests without breaking real Gatsby applications downstream.CircleCI users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
ContentfulConfirmed
HoneycombConfirmed
LaunchDarklyConfirmed
PantheonConfirmed
RollbarConfirmed
SolarWindsConfirmedGo straight to the source
Based on CircleCI’s published case study. We check the public evidence; the results are reported by the vendor.
circleci.com- Source published
- Nov 12, 2026
- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of GatsbyJS.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- GatsbyJS uses CircleCIChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
When we started our transition to CircleCI, we thought we would just replicate what we had with our previous tool, and then we found that we can actually do a lot more on CircleCI.
