Netlify Enterprise

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.

What do you like best about the product?

Netlify makes deployments incredibly easy. Whether I’m deploying a static site or a more robust app, it only takes a few minutes to get everything up and running.

What do you dislike about the product?

It’s not really a downside, but the observability could be improved a bit to surface more relevant, actionable data.

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

It helps me ship MVPs very quickly while still keeping things robust and giving the sense that it’s a full, polished product.

What do you like best about the product?

Netlify's instant deployment pipeline is a game-changer for a lean founder team. I use it to host and deploy AEOmotor's frontend — pushing to Git and having the live site update in under 30 seconds removes an enormous amount of friction from our development cycle. The branch previews are also incredibly useful for testing schema changes and structured data updates before they go live.

What do you dislike about the product?

The free tier's build minute limits can become a bottleneck during active development sprints. Also, the analytics dashboard is fairly basic compared to dedicated monitoring tools — you need to integrate third-party services to get meaningful insights into traffic patterns.

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

As a solo founder building AEOmotor — an AEO audit and AI search visibility platform — I needed a hosting solution that could keep up with rapid iteration without DevOps overhead. Netlify eliminates the need for a dedicated infrastructure engineer. CI/CD is fully automated, rollbacks take one click, and the edge network ensures our audit tool loads fast globally. This directly frees up time I can spend on product development and customer acquisition instead of server management.

What do you like best about the product?

I like that I'm able to deploy my web applications on Netlify easily using a live link. This feature is useful for publishing both front-end and back-end applications like those built with React, Next.js, Angular, Vue, and Django. The platform allows me to connect to real applications and deploy for various purposes such as ecommerce stores or client projects. I appreciate using artificial intelligence to help detect errors during deployment and enhance productivity. The command line interface, continuous integration, and continuous development features are great for ensuring my applications are always deployable and up to date, which helps prevent vulnerabilities and software rejections. Netlify automates the deployment process, checking for exposed .env variables and outdated software, which is crucial for maintaining security and functionality.

What do you dislike about the product?

Netlify has where it requires you use a certain amount of credits. They have their own command line interface, which I can easily use within the terminal rather than using the web application. Or the web version and being able to manually deploy it. It also gives me error messages when it hasn't been successfully deployed to the platform and posted to the web. There's also some ways of detecting any vulnerabilities and how I can improve and protect the web application from vulnerabilities. Just like Cloudflare or Vercel, Vercel has a detection where it can tell if you're vulnerable and which platform is vulnerable.

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

I use Netlify to deploy applications with live links, automate deployments using CLI, detect errors with AI, and ensure up-to-date software. It helps me showcase projects and handle servers efficiently, boosting productivity.