Stopnetic product walkthrough English narration transcript Demo data and sample website; computer-generated voice. Protect your website from unwanted bots and AI scraping with Stopnetic. Your server checks requests before releasing protected pages or data. Let's start with the protection controls, then walk through the setup. Enable automation checks to block detected bot signals. Require browser verification on guarded pages, and protect the data those pages load. When your rules deny a request, your protected content stays on your server. Control repeated access with request limits and data budgets. Set how quickly requests can arrive, and how much data an allowed call can use. These controls help reduce scraping bursts before protected responses are released. First, add your website and verify that you own the domain. You don't need to move your hosting. Your website stays where it is, and a server guard connects it to Stopnetic. Next, follow the setup guide for your Next.js or JavaScript server project. Install the guard, then deploy it. Remember to cover your private APIs and downloads too. A browser- only setup can't protect content before it's sent. Once you're connected, this is your overview. You can see allowed, challenged, and blocked requests in one place. Choose a time period, or switch to another website. We're using sample traffic for this tour. Now, let's look at Policies. Keep your public pages open, ask visitors to complete a browser check, or block a path. Rules run from top to bottom, so put specific exceptions above broader rules. Say you're building a website for a client, but you're not ready to show everyone. Turn on a preview password for the whole guarded site, or just selected pages. Save it, then share the link and password privately. This is what your client sees when they open the link. Your protected content stays behind the password screen. They just enter the password you've shared. There's no account to create. And here's the preview, unlocked. Access can last up to twelve hours in the same browser. Saving the preview settings revokes previous unlocks. Keep in mind, anyone with the password can pass it on. Want visitors to start the check themselves? Choose the optional checkbox flow. They'll select Verify to continue, which starts browser verification. Keep your own login and permissions for private content tied to a user account. You can also limit repeated requests. Choose a refill rate and a burst allowance to help reduce rapid refreshes and repeated API calls. People on the same network share the limit. This needs trusted Vercel network protection. For APIs, you can go a step further and budget the records returned, or actions performed. Your server declares the maximum cost, and your app enforces it. Set up the cost callback and trusted Vercel network protection first. To see what's happening, open Event explorer. You'll find access decisions, reason codes, and any reported country or device details. Use the filters to narrow things down. Growth and Ultimate plans also offer Excel downloads. Traffic insights give you a broader view of reported countries and devices. These are request counts, not individual people or proof of identity. Use the information to review your traffic and adjust your rules. That's the basic flow. Connect your server, set a rule, and test a real request. Then check the results in Stopnetic. Keep your hosting, and manage access from one workspace.