Block scrapers posing as browsers in Vercel Firewall
Sumly keeps bots that pretend to be people out of your numbers, and with a token scoped to your project adds a Vercel Firewall custom rule that denies their network: in one click, through your assistant, or by itself.
-
AstroChart Google Play · in the app 🇪🇸 +€9.99
-
Humanize Stripe · on the site · from Facebook 🇿🇦 +€11.04
- TimeLoop App Store · in the app · via RevenueCat 🇺🇸 +€29.99
-
The live demo: our own apps, with example numbers.
Blocking in three steps
A token for the one project, pasted once. Custom rules are on every Vercel plan.
-
1
In Vercel, open Account settings › Tokens › Create and scope the token to the project (or its team).
-
2
In Sumly, open Projects and payments, the project, Bots & blocking, choose Vercel, paste the token and the project's name or ID. Sumly checks it can read the project's firewall.
-
3
Under Insights › Bots › Disguised scrapers, press Block in Vercel, or turn on the autopilot.
What you see
Vercel next to every other project and provider, on the same pages.
Bots
Disguised scrapers, each with Block in Vercel, and Undo once it is denied.
Overview
One card while a project is being scraped, with the button.
Alerts
One Bot attack notice per attack, in the bell and the app.
Visitors and Live
How many page views the Smart bot filter kept out.
Counts toward your plan
Nothing: the Smart bot filter and blocking are on every Sumly plan, and custom rules are on every Vercel plan. Plans →
What you don't get
Nothing else in Vercel is read or changed: deployments, settings and your own firewall rules stay as they are.
The details
What Sumly adds to Vercel Firewall
- For a scraper network, one custom rule: geo_as_number is the network's number, action Deny.
- For scrapers crowding one part of the site: path starts with it, action Challenge.
- Added one rule at a time (rules.insert) next to yours, never by writing the whole firewall config. Each is named sumly_…, so Sumly finds its own and never touches yours.
When Sumly adds a rule
- When you press Block or Challenge, or your assistant calls block_bot and you confirm.
- By itself only with the autopilot on (off by default), for clear cloud scraper networks, and the alert says so.
- Undo removes Sumly's rule alone (rules.remove). A network you took back is never blocked by the autopilot again.
Good to know
- Hobby has 3 custom rules a project, Pro 40, Enterprise 250: each scraper Sumly blocks takes one.
- The rule denies the whole network. Unlike Cloudflare, no exception for verified bots is added, as Vercel documents no such condition for custom rules.
- A network that also carries people at home or on their phones is never blocked whole.
- Disconnecting deletes the token. Rules already added stay until you take them back.
Vercel questions
Which token should I make?
One scoped to the project: Vercel then refuses it for anything else. A team-scoped token works too; a full-account token needs the team's ID.
Does it work on Hobby?
Yes. Hobby has 3 custom rules a project, so Sumly can block up to 3 scrapers there next to none of your own.
Can I undo it?
Yes: Undo block on the scraper's row, or delete the sumly_… rule under the project's Firewall.
Will my other firewall rules change?
No. Sumly adds and removes only its own rules, one at a time, and never writes the whole configuration.
Other integrations
Shopify
Try it with your own projects
Sign in with Google or a code by e-mail and connect your first project. The first 14 days of a paid plan are free, with no card.
Start free trialOr look around first: open the live demo.