See it. Act on it. Automate it.
Every plan is per site, cancel anytime. Each tier is everything before it, plus one more level of power.
❯ No free tier — the intelligence we build on your traffic has exactly one buyer: you.- ❯Every bot & AI agent named and classified
- ❯Verified vs. claimed identity — impostors caught against operators' own published records
- ❯Impact scoring: cost (bandwidth $) vs. earn (referrals, citations, assistant traffic)
- ❯Clean human-only analytics baseline — bots fully separated
- ❯Weekly email digest — impostors flagged
- ❯30-day history
- EVERYTHING IN SEE, PLUS:
- ❯❯Per-class toggles: block impostors, throttle scrapers, welcome assistants
- ❯❯Smart suggestions backed by your own traffic evidence
- ❯❯Dry-run preview: see exactly what would happen before anything does
- ❯❯Never-block-search interlock — rankings structurally protected
- ❯❯Cost/earn receipts — exportable evidence for licensing talks
- ❯❯12-month history + exports
- EVERYTHING IN ACT, PLUS:
- ❯❯❯Auto-pilot: new scrapers & impostors handled by your standing policy the moment they appear
- ❯❯❯Anomaly response: crawl-spike throttling with auto-release
- ❯❯❯Auto-updated rules as operators rotate IPs & identities daily
- ❯❯❯Every automated action logged, explained & reversible
- ❯❯❯API access + webhooks
- ❯❯❯Priority support
Why isn't there a free plan?
Free analytics products have to make money somehow — usually with your data. Frenemy's only revenue is your subscription, so our only incentive is being worth it. Subscribing buys the whole truth about your traffic, an alignment guarantee, and a vendor that will still exist next year.
Try the whole thing free for 14 days — full SEE + ACT access, no card up front, keep your data either way.
Vantage comparison
Where Frenemy sits in your stack decides what it can watch and where it can act. All three installs run the same brain on 100% of what they see; the difference is the vantage point.
| Aspect | Cloudflare Workerv0.2 · any stack behind CF | Next.js middlewarev0.2 | WordPress pluginv0.3 · no CF needed |
|---|---|---|---|
| Every bot & AI agent named & classified | ✅ same engine, 100% of what it sees | ✅ same engine, 100% of what it sees | ✅ same engine, 100% of what it sees |
| Per-crawler cost / earn ledger | ✅ bytes out vs. visits back, per agent | ✅ bytes out vs. visits back, per agent | ✅ bytes out vs. visits back, per agent |
| Safe by default | ✅ never-block-search · fails open · kill switch | ✅ never-block-search · fails open · kill switch | ✅ never-block-search · fails open · kill switch |
| Install | Paste one Worker + set 2 variables + 1 route (~5 min) | Add the middleware to your app + deploy | Install → Activate → paste your key (~90 s) |
| Where it sits | The edge — in front of EVERYTHING | Inside your app, before your routes | Inside WordPress, after your host's web server |
| Sees static files/assets | ✅ everything the zone serves that reaches the Worker — what Cloudflare blocks at the zone level is blocked before any Worker runs | ⚠️ only what the middleware matcher covers | ❌ only requests that reach PHP |
| Response facts (status / bytes / duration) | ✅ measured | ❌ can't measure (runs before the response exists) — never a fabricated 0 | ⚠️ status + duration measured; bytes usually can't be measured — never a fabricated 0 |
| "Verified" badges (IP checks) | ✅ full strength — Cloudflare hands us the true client IP | ⚠️ full strength behind CF or a configured proxy; otherwise capped at "claimed" | ⚠️ depends on the host's headers; unknown hosts cap at "claimed" |
| Where blocks happen (ACT) | At the edge — a blocked request never touches your server | At your app's front door — server touched, page never built | Inside WP — server touched, page never built |
| Bandwidth actually saved by a block | ✅ yes | partial | partial |
| Data freshness (who's who) | Updated with each template refresh | Updated with each deploy | Updated with plugin updates (mechanism is a v0.3 design decision — may fetch daily) |
Common questions
The honest short answers. Full help in the FAQ.
When can I actually block?
Enforcement is built, and it ships deliberately: per-site, opt-in, only after your own observe data has proven the classifications on your traffic. Blocking a real search crawler by accident is the one mistake we refuse to ship. ACT's dry-run shows you exactly what every rule would have done — so when the crawler landscape shifts this September, you'll already know your answer.
If I go over my plan's limit, do you stop protecting me?
No. Enforcement never stops or samples — it runs on every request regardless. The limit only affects how many individual bot events we store for drill-down; your totals and the dollar ledger stay exact.
Is the dollar figure real?
It's an estimate, always labeled as one: measured bytes × a rate you set. The bytes are measured; the dollar is your assumption made visible — never a fake invoice.
Is it safe? Can Frenemy break my site?
Frenemy fails open — if we ever go down, you don't. Verified search engines are never blocked by default, enforcement is opt-in and off until you turn it on, and everything Frenemy can do turns off with one switch. Safe isn't a mode; it's the default.