Welcome to Cloudflare - Powering the next generation of applications
Users generally praise Cloudflare for its robust security features, easy integration, and overall performance reliability, as reflected in consistently high review ratings. Nevertheless, some social mentions allude to concerns about resource limits, like API restrictions, affecting user experiences with related tools. The sentiment around pricing is not explicitly highlighted but often tied to value for the offered services. Overall, Cloudflare maintains a strong reputation among users for being a dependable and effective solution in the software space.
Mentions (30d)
23
2 this week
Avg Rating
4.3
20 reviews
Platforms
2
Sentiment
19%
19 positive
Users generally praise Cloudflare for its robust security features, easy integration, and overall performance reliability, as reflected in consistently high review ratings. Nevertheless, some social mentions allude to concerns about resource limits, like API restrictions, affecting user experiences with related tools. The sentiment around pricing is not explicitly highlighted but often tied to value for the offered services. Overall, Cloudflare maintains a strong reputation among users for being a dependable and effective solution in the software space.
Features
Use Cases
Industry
computer & network security
Employees
4,400
20
npm packages
23
HuggingFace models
Project Glasswing: what Mythos showed us (Cloudflare)
Project Glasswing: what Mythos showed us (Cloudflare)
View originalPricing found: $0 /month, $20 /mo, $25/mo, $200 /mo, $250/mo
g2
What do you like best about Cloudflare Application Security and Performance?Cloudflare has a great team that is when ever there was a downfall , it didn't affect our publishers directly and came back soon. The kind of insights we get from the dashboard is crazy which helps build trust with our clients. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?The limitations of getting only few rows of data Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?Cloudflare is genuinely reliable and easy to use. I’ve been using it for years, and it has protected hundreds of my sites without going down. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?I feel like, at times, it takes a little too long for the DnS to register. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I like how Cloudflare Application Security and Performance combines both security and performance on one platform. The CDN noticeably improves load time, and it builds in security features like DDoS protection and a web application firewall, which provides strong protection. The interface is very clean and easy to manage, and its overall performance is really good. Their analytics and traffic insights are also very helpful. I find the initial setup to be very straightforward; the dashboard is intuitive, and configuring most core security and performance features doesn't require much technical effort. It's a very easy and good platform to work with. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?Some advanced configuration can be a bit complex for a new user, and certain powerful features are limited to the higher-tier plans. It would be great to see simpler guidance for beginners and more flexibility in pricing. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?Nothing.Nothing.Nothing.Nothing.Nothing. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?Cloudflare's "Cancellation" System is a Joke - 35+ Days, Multiple Charges, Still Can't Cancel TL;DR: Cancelled all Cloudflare subscriptions on December 25th, 2025. Got charged anyway on December 27th AND January 27th. Their support says "engineers cancelled all subscriptions" but the billing page STILL shows an active $240/year subscription that I literally CANNOT edit or remove (the Edit button does nothing). Over a month later, still fighting this. --- The Timeline of Absurdity December 25, 2025: I cancel ALL my subscriptions through the Cloudflare dashboard. Everything. Done. Or so I thought. December 27, 2025: I get charged $10 for "Advanced Certificate Manager" - a service I JUST cancelled 2 days ago. I open a support ticket demanding a full refund, explanation of why a cancelled service was charged, and all payment methods permanently deleted. December 31, 2025: Support responds saying it's a "system-side issue" and they've "escalated to engineering." They also mention response times might be slow due to holidays. Fair enough, I guess. January 27, 2026: I GET CHARGED AGAIN. Same subscription. At this point I've been waiting a MONTH. January 29, 2026: Support claims "Our engineers have cancelled all active subscriptions on the account." January 31, 2026 (Today): I check my billing page. THERE'S STILL AN ACTIVE SUBSCRIPTION showing $240.00/yr with a renewal date of June 8, 2026. The "Edit" button? Doesn't work. Nothing happens when you click it. --- What I've Learned 1. Cloudflare's cancellation system doesn't actually cancel billing - They might stop your services, but the billing keeps rolling. 2. The UI is deliberately broken - You literally CANNOT click "Edit" on subscriptions to remove them. It's not a bug, it's a feature (for them). 3. Support plays the "escalated to engineering" card - Classic stalling tactic while they keep charging your card. 4. They ignore requests for legal contact information - I've asked multiple times for their legal representative's contact details. Radio silence. --- My Response to Their Latest "We cancelled everything" Email "No, you did not cancel all active subscriptions in my account! Can you see how that subscription is still active? I want that permanently removed." "You will have to remove my payment method, and permanently delete my account and make sure all subscriptions are canceled!" --- What's Next - Filing complaint with ANPC (Romania's consumer protection agency) - Filing EU consumer protection complaint - Contacting legal representation - Documenting EVERYTHING for potential legal action --- The Real Question How is a company this big allowed to have billing systems this broken? Or is it "broken" by design? When you can't cancel a subscription because the Edit button literally doesn't respond to clicks, that's not a bug - that's a dark pattern. --- Has anyone else experienced this with Cloudflare? I'd love to hear your stories. Maybe we can compile enough cases for a class action. EDIT: I have the full 5-page support ticket transcript as evidence. Names/emails redacted for privacy but happy to share with anyone who needs it for similar cases. --- Posted from someone who's been in tech for 30 years and has never seen billing this bad. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?This is compactable to use with default built in features like Waf, Ddos protection and bot management The dashboard is more intuitive and rules are more flexible and easy to use great value product Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?Debugging security events or performance issues feels opaque Concepts like firewalls rules and rate limiting and caching behaviors are confusing Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I really like that I can use the Cloudflare platform for high-level security with DDoS protection. The DNS service is compatible with my needs, and I also appreciate other features such as analytics and performance, which enhance the speed of the site. I drastically use Cloudflare to protect my websites. Incorporating different features like this is key when I build websites using fullstack tools and technologies. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?I do have to pay for the services. It was a bit difficult since I had to change over the CNAME, and the other DNS services. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I like Cloudflare Application Security and Performance for its robust protection against DDoS attacks and web threats. It automatically improves application speed through its global CDN and edge networks without requiring complex configurations or infrastructure changes. The DDoS protection and global CDN are especially valuable because they provide security and performance at the same time without adding complexity to our infrastructure. The initial setup was straightforward and relatively quick. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?Fine-tuning WAF rules and bot management settings can take time to avoid false positives, particularly for complex or highly dynamic applications. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I use Cloudflare Application Security and Performance to protect and speed up websites. What I like most about Cloudflare Application Security and Performance is how it handles security and speed together. The DDoS protection and firewall work really well in the background. The CDN makes the website load faster without much manual work, saving a lot of time and giving peace of mind. The DDoS protection blocks sudden fake traffic effectively, the firewall filters out suspicious requests with ease, and the CDN serves content from nearby servers, improving loading speed. It also works smoothly with other tools like web hosting services, CMS like WordPress, and GitHub for deployment, adding an extra layer of security and performance on top of the existing setup. After moving to Cloudflare, things became more stable, faster, and easier to manage. The initial setup was fairly easy and manageable even without deep expertise. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?Some settings are a bit confusing at first, especially the security rules and firewall options. For beginners, it takes some time to understand what to enable and what not. Also, advanced features are locked behind paid plans, which can be limiting sometimes. The learning curve could be smoother. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I like that Cloudflare Application Security and Performance is very fast and easy to use. It provides built-in security performance improvements without much manual effort, which mainly helps to keep applications secure and fast with minimal maintenance. Its ability to improve application speed and availability is quite beneficial. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?New users might have some learning to do when they start using Cloudflare Application Security and Performance, but it's not a big problem, it's just something to get used to. Review collected by and hosted on G2.com.
What do you like best about Cloudflare Application Security and Performance?I really appreciate that Cloudflare Application Security and Performance handles maintenance tasks for me, making most things a one-time setup. They also provide great value and services even in their free tier. Additionally, I use the CDN for caching and image optimization, which enhances performance. Review collected by and hosted on G2.com.What do you dislike about Cloudflare Application Security and Performance?I think the UI and UX could be simpler, as new users often get stuck and need a professional's help. Review collected by and hosted on G2.com.
browser-search — three tools, zero cost, and your AI agent learns to search and browse the web
I've been using AI agents like OpenCode, Claude Code, and Cursor for months. They're great with code, but when they need to search or browse the web, things get complicated: Cloudflare blocks them, JavaScript-heavy sites don't load, APIs cost money. So I built browser-search. It's three open source tools orchestrated by a skill, fully self-hosted: SearXNG — metasearch engine that queries dozens of search engines at once Camofox — full browser via REST API, always warm, for browsing and interacting CloakBrowser — stealth browser for when the site has Cloudflare, Akamai, or DataDome The agent decides which tool to use. Zero human intervention. Zero API keys. Zero subscriptions. What makes it different: It's a skill, not a plugin — works with any agent that can read instructions Automatic navigation escalation: if Camofox gets blocked, it switches to CloakBrowser Deep Research mode: the agent is instructed to go beyond surface-level answers, cross-verify sources, cover every aspect Integrated Readability.js for clean article extraction (~70% token savings) The SKILL.md is plain text — fork it, tweak it, make it yours MIT licensed on GitHub: https://github.com/Johell1NS/browser-search If you try it, let me know. If you make it better, even more so. If you don't need it, share it with someone who might. Every star, comment, or pull request is welcome — that's what makes open source great. submitted by /u/Ill-Tradition1362 [link] [comments]
View originalOffering Free Websites Sounded Stupid Until I Tried It
My philosophy is that the longer you stay in a business, the better you get and the better systems you build. 4 years ago I was a complete rookie in the web design niche. My whole workflow was bad and not scalable at all. I used to adapt myself to every client. Some clients paid upfront before seeing the website, others paid half upfront and half after, and others paid after the website was finished. Honestly, I was doing whatever I could to get paid. Looking back, it wasn't professional and I wasn't in control. I was also spending way too much time on outreach. One week I was cold calling, the next week I was sending DMs, then I was trying email outreach. I was constantly jumping between different methods and it was exhausting. Along the way I made a lot of friends who were running web design agencies and I started paying attention to what they were doing. Every agency owner had something they were really good at. Some were amazing at outreach, some were great at sales, and some had incredible systems. So I started taking the best ideas from each person and implementing them into my own workflow. The first thing I changed was outreach. I completely stopped manually researching websites and writing emails one by one and started using website analysis and personalized outreach instead. I upload a list of businesses with websites and run an analysis on the entire list. It automatically finds issues related to design, layout, mobile optimization, SEO, and other areas that could be hurting the business, then turns those findings into ready-to-send personalized emails. And when I say personalized emails, I don't mean generic reports with a website score and an SEO score. Nobody cares about that. I mean actual humanly written emails that explain what could be improved and why it matters to the business. The crazy thing is that businesses genuinely think I've manually reviewed their website and written the email myself. Honestly, it's scary how detailed some of them get. I run all my outreach campaigns like this. The second thing I changed was the offer. Inside the campaigns I can choose how I want the email to end. I can try to book a meeting, start a conversation, or offer a free website draft. I almost always choose the free website draft because you'd be surprised how many business owners are willing to take a look at a better version of their website when it costs them nothing. The third thing I changed was how I build websites. This might make some people mad, but I use AI heavily and honestly nobody cares. AI has become insanely good. The process is faster, easier, and allows me to spend more time talking to clients instead of spending hours building the same things over and over again. The fourth thing I changed was the sales process, and this is where I see a lot of people make a huge mistake. Do not send the preview link through email. I repeat, do not send the preview link through email. When someone is interested in the free website draft, your goal is to get them on a meeting. If you send the link, they'll look at it for 30 seconds and move on with their day. Instead, I invite them to a Google Meet and present the website live. That's where everything changes. They see a modern version of their business, a better design, a better layout, and a better user experience. Most of the time the conversation naturally becomes, "How much would it cost to keep this?" Depending on the business, I charge anywhere from $500 to $5,000 upfront and usually between $50 and $150 per month for hosting, maintenance, and future updates. My biggest lesson from the last 4 years is simple. Always network, always learn from people who are ahead of you, and when you see something that's working, don't be afraid to implement it into your own business. As I've been helped by others, I figured I'd share what's currently working for me. For anyone wondering, my stack is: Swokei for website analysis and personalized outreach. Claude for building websites. Cloudflare for hosting websites. Google Meet for presentations and sales meetings. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalThe hardest part of AI memory isn't remembering things
The hardest part of AI memory isn’t remembering things. It’s figuring out what the AI should still believe later. Example: A few months ago, you tell it: “this project uses Postgres.” Yesterday, while brainstorming, you say: “SQLite might be simpler.” What should the memory system do? Should it update the project memory? Flag a conflict? Treat SQLite as a draft idea? Ask before changing anything? This is the part of AI memory I think gets overlooked. A lot of systems focus on storing and retrieving context, but the harder problem is memory quality over time. Once there’s enough memory, you run into stuff like: old decisions vs new thoughts duplicates that are almost the same casual notes competing with confirmed decisions stale context that still shows up in recall conflicts that get resolved silently when they probably shouldn’t The approach I’ve been experimenting with is treating memory less like chat history and more like a small system of record: canonical for trusted memories draft for things that might be true deprecated for outdated context contradiction detection before overwriting merge logic for near-duplicates importance scoring so real decisions rank above throwaway notes I open-sourced what I have so far here: https://github.com/rahilp/second-brain-cloudflare It runs on Cloudflare Workers, D1, and Vectorize, and is meant to work as a shared memory layer across MCP clients. Mostly posting because I’d like feedback from people thinking about this too. What should an AI memory system do when a new memory conflicts with an old one? submitted by /u/rahilpirani5 [link] [comments]
View originalIs it Possible To Make 1M$ By Selling Websites?
For the longest time, I thought landing higher paying web design clients required some secret sales strategy or better closing skills. After looking through my client reports every month, I realized something interesting. The difference between landing a client paying $500 and one paying $5,000 usually comes down to positioning and who you're targeting. With bigger companies, it takes more effort to find the right person involved in website decisions. Smaller businesses are easier because you can usually reach the owner directly. But the outreach process I'm using now works for both. I don't cold call anymore. Instead, I run automated email campaigns with an offer that's extremely hard to ignore. The first step is getting a list of businesses that already have websites. This is important. I don't target businesses without websites because the whole strategy depends on offering them a better version of their current website. Once I have the list, I put the businesses into a campaign and choose my campaign settings and offer. The options usually include starting a conversation, booking a meeting, or offering a free website draft. I always choose the offer as free website draft. Then I set a quality threshold. Mine is 7/10. Any website scoring above that gets skipped because there's no point trying to sell a redesign to a business that already has a great website. After that, I launch the analysis. Every website gets scored and reviewed for design, speed, SEO, layout, and mobile optimization. Then a personalized email is generated explaining what could be improved. Not one of those generic reports full of random scores and numbers, but an actual explanation written in plain language. The response rate is surprisingly good because most business owners appreciate someone taking the time to look at their site and give useful feedback. A lot of the replies are basically: "Sure, as long as it's free." Or: "Who says no to a free website redesign?" That's when I call them. I tell them I've already created the redesign and would like to walk them through it on Google Meet. The funny thing is I can build these drafts incredibly fast with AI, so by the time we talk, I already have something to show. During the presentation, even though I position it as a free redesign, most prospects end up asking: "How much would this cost to me?" That's where the sale happens. Depending on the business, I charge anywhere from $500 to $5,000 upfront, plus a monthly fee between $50 and $150 for hosting, maintenance, updates, support, and small changes. This approach has worked really well because the offer feels low risk for the client. They get value before they ever have to make a buying decision. For anyone curious about the stack I use: Swokei for lead generation, website analysis, and personalized outreach. Claude Code for building websites. Hetzner for hosting (moved from Cloudflare). Google Workspace for email. Google Meet for sales calls. Nothing revolutionary. Just a simple offer that's easy for businesses to say yes to. Curious what outreach methods are working for other agency owners right now. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalMy Weirdest Web Design Sales Trick Actually Works
For the longest time, I thought landing higher paying web design clients required some secret sales strategy or better closing skills. After looking through my client reports every month, I realized something interesting. The difference between landing a client paying $500 and one paying $5,000 usually comes down to positioning and who you're targeting. With bigger companies, it takes more effort to find the right person involved in website decisions. Smaller businesses are easier because you can usually reach the owner directly. But the outreach process I'm using now works for both. I don't cold call anymore. Instead, I run automated email campaigns with an offer that's extremely hard to ignore. The first step is getting a list of businesses that already have websites. This is important. I don't target businesses without websites because the whole strategy depends on offering them a better version of their current website. Once I have the list, I put the businesses into a campaign and choose my campaign settings and offer. The options usually include starting a conversation, booking a meeting, or offering a free website draft. I always choose the offer as free website draft. Then I set a quality threshold. Mine is 7/10. Any website scoring above that gets skipped because there's no point trying to sell a redesign to a business that already has a great website. After that, I launch the analysis. Every website gets scored and reviewed for design, speed, SEO, layout, and mobile optimization. Then a personalized email is generated explaining what could be improved. Not one of those generic reports full of random scores and numbers, but an actual explanation written in plain language. The response rate is surprisingly good because most business owners appreciate someone taking the time to look at their site and give useful feedback. A lot of the replies are basically: "Sure, as long as it's free." Or: "Who says no to a free website redesign?" That's when I call them. I tell them I've already created the redesign and would like to walk them through it on Google Meet. The funny thing is I can build these drafts incredibly fast with AI, so by the time we talk, I already have something to show. During the presentation, even though I position it as a free redesign, most prospects end up asking: "How much would this cost to me?" That's where the sale happens. Depending on the business, I charge anywhere from $500 to $5,000 upfront, plus a monthly fee between $50 and $150 for hosting, maintenance, updates, support, and small changes. This approach has worked really well because the offer feels low risk for the client. They get value before they ever have to make a buying decision. For anyone curious about the stack I use: Swokei for lead generation, website analysis, and personalized outreach. Claude Code for building websites. Hetzner for hosting (moved from Cloudflare). Google Workspace for email. Google Meet for sales calls. Nothing revolutionary. Just a simple offer that's easy for businesses to say yes to. Curious what outreach methods are working for other agency owners right now. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalThe Difference Between a $500 Client and a $5,000 Client
For the longest time, I thought landing higher paying web design clients required some secret sales strategy or better closing skills. After looking through my client reports every month, I realized something interesting. The difference between landing a client paying $500 and one paying $5,000 usually comes down to positioning and who you're targeting. With bigger companies, it takes more effort to find the right person involved in website decisions. Smaller businesses are easier because you can usually reach the owner directly. But the outreach process I'm using now works for both. I don't cold call anymore. Instead, I run automated email campaigns with an offer that's extremely hard to ignore. The first step is getting a list of businesses that already have websites. This is important. I don't target businesses without websites because the whole strategy depends on offering them a better version of their current website. Once I have the list, I put the businesses into a campaign and choose my campaign settings and offer. The options usually include starting a conversation, booking a meeting, or offering a free website draft. I always choose the offer as free website draft. Then I set a quality threshold. Mine is 7/10. Any website scoring above that gets skipped because there's no point trying to sell a redesign to a business that already has a great website. After that, I launch the analysis. Every website gets scored and reviewed for design, speed, SEO, layout, and mobile optimization. Then a personalized email is generated explaining what could be improved. Not one of those generic reports full of random scores and numbers, but an actual explanation written in plain language. The response rate is surprisingly good because most business owners appreciate someone taking the time to look at their site and give useful feedback. A lot of the replies are basically: "Sure, as long as it's free." Or: "Who says no to a free website redesign?" That's when I call them. I tell them I've already created the redesign and would like to walk them through it on Google Meet. The funny thing is I can build these drafts incredibly fast with AI, so by the time we talk, I already have something to show. During the presentation, even though I position it as a free redesign, most prospects end up asking: "How much would this cost to me?" That's where the sale happens. Depending on the business, I charge anywhere from $500 to $5,000 upfront, plus a monthly fee between $50 and $150 for hosting, maintenance, updates, support, and small changes. This approach has worked really well because the offer feels low risk for the client. They get value before they ever have to make a buying decision. For anyone curious about the stack I use: Swokei for lead generation, website analysis, and personalized outreach. Claude Code for building websites. Hetzner for hosting (moved from Cloudflare). Google Workspace for email. Google Meet for sales calls. Nothing revolutionary. Just a simple offer that's easy for businesses to say yes to. Curious what outreach methods are working for other agency owners right now. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalThe $20K/Month Website Redesign Blueprint Nobody Talks About
So I’m writing this for anyone running a web agency who’s struggling to get consistent clients or build scalable systems. I understand how stressful it can be because I was in the exact same position. I’ve been running my web agency for 4 years, but only in the last year did I start using AI seriously, and honestly it changed everything for me. I used to build websites on WordPress and do all my outreach manually. It worked, but it was inconsistent and exhausting. Once I started implementing AI into my business, I went from constantly chasing clients to doing around $20k/month recurring. This is basically what changed for me. At first I was targeting businesses with no websites, but switching to businesses that already had websites worked way better. There are SO many businesses with outdated websites that clearly need upgrading. Plus, these business owners already understand the value of having a website because they’ve already paid for one before. It’s way easier convincing someone to improve something they already believe in than trying to convince someone from zero. The second big shift was moving from manual outreach to automated email outreach that actually feels personalized. Instead of sending generic emails, I now use a tool called swokei that mass analyzes a business’s website and generates personalized outreach based on things like design issues, SEO problems, site speed, mobile optimization, and overall user experience. I run all of my outreach campaigns through it. The third thing that changed everything was offering a free redesigned draft version of their current website. Realistically, who says no to free? I can build these drafts really quickly using Claude Code, and most of the time they already look way more modern than the client’s existing site. Once business owners see a better version of their own company in front of them, selling becomes way easier. Another huge mistake I used to make was just sending preview links through email. They open it later when they’re busy, nobody’s there to explain the improvements properly, and eventually the lead goes cold. Now I always present the website live on Google Meet and try to close them on the spot. That alone massively increased my close rate. Also, always charge upfront for the website build, but don’t ignore monthly recurring revenue. Hosting, maintenance, edits, SEO, ongoing changes, etc. That’s where stability comes from if you actually want predictable income every month instead of constantly hunting for new clients. For anyone curious about the tools I use, it’s honestly pretty simple. Apollo for finding leads because you basically never run out of businesses to contact. Swokei for outreach. I upload my lead list there and it analyzes each business website, scores it, and turns flaws in design, SEO, speed, and mobile optimization into personalized outreach emails automatically. Pointing out actual issues on their website increased my reply rates massively. Claude Code for building websites. And honestly, people saying AI built websites don’t perform well are just wrong. If you know what you’re doing, you can build pretty much anything now. And Cloudflare for hosting client websites. That’s pretty much the system I run now. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalHow To Get Web Design Clients
Running a web agency is honestly a lot harder than most people think. I've talked to a lot of web designers and agency owners over the years, and everyone seems to have a completely different way of getting clients. Some swear by paid ads, others rely on referrals, SEO, cold calling, LinkedIn outreach, email marketing, and so on. What surprises me is that I rarely hear anyone talking about the strategy that has worked best for me. The biggest challenge with running a web agency as a solo founder is that you're wearing every hat. You're building websites, maintaining websites, handling support requests, fixing bugs, making client changes, managing hosting, answering messages, and dealing with everything else that comes with running a business. The question is, when are you supposed to do outreach? That's why I prefer email outreach. The reason is simple. It works for me in the background while I'm doing everything else. I don't have to spend hours every day cold calling businesses or manually searching for leads. The system keeps working while I focus on servicing existing clients. But I don't do email outreach in the traditional way. Most people are blasting generic emails through tools like Instantly or Klaviyo. The problem is that business owners get those emails every day and can spot them immediately. What I do instead is use a tool called Swokei. I simply upload a batch of business websites, and the tool analyzes each one individually. It looks at things like design issues, SEO problems, mobile optimization, layout weaknesses, and other things that could be hurting conversions. It then generates a personalized outreach message based on the specific problems it finds on that business's website. The result is that I can run highly personalized outreach campaigns without spending hours manually reviewing websites and writing custom emails one by one. Another thing I like is that before running the analysis, you can choose the offer you want to lead with. You can start conversations, try to book meetings, or offer a free draft. I always choose the free draft option. When a business owner replies and says they're interested in seeing what their website could look like, I never build the site and send it over email. Instead, I reply with something like: "Sounds great. When are you free for a quick 10 to 15 minute Google Meet so I can show you what I have in mind?" Then I book the call. Before the meeting, I use AI tools to create a redesigned version of their website. It usually takes a very short amount of time. Most of the businesses I'm reaching out to have outdated websites, so even a solid AI assisted redesign looks significantly better than what they're currently using. Then I present it live during the meeting. This is where the real selling happens. They're seeing a better version of their business online, customized specifically for them, and you're there to answer questions and handle objections in real time. If they're interested, I close them on the call with a one time website fee plus a monthly hosting, maintenance, and support package. For hosting, I mainly use Hetzner and Cloudflare. They're reliable, affordable, and make it easy to scale when you start getting more clients. One thing I've learned is that you should never send the redesign over email. The meeting is where you have the highest chance of closing the deal because you can walk them through the improvements, explain the reasoning behind the changes, and answer any concerns on the spot. So my stack is pretty simple. Hetzner and Cloudflare for hosting. Swokei for website analysis and personalized outreach. Claude for building website drafts and speeding up development. That's basically it. No paid ads. No cold calling. No spending hours writing personalized emails manually. Just finding businesses with weak websites, showing them a better version, and having a conversation. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalWorked on the Claude buddy firmware for cardputer, for the t-Lora pager. The OG cardputer zero.
-Claude chat- using haiku for quick responses. -Gmail inbox- for read and write gmail. -Meshtastic- for radio nerds to muck up their local mesh. -Genius Loci- WiFi tarot card reader to read the room. -Flock spotter- intrusive AI camera identifier. -Settings- WiFi, sound, and cloudflare worker config. submitted by /u/poon_goon [link] [comments]
View originalIt's kinda scary how good Claude is at coding now
Hey all, I'm a professional software engineer with over 10 yoe so long before AI. At first I was very skeptical about using AI to code. At first it was trash but it's gotten so good over the last year it's impossible not to use it. Even still, a lot of people say that the downside is you don't get to learn the systems as well. That's partially true in that you don't get to learn the languages as well but I find that it's helped me learn systems much much faster. I recently started making a little web game, which I won't link as to not be an advertisement, with the overall goal of learning web sockets and Cloudflare's infrastructure. The idea was simple, players try and keep a balloon from touching the ground but on a large scale in real-time. In a weekend I was able to create a fully scalable (albeit simple) MMO web game complete with auth, session management, horizontal auto-scaling, and matchmaking. There is absolutely no way I could have done that in so little time otherwise. The industry is always changing and this time even faster than before which is totally scary but it's also very cool. I'm just glad that I'm at least still able to learn and not just "Claude do this" without really knowing what's going on. If anything it's let me focus more on design and architecture and less on random idiosyncratic details. Anyways tldr; Software Engineering is still cool and still challenging just faster. Edit: grammar submitted by /u/8bitAlexx [link] [comments]
View originalBuilt with Claude Code: pidgin.sh — let Claude share artifacts as URLs
I kept running into the same friction with Claude Code: it'd generate something nice (an HTML mockup, a report, a plot, a one-pager) and then I'd have to manually save it, find somewhere to host it, and send a link. So I built pidgin.sh, a service plus an agent skill that lets Claude upload a file and hand back a public URL in one step. What it does You install the pidgin-share skill (npx skills add pidgin-sh/skills -g — works in Claude Code, Cursor, Codex, etc.). Ask Claude: "share this file as a pidgin URL". It uploads via the API and prints back something like jane.pidgin.sh/abc123/report.html. Each user gets their own subdomain; URLs include a random privacy token so they're unlisted by default. Paid plans add a response channel: artifacts can collect replies (polls, approvals, design picks, RSVPs) and the agent waits for the results before continuing. How Claude helped I wrote the whole thing in Claude Code — the Cloudflare Workers backend (R2 + D1 + KV), the GitHub OAuth + Stripe billing wiring, the dashboard UI, the skill itself, the docs. Link: https://pidgin.sh Skill repo: https://github.com/pidgin-sh/skills Happy to answer questions! submitted by /u/bradleyboy [link] [comments]
View originalClaudeBot scrapes roughly 11,000 pages for every 1 visitor it sends back. Down from ~60,000. Is that… fine?
I fell down a rabbit hole on this last week. Quick version: Last June Cloudflare's CEO put numbers on the crawl-to-referral gap. A decade ago Google crawled about 2 pages for every visitor it sent you. Now it's around 18. Then the AI bots: OpenAI was about 1,500 pages per referral, and ClaudeBot peaked near 60,000. It's improved a lot since (Anthropic launched web search and started sending some traffic back, so it's closer to 11,000:1 now), but that's still eleven thousand pages scraped for one person who actually clicks. The bit I can't get past is that traffic used to be the way many website monetize themself. You let the crawler in, it sends you readers, the readers pay the bills somehow. For AI that loop just never closes, and no SEO trick fixes it because the visitor was never going to show up. My best guess at what replaces it: For anyone publishing something an agent might want, the useful surface stops being a webpage and becomes something an agent can call directly. This could be an MCP or something else. You expose an endpoint, the agent pulls the exact slice it needs, and you can meter or charge for it instead of praying for a click. Almost no big publisher is doing this yet, which is either the opportunity or a sign it's a dumb idea. Here is the original blog post from Cloudeflare. In order to document my thoughts I put together a longer writeup that evaluates potential angles of how this could play out, with the actual numbers and sources: Writeup Where I'm not sure: A lot of you think MCP is already on the way out and it's all CLIs and skills now. So does a callable web actually happen, or do agents just keep scraping HTML forever because it's the path of least resistance? submitted by /u/Ok-Constant6488 [link] [comments]
View originalHow I Sold 200 Websites in 12 Months
In the last 12 months I’ve managed to sell around 200 websites. And before people ask, no, I don’t run some massive agency with a huge team. It’s literally just me and my partner. The only reason we’ve been able to move that fast is because we automated almost everything and built systems that actually scale. The best web designer in the world will eventually lose to some random teenager using AI and systems properly. That’s just where things are going. One of the biggest changes I made was completely quitting manual outreach. It takes too much time and it’s impossible to scale properly. A lot of people automate outreach already, but most of them just send generic “we can redesign your website” emails that everyone ignores. What we do is different. We scrape thousands of businesses, automatically analyze their websites, and generate personalized outreach based on actual issues on their site like bad design, poor mobile optimization, weak SEO, slow load times, layout problems, and stuff like that. So instead of manually checking every website and writing every message ourselves, the entire process is automated from analysis to ready to send campaigns. Another thing that changed a lot for us was automating SEO blogging. SEO compounds hard over time and once your articles start ranking, businesses start coming to you instead of you chasing them. That alone changed a lot for us. The other massive shift was how we build websites. I used to be a full WordPress developer and spent way too much time building everything manually. Now we build almost everything with AI. It’s way faster, delivery is easier, and clients care way more about the final result than how the website was actually made. For anyone wondering, the stack is pretty simple. Apollo for leads. Swokei for website analysis and outreach campaigns. Soro for SEO blogging. Claude Code for building websites. Cloudflare for hosting. That’s pretty much the entire setup. Most people running agencies are still doing everything manually and burning themselves out for no reason. Systems and automation change everything. submitted by /u/Murky_Explanation_73 [link] [comments]
View originalI launched a brand-new author identity with zero web presence. An AI cited him correctly in 6 days — while a firewall blocked every AI crawler from the site the whole time
I ran a small experiment on myself and the result broke my mental model of how AI "knows" things, so I'm sharing it. The setup: on May 11 I created a brand-new pseudonymous fantasy author entity ("Marin T. Kael") with no prior web footprint and no published book yet. Then I asked 5 web-connected AI systems the same 16 questions, every day, for 23 days, and scored every answer (+1 correct/source-grounded, 0 not found, -1 hallucinated). About 16,000 scored datapoints. The whole thing was pre-registered before I started, n=1, and I logged the failures publicly. It's a measurement, not a success story. Here's the part that messed with my head. An AI cited the entity correctly on day 6. Google had a Knowledge Graph entry by day 4. And for 22 of those 23 days, the website's firewall was returning HTTP 403 to every single AI crawler. I didn't set that block on purpose — Cloudflare now silently opts new domains out of AI crawling by default. So the AIs never read the site. They got the entity anyway, by stitching it together from the Knowledge Graph (Wikidata) and third-party mentions at the moment you ask. The "front door" was bolted shut the entire time and it didn't matter. (Honest caveat: because the crawlers were blocked, I can't tell you anything about llms.txt or on-site optimization.) Other surprises: it's not a "smarter model = better" story, it's a retrieval story. OpenAI's newest web model hit 4.7 correct per 1 hallucinated; Gemini went net-negative — and grounded on the entity ONLY via Reddit (17/17), while OpenAI hit the entity's own domain 119x. Going viral did nothing: a 23x Reddit-karma jump produced zero citation lift. Structured identity (Wikidata, site, DOIs) moved the needle; reach didn't. And the controls caught the models fabricating a "Wikipedia" source 24 times for an entity with no Wikipedia page. n=1 with me as investigator and subject is the obvious limit — which is why it's pre-registered with a public failure log. Everything's open: Report + data (Zenodo, CC-BY): https://doi.org/10.5281/zenodo.20549020?utm_source=reddit Code (MIT): https://github.com/marintkael/marin-research-tools Dataset: https://huggingface.co/datasets/marintkael/ai-citation-fidelity submitted by /u/marintkael [link] [comments]
View original‘Bots have now passed human traffic online,’ Cloudflare boss laments — says agentic traffic wasn’t expected to eclipse real people until next year
submitted by /u/EchoOfOppenheimer [link] [comments]
View originalYes, Cloudflare offers a free tier. Pricing found: $0 /month, $20 /mo, $25/mo, $200 /mo, $250/mo
Cloudflare has an average rating of 4.3 out of 5 stars based on 20 reviews from G2, Capterra, and TrustRadius.
Key features include: Run everywhere, Run anywhere, Run at massive scale, Fighting infra with “cloud”, Pay for clean traffic, Custom, Fits into your existing workflows, One network for users, apps, and data.
Cloudflare is commonly used for: Build and secure AI agents.
Cloudflare integrates with: Vercel, Supabase, Discord, Zendesk, Investec, AWS, Google Cloud, Microsoft Azure, Heroku, GitHub.
Mistral AI
Company at Mistral AI
2 mentions
Based on user reviews and social mentions, the most common pain points are: token usage, API bill, anthropic bill, token cost.
Based on 102 social mentions analyzed, 19% of sentiment is positive, 80% neutral, and 1% negative.