Netlify Enterprise

What do you like best about the product?

N/A

What do you dislike about the product?

My experience with Netlify was unprofessional and unacceptable. After I accidentally canceled my domain subscription while trying to cancel my hosting, my business website was offline for five days. Initially, Netlify claimed the domain wasn't registered through them, though I had purchase confirmation, and Name.com verified their control through a reseller account. There seemed to be no urgent escalation process for an inaccessible business website, with emails answered only overnight, leaving me to question if support lacked daytime coverage for U.S. customers. It eventually took contacting executives and arguing for days to get my domain transferred to my Name.com account. Their slow and inaccurate handling of this outage harmed my business.

What problems is the product solving and how is that benefiting you?

N/A

What do you like best about the product?

I love that deploying with Netlify is a non-event; I just push to the branch, and it's live. As a solo operator, not having to deal with broken deploys at odd hours is invaluable. I don't have to run servers, which means no patching, no uptime monitoring, and no hosting tickets. Netlify saves me so much time, allowing me to focus more on client SEO work. The deploy previews are great; I can send clients the real site on their phone before anything goes live. I also enjoy being able to trigger builds and easily set up DNS configurations. The initial setup, including DNS and auto HTTPS for SSL certification, is very simple. Everything works seamlessly, even switching records and connecting proper repos.

What do you dislike about the product?

I would say for it to be easier to view the usage and plans that Netlify offers, it's a bit difficult to actually view the monthly build times and information; it's a bit unintuitive.

What problems is the product solving and how is that benefiting you?

Netlify lets me deploy sites effortlessly as a solo operator, eliminating server management tasks, saving time for client work. My clients never worry about hosting, and deployment is fast with just a branch push.

What do you like best about the product?

It makes deploying and managing web applications really easy, thanks to automated CI/CD, preview deployments, and integration with Git repos.

What do you dislike about the product?

I don’t dislike anything about Netlify. It’s simple, reliable, and developer-friendly.

What problems is the product solving and how is that benefiting you?

It reduces the complexity of deploying, hosting, and managing web applications by offering automated CI/CD, which helps me deliver faster and more reliably.

What do you like best about the product?

Generous free tier, easy to use, and lots of great features.

What do you dislike about the product?

I don't dislike anything about it. But it's not for non-technical people.

What problems is the product solving and how is that benefiting you?

It makes production deployment of marketing websites and web apps really easy.

What do you like best about the product?

I like how easy Netlify makes deployment. The Git-based workflow, preview builds, CDN, serverless functions, redirects, and edge features are all integrated well, so I can ship modern web apps quickly without managing much infrastructure.

What do you dislike about the product?

Costs and platform limits can become harder to predict as usage grows. I’d like better observability, clearer pricing/resource visibility, and more control over caching, redirects, build behavior, and serverless/edge-function constraints.

What problems is the product solving and how is that benefiting you?

Creating and hosting webapps for internal use

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product 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.

What do you like best about the product?

What I like most about Netlify is how easy it makes frontend deployment. Connecting a Git repository and having automatic builds and deployments on every push saves a lot of time during development. Especially the preview deployments for pull requests are useful because they allow changes to be reviewed before going live which saves me a lot of time.

What do you dislike about the product?

The free tier works fine for personal projects, but build minutes and bandwidth limits can become restrictive as applications size increases. Occasionally, debugging build failures also requires digging through lengthy logs.

What problems is the product solving and how is that benefiting you?

Netlify removed the need to manually configure servers or deployment pipelines for frontend applications. Automatic deployments, CDN hosting, HTTPS setup and preview environments allowed me to focus more on development rather than infrastructure management.

What do you like best about the product?

We can deploy websites easily and fast with simple setup process, also it has clean and user friendly dashboard, we can do preview deployments.

What do you dislike about the product?

The build time can slow for larger projects with less usage limits for free tier and remaining things are fine

What problems is the product solving and how is that benefiting you?

I've been using Netlify for a while to deploy frontend projects, and it has made the deployment process much simpler. The Git integration works smoothly, and automatic deployments save a lot of time. I also like how easy it is to manage domains, SSL, and preview builds from a single dashboard

What do you like best about the product?

I use Netlify to park JSON files online so our whole company can view and interact with them. It allows us to place something online without a domain or website, like manuals and company info. I like how easy it is to drag in a JSON and within seconds have a live site online. Plus, I appreciate the ability to connect with other software, like emailJS and Firebase, for reading and writing info. The initial setup was extremely easy; I signed up and started working right away. Even after upgrading to a higher plan for more functionality, there were no issues. Overall, my experience has been positive, and I'd rate my likelihood to recommend Netlify to a friend or colleague a 10 out of 10.

What do you dislike about the product?

Theres nothing I've found so far I dislike. So far this is the only tool i've used that can do this so its already ahead of the curve in that aspect

What problems is the product solving and how is that benefiting you?

I use Netlify to park JSON files online without a domain or website, making company info accessible. It's easy to get a live site online by dragging in a JSON file and connecting with other software.

What do you like best about the product?

The artificial intelligence guides you on the prompts and helps create a better response.

What do you dislike about the product?

It is extremely expensive to build bigger projects. I feel like the credits go really fast.

What problems is the product solving and how is that benefiting you?

Coding my websites without any errors. This saves me time and headaches.