G2

Yauhen D.

Senior Fullstask Developer

Information Technology and Services

Mid-Market (51-1000 emp.)

7/26/2026

"Deploy Previews made design, QA, and engineering reviews much more practical!"

4.5/5

What do you like best about Netlify?

Immutable deploys have saved us more than once, especially when a failure had nothing to do with the code we had just changed. In one case, during a dependency update, the build completed successfully, but a library changed the behavior of a route that wasn’t covered by our tests. We used Instant Rollback to restore the previous deploy while we investigated, rather than rebuilding an older version or reverting several commits under pressure. The working deploy was already there, with the exact assets and configuration it originally shipped with. Context-specific environment variables are just as valuable during review. Production, Branch Deploys, Deploy Previews, and local development can all use different values, so our previews can point to staging services, disable certain third-party providers, and rely on restricted credentials. That way, someone can test a full flow without accidentally creating real customer data or triggering a live charge. We’ve also used Netlify Forms on smaller sites where a form needed reliable submissions and notifications but didn’t justify adding another backend service. It handles that kind of requirement well, as long as the workflow stays simple. Review collected by and hosted on G2.com.

What do you dislike about Netlify?

Build times become more noticeable in monorepos and in projects with a large number of generated pages. Caching helps when enough of the previous build can be reused, but changes that invalidate a large portion of the project can still take a while. On a small application, that delay is easy to ignore. Once several developers are opening pull requests and each one generates a preview, concurrency and overall build consumption start to become part of the delivery conversation. Deploy Previews reduce the work of maintaining temporary environments, but they don’t make those environments free. Review collected by and hosted on G2.com.

What problems is Netlify solving and how is that benefiting you?

A checkout redesign had already passed local testing when the client asked marketing, design, and QA to review the variants before anything reached production. The pull request produced a Deploy Preview with its own configuration, the Netlify Functions used by the new flow, and a payment variable pointing to the test environment. Design left feedback through the Netlify Drawer, and QA caught an issue that only showed up when a user returned from the payment provider. The Function logs made it clear that the same callback was being processed twice. We corrected the idempotency logic, updated the pull request, and everyone re-reviewed the fixed version using the same preview link, rather than waiting for another temporary environment to be set up. After release, a dependency triggered a failure on a less frequently used route, so we used Instant Rollback to restore the previous deploy while the fix was being prepared. Netlify didn’t prevent the defect, and it didn’t replace proper test coverage. What it did change was how quickly the team could review the real build, trace the problem to the exact Function version, and recover production without having to improvise a rollback while the client was already watching. Review collected by and hosted on G2.com.