Create with AI or code, deploy instantly on production infrastructure. One platform to build and ship.
Netlify is highly praised by users for its ease of use, reliability, and capabilities in hosting websites efficiently. The platform receives consistent high ratings, predominantly between 4.5 and 5 out of 5, indicating strong user satisfaction. While specific complaints were not prominent in the reviews analyzed, the absence of negative feedback suggests overall contentment with the product. Pricing sentiment appears neutral as it is neither a highlighted issue nor a frequent topic in user mentions, and Netlify is often used alongside other tools like Firebase, suggesting its incorporation in broader development workflows.
Mentions (30d)
7
Avg Rating
4.7
20 reviews
Platforms
2
Sentiment
15%
5 positive
Netlify is highly praised by users for its ease of use, reliability, and capabilities in hosting websites efficiently. The platform receives consistent high ratings, predominantly between 4.5 and 5 out of 5, indicating strong user satisfaction. While specific complaints were not prominent in the reviews analyzed, the absence of negative feedback suggests overall contentment with the product. Pricing sentiment appears neutral as it is neither a highlighted issue nor a frequent topic in user mentions, and Netlify is often used alongside other tools like Firebase, suggesting its incorporation in broader development workflows.
Features
Use Cases
Industry
information technology & services
Employees
190
Funding Stage
Series D
Total Funding
$214.1M
20
npm packages
5
HuggingFace models
Pricing found: $0, $9, $20 / month, $5 / 500, $10 / 1
g2
What do you like best about Netlify?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. Review collected by and hosted on G2.com.What do you dislike about Netlify?It’s not really a downside, but the observability could be improved a bit to surface more relevant, actionable data. Review collected by and hosted on G2.com.
What do you like best about Netlify?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. Review collected by and hosted on G2.com.What do you dislike about Netlify?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. Review collected by and hosted on G2.com.
What do you like best about Netlify?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. Review collected by and hosted on G2.com.What do you dislike about Netlify?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. Review collected by and hosted on G2.com.
What do you like best about Netlify?What I like best about NEtlify is how easy and fast is to deploy a website .I can easily connect my github repository and site gets deployed automatically. The dashboard is simple ,and I dont need to setup server or configuration. Review collected by and hosted on G2.com.What do you dislike about Netlify?Sometimes the build and bandwidth limitations in the free plan.Also when a build fails ,the error message are not always very clear for beginners. Review collected by and hosted on G2.com.
What do you like best about Netlify?Easy to setup hosting solution for websites, works well with various tools like React and svelte. Review collected by and hosted on G2.com.What do you dislike about Netlify?I don't really have any dislikes to be honest. Review collected by and hosted on G2.com.
What do you like best about Netlify?What I love most is how simple it is to push changes. For example, I updated my portfolio with new project screenshots, committed to Git, and Netlify had the new version live almost immediately. I don’t have to touch hosting or SSL certificates which I often struggle, it just works. Review collected by and hosted on G2.com.What do you dislike about Netlify?Sometimes, especially on bigger projects, the free tier can hit limits on build minutes or bandwidth, which slows things down. Also, the error messages aren’t always obvious if something unusual happens during deployment,it took me a couple of tries to figure out a domain redirect issue Review collected by and hosted on G2.com.
What do you like best about Netlify?Netlify makes frontend deployment unbelievably smooth, love the instant deploy previews on each PR, and the clean UI makes managing multiple projects simple. Review collected by and hosted on G2.com.What do you dislike about Netlify?Advance backend integration is limited , But for frontend-heavy apps or JAMstack projects, it’s not a big deal. Review collected by and hosted on G2.com.
What do you like best about Netlify?Makes it easy to connect multiple sources and display it on your Netlify site. Strong compatibility with leading CMS solutions, including WordPress, Shopify, Drupal, etc. Strong caching mechanisms ensure that content is delivered quickly. Review collected by and hosted on G2.com.What do you dislike about Netlify?Requires the site to be hosted on Netlify; can't be used as a standalone content aggregation service. Not a self-serve solution; must contact Netlify to set up a plan. Review collected by and hosted on G2.com.
What do you like best about Netlify?My most preferred aspect of Netlify is that static sites and JAMstack sites become deployable with a one-button click or simply a push to Git. The automated/continuous deployment from Git is smooth and all the built-in features like forms, serverless functions, redirects, and preview branches simplifies the development process. The dashboard is simple to work around and the free plan is surprisingly large and reduces the time for code and preview. Review collected by and hosted on G2.com.What do you dislike about Netlify?Netlify is good for the front-end and static websites, but there are some limits for more complex backend functionality. Lacks the logs to resolve the issues Review collected by and hosted on G2.com.
What do you like best about Netlify?Netlify’s simplicity and power are unmatched. Its seamless CI/CD integration makes deploying websites and web apps incredibly straightforward, even for beginners, making the ease of implementation outstanding. The intuitive dashboard, paired with preview links, has streamlined my workflow for frequent deployments. Netlify’s support team is responsive and helpful, providing clear solutions to issues, which adds to the overall positive experience. The platform’s reliability means we use it frequently for a variety of projects, from small prototypes to full-scale web apps. Review collected by and hosted on G2.com.What do you dislike about Netlify?While Netlify is fantastic overall, the free plan has limitations on build minutes and bandwidth, which can be restrictive for scaling projects. The pricing for higher tiers can also feel steep for smaller teams or individual developers. Additionally, more advanced documentation for less common use cases would be helpful for more niche implementations. Review collected by and hosted on G2.com.
Netlify and Claude
I am working on an app that is looking at a person's Bio in PDF format and allows me to ask questions based on the profile. Is this the best combo to use? Claude went back and forth about Claude doing it or deploying in Netlify. I get error messages. I just send it back. i just started using it a few weeks ago.. How much should I be spending a month to build a few apps? Looks like Claude timed out so I paid 5 bucks more. I am using the 20 dollar pro plan..Netlify free. So far:) Whoa...It just asked me to buy credits. Figure 10 - 15 hours a week of me telling it what to do.... Thanks all... submitted by /u/AliG68 [link] [comments]
View originalBuilt a site with Claude. How do I deploy it + hand it over to a client
I’ve just started building websites with Claude and I can make one now, but I’m stuck on the next steps. Getting it live: I’ve heard about Netlify but not sure how to actually deploy and make it searchable/Googleable. What’s the process? Backend: What even is a “backend” and do I need one if it’s just a brochure site + contact form? Client handover: Once it’s live, what do I give the customer? Files, hosting login, or just the link? After launch: Any other technical stuff I need to handle? SSL, SEO, analytics? Basically: what’s the 80/20 I need to know after Claude gives me the code? Thank you all in advance submitted by /u/lildweeb_101 [link] [comments]
View originalWeb dev using claude
Can you give me a prompt to ask Claude to build a super-complex, fully functional full-stack web app from scratch, including all source code, deployment files, and Netlify configuration? I want to be able to buy a domain, connect it, and launch the site. Also, how long would Claude typically take to generate a project of that scale? submitted by /u/Few_Cauliflower_3980 [link] [comments]
View originalWeb development using claude
Sorry if this sounds like a silly question, but I have a doubt. 1. Is it possible to build an entire, highly complex web application from scratch using Claude? Can it generate all the necessary project files so that I can upload them to Netlify, connect a custom domain, and deploy the application as a fully functioning website? 2. What actually Claude can actually do in web development? submitted by /u/Few_Cauliflower_3980 [link] [comments]
View originalWhere are you guys actually hosting/sharing the UI you build with Claude Design?
Hi folks. I’m researching an idea for an artifact hosting tool. Standard hosting options obviously exist, but the massive shift to agentic design tools like Claude Design, Lovable, and v0 seems to have created a gap. They generate UI incredibly fast, but their native publish links (like claude.site) are pretty limited for actual client handoff or enterprise use. I am considering a unified hosting layer where you can just dump the exports from any of these AI tools and get a professional setup instantly. Some features I have in mind: * Live markup for client feedback * Instant SSO and password walls (for private internal tools, preview sites) * EU data residency * Visitor analytics Is this something that would be useful to your workflow? Or do you just download the zip and manually push to Netlify/Vercel every time anyway? What do you actually use for this workflow? submitted by /u/VastPresentation7098 [link] [comments]
View originalSmall victory using Cloudflare for simple hosting of generated HTML/mini-websites
Something many people are running into: You, or a teammate, have created some kind of mini-website app out of Claude and now want to share it with the rest of the company, without overbaking the hosting solution (e.g. not setting up new Azure app services or containers, etc). Maybe you also need some basic data storage for persistence. And how do you do all of that securely? We recently went down this rabbit hole, while looking at all the major players: Vercel/V0, Lovable, Netlify, Coolify, Dokploy, Github Pages.. and even considered baking together our own hosting app solution using Azure or AWS as the backend. Our target audience is non-technical users in the team, so I was looking for something with drag-n-drop style deployment (no git required), and I really wanted to have SSO for protecting application access, along with some type of DB storage. The main issue I ran into was SSO authentication support being gated behind enterprise-level pricing plans for hosting systems like Netlify (which I'd otherwise highly recommend for a small public project). Netlify's enterprise level quickly gets quite a bit more expensive than their base tiers. I also didn't want to purchase yet another AI platform (e.g. Lovable, where really they're pushing an end-to-end AI development platform where you buy token credits through them). I wanted to host things we're already creating in our own Claude environment. Finally, I ended up on Cloudflare, which I've otherwise not really used before professionally. It's not as non-technical-friendly as Netlify, but it's pretty close. You can deploy Cloudflare Pages content via drag-n-drop. It has button-click databases available for integration, and most critically for us, the SSO integration is completely free for under 50 users. Their free hosting tier is also extremely generous and basically unlimited for completely static apps. Noting that SSO goes up to $7 USD/user/month for over 50 users, so your org size can really make a difference. If you have 500 users and the same use case for "hosting little mini apps", I'd go back to Netlify or another offering where SSO is more of a fixed fee. The other big win was that Cloudflare has a solid MCP server that works perfectly with Claude Cowork. We integrated that in and then wrote up some skills to assist with app building and deployment, including prompts for if a database backend is needed (using Cloudflare D1) and whether the app should be public or internal only with SSO protection. All working perfectly with minimal technical experience required for the enduser. I'm not at all associated with Cloudflare, just thought I'd share how we got a win for this use case. I'd be interested to hear if anyone else solved the same problem in a different way. submitted by /u/flck [link] [comments]
View originalVibe Coding for Oldies
At the ripe old age of 62, I have ventured back into programming. Last coded something like 30 years ago. May have been a bit ambitious, I wanted a Gardening program that would track the progress of my plants on both PC and on my Android phone. Androd is way more buggy. My one advantage is that I work in IT projects, so I know the stages to follow. And have definitely not skipped the testing. Seeing an update fix one thing and then break another, took me back to my programming days. And the familiar banging my head against the wall. So this was my first attempt and I was totally dependant on Claude for the coding. Also noted that I am also dependent on the tool to recommend the sub programs like Supabase. Rapidly ran out of tokens on Netlify and had to invest in a subscription. So not the cheap experiment that I was hoping for. I am not sure this is an activity for those that are not IT savy, just too many steps and repeating uploads. Plenty frustrating. But I do think it is a useful activity for schools to do. It teaches essential information on where all these Apps come from and why they are buggy. It is easier than when I first learned coding, but it is not yet magic. submitted by /u/Particular_Cicada395 [link] [comments]
View originalBuilt an MCP for claude code that turns ticket-mentions into PRs with browser QA (and what I learned along the way)
notesasm is an MCP server you add to claude code. you mention a fix mid-flow ("make a ticket on notesasm: fix the regex for quoted emails") and it files the ticket. later, on your schedule, an autonomous agent picks the ticket up, writes the fix, runs real-browser QA against your preview deploy, and opens a PR with screenshots. closed alpha, free during it. demo + signup: notesasm.com the pain it solves (3 separate ones, actually): claude code is fast enough now that shipping isn't the bottleneck anymore. when you're deep in a feature and notice "the regex misses RFC-quoted local parts" or "the footer copy is wrong on mobile", you'd never break flow to open jira/linear or even write it down anywhere. so the idea goes nowhere. multiply by a year and your repo has invisible debt nobody's tracking. claude code helps while you're at the keyboard. it doesn't help while you sleep. your repo doesn't move overnight unless you stayed up to push it. for solo founders or small teams, that means losing 8 hours a day where you could be shipping if you had a way to delegate work to your own agent. and even if you do have something pushing code for you overnight, you lose context with AI-generated PRs and they usually need visual review. claude writes code that compiles and tests pass, but the actual rendered output might be subtly broken (or super broken lol). reviewing those visually is tedious and a lot of teams skip it, then ship regressions. how it works: you add the MCP server: claude mcp add notesasm --scope user --transport http -H "Authorization: Bearer ". BYOK style, the token comes from your dashboard. zero local install beyond the one command. then in any claude code session you can say "make a ticket on notesasm for this" (based on your conversation) and it just files it. the MCP server is HTTP-transport (not stdio), runs in the cloud, hits a fastapi backend that stores the ticket in postgres against your workspace. later (your schedule, your spend cap), a worker process picks up queued tickets. for each one: clones your repo with a github app installation token (commits look like asmnotes[bot], a verified author. bypasses vercel/netlify deploy protection that rejects unknown-team-member commits.) runs the claude agent sdk with your ticket body as the prompt. defaults to sonnet 4.6, opus 4.7 for hard tickets the user marks explicitly. agent reads the codebase, makes the edits, commits, pushes a branch, opens a PR via the github API. waits for your preview deploy to land. vercel polled by default, configurable probe URL for split frontend/backend setups like vercel + railway. QA agent drives a real chrome session on browserbase against the preview. stealth profile with residential proxies. takes before/after screenshots. verifies your acceptance criteria against the rendered output. if QA fails, the report feeds back into the build agent for up to 3 retry iterations before parking the ticket. final: PR with QA screenshots in the description, ready to merge. stack: - backend: fastapi + asyncpg + railway - frontend: vanilla html/js, no build step, vercel - agents: claude agent sdk (build), claude + browserbase (QA) - auth: clerk - email: resend (welcome, invite, feedback) - mcp transport: http (cloud-hosted, no local install) things i learned building it that other claude code folks might care about: - the build agent loves to spawn subagents via the Task tool. disable it explicitly in the system prompt or you get 4-minute hangs the SDK doesn't surface as errors. - browserbase sessions default to a ~5-min timeout. if your QA wall budget is anywhere near that, set the session lifetime explicitly to 1800s on session create (the timeout field). otherwise you get random "410 Gone" mid-run. - don't rely on the SDK's wall budget alone. add a per-message timeout (90s works) so a hung tool call doesn't silently burn your whole budget. - claude code's default mcp scope is per-cwd. always tell users `--scope user` in your install instructions, otherwise the MCP works in one repo and silently doesn't in others. - ResultMessage emissions happen multiple times per job if you have iteration loops (build + QA + qa-fix). sum them all when computing per-job cost, not just the last one. what's next: closed alpha is open. would love ~30 active users to try it out, all free during it. paid plans later this year with a permanent discount for alpha users. happy to answer anything about the MCP design, the QA verification loop, cost tracking, the agent-sdk integration, or anything else. demo + signup: notesasm.com submitted by /u/FormExtension7920 [link] [comments]
View originalIf you are treating a one-shot generated file as your deliverable, you got it wrong.
I've been seeing a lot of posts and comments about people debating where to host files: GitHub Pages, Netlify, Vercel, SharePoint, Cloudflare etc.. Why is a static file the deliverable in the first place? you are stripping prompt history, iteration path, the ability to re-run on new data and to ingest feedback without starting over. You are essentially sending a postcard of a session. The right unit of work is the session it self. The prompts, the context, the skills that produced the dashboard, the path of the revision. That is what the recipient actually needs to engage with, because that is what gets rerun when they ask for the next version. The artifact is just one moment of an output. What does your deliverables looks like? Internally/ externally? Are you trying to relay context or still with single files or folders? submitted by /u/Ok-Dragonfly-6224 [link] [comments]
View originalAdding html files to website for client proposals?
I've cancelled my CRM and want to create custom proposals for client projects. I have a Squarespace website and have deployed other HTML work via netlify, and one with valtown as well. If I build a proposal with claude, and want clients to select an option with a next step to go to a stripe invoice, for example, how can I do this? Would I have to connect each HTML proposal to netlify + valtown? Ideally its a url like https://clientname.mydomain.com or simliar. Curious what others are doing to make this happen? If I add the code to my SQSP website, the embed frame looks weird. Thanks! submitted by /u/Beginning_Plant_7931 [link] [comments]
View originalPaste artifact url to publish as website, here's the actual workflow
The path most people don't realize exists: static.app/claude-hosting takes a claude artifact url and converts it into a hosted website without any download step. workflow: publish your artifact in claude (click share, get the public artifact url) open static.app/claude-hosting paste the url into the "import from url" field hit fetch, wait about 30 seconds you get a live website url From there you can connect a custom domain, turn on analytics, password protect it, or edit the html in the browser if you spot something to fix. forms inside your artifact start capturing submissions to a dashboard. The alternative is downloading the html from claude and uploading it to netlify drop or github pages, which works but is more steps. if all you want is "artifact url in, website url out," the importer is the shortest path i've found. submitted by /u/Then-Chest-8355 [link] [comments]
View originalMobile App with Clade
Just a quick question. Is building a mobile app like this actually a legit approach? I recently came across someone building fairly complex web apps, for example a geo quiz with full database integration, using this workflow: He generates all the HTML, CSS and JS through Claude (the AI), deploys it to Netlify, connects a database like Supabase or Firebase, and then uses "Add to Homescreen" so it looks and feels like a native mobile app. No framework, no GitHub repo, no CI/CD, no app store. And honestly it works. The apps are functional and pretty complex. So my questions are: Is this a legit long-term approach or will it break at some point when it comes to scaling, maintenance, payments etc.? Does anyone know a successful product built this way, just AI generated frontend code hosted on Netlify plus a backend as a service? At what point do you actually need a proper repo, a framework and a native app? For someone trying to ship fast and validate ideas, is this actually the smartest approach right now? I've been building things the proper way and now I'm questioning if I'm overcomplicating it. submitted by /u/yoloswaghipsterxx [link] [comments]
View originalLooking for testers - people who are selling locally
I built yrdsl.app, a digital yard sale tool with a Claude MCP integration. You drop in photos, Claude writes the listings, you get a shareable link like yrdsl.app/you/sale. Buyers reserve what they want. No commission. Where Claude comes in: through the MCP, you can add items, write descriptions, set prices, and attach photos just by chatting. "Here are 8 photos from my garage, list them all, price them to move" and it does. Works as a Claude Code plugin or with any MCP client. You can self-host on GitHub Pages, Vercel, Netlify, or Cloudflare Pages for free, or use the hosted version (about 10 cents per sale per month, no commission). What I need: people who are actually selling stuff locally - moving, downsizing, cleaning out a garage, estate sale, whatever. I want to watch the flow break on real inventory, not test data. Free during the invite-only beta. If you have a pile of stuff and 20 minutes, reply or DM and I'll get you set up. Happy to walk through it with you on a call if it helps. Link: https://yrdsl.app submitted by /u/matchoo [link] [comments]
View originalLessons learned building a no-hallucination RAG for Islamic finance similarity gates beat prompt engineering
Lessons learned building a no-hallucination RAG for Islamic finance similarity gates beat prompt engineering I kept getting blocked trying to share this so I'll cut straight to the technical meat. The problem: Islamic finance rulings vary by jurisdiction and a wrong answer has real consequences. Telling an LLM "refuse if unsure" in a system prompt is not enough. It still speculates. The fix that actually worked: kill the LLM call entirely at retrieval time. If top-k chunks score below 0.7 cosine similarity, the function returns a hardcoded refusal string. The LLM never sees the query. No amount of clever prompting is as reliable as just not calling the model. Other things worth knowing: FAISS on HuggingFace Spaces free tier is ephemeral. Every cold start wipes it. Solution: push the index to a private HF Dataset, pull it on startup via FastAPI lifespan event. PyPDF2 on scanned PDFs returns nothing. AAOIFI documents are scanned images. trafilatura on clean HTML beats OCR every time if a web version exists. Jurisdiction metadata on every chunk is not optional. source_name + source_url + jurisdiction in every chunk. A Malaysian SC ruling and a Gulf fatwa can say opposite things on the same question. Stack: FastAPI + LlamaIndex + FAISS + sentence-transformers + Mistral-Small-3.1-24B via HF Inference API. Netlify Function as proxy so credentials never touch the browser. What threshold do you use for retrieval refusal in high-stakes domains? submitted by /u/Particular-Plate7051 [link] [comments]
View originalgot mad at the news and built a satirical tariff refund portal in a few hours
i used: - claude sonnet - netlify - rage no coding background whatsoever and this was my first successful build after dabbling around with loveable months ago. learned a lot about efficient prompting and how to spec a website! submitted by /u/beepboopbleepbop [link] [comments]
View originalYes, Netlify offers a free tier. Pricing found: $0, $9, $20 / month, $5 / 500, $10 / 1
Netlify has an average rating of 4.7 out of 5 stars based on 20 reviews from G2, Capterra, and TrustRadius.
Key features include: Prompt Claude, Gemini, or Codex, Deploy from Git, CLI, or drag and drop, Preview every change before it's live, Roll back any deploy in one click, Build APIs with serverless functions, Add instant databases and file storage, Handle auth with built-in identity, Connect to AI models through AI Gateway.
Netlify is commonly used for: Why Netlify?, For every kind of web app..
Netlify integrates with: GitHub, GitLab, Bitbucket, Slack, Zapier, Sentry, Contentful, Shopify, Stripe, Auth0.
![Netlify Community Showcase [March 2026]](https://i.ytimg.com/vi/twtN2kWHAzI/mqdefault.jpg)
Netlify Community Showcase [March 2026]
Mar 13, 2026
Based on user reviews and social mentions, the most common pain points are: cost tracking, token usage.
Based on 34 social mentions analyzed, 15% of sentiment is positive, 82% neutral, and 3% negative.