AIPM Defense · Tier 2

Valve

Name: AIPM Defense Valve
Brand: AIPM
Price: 499 USD
Availability: InStock

One-click allow/deny for 40+ AI crawlers, applied to your CDN. Named stances. Continuous proof.

$499 / month

Start Valve → Back to overview

Stripe checkout coming this week. Onboarding includes CDN credential review call.

Everything in Observatory, plus policy

Observatory tells you who's crawling. Valve lets you do something about it. Per-vendor. Per-stance. With audit-log proof that the policy is actually applied — because we read the same log to confirm the block is firing.

Named stances (one click each)

Training Opt-Out

blocks: GPTBot, ClaudeBot, Google-Extended, CCBot, anthropic-ai, Bytespider, FacebookBot, Meta-ExternalAgent, Applebot-Extended

Keeps retrieval bots and traditional search. Denies the crawlers that feed future training sets. The stance most privacy-conscious brands actually want.

Retrieval-Only

allows: OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Googlebot, Bingbot · blocks: training crawlers

AI assistants can cite you live at query time. Training crawlers don't ingest you. Useful for publishers and news outlets with IP concerns.

Pre-Launch Stealth

blocks: all AI crawlers · allows: Googlebot, Bingbot

Your product announcement ships next month. You don't want models trained today to "know" about it. Block training crawlers now; flip to Retrieval-Only on launch day. Audit log proves the exclusion window.

Full Blackout

blocks: everything AI · allows: traditional search bots

The nuclear option. Nothing AI-shaped sees the site. Traditional search still works. Some legal cases require this for discovery windows.

Custom

per-crawler rules

Allow Claude. Block ChatGPT. Challenge Perplexity with a CAPTCHA. Rate-limit Bytespider. Anything the CDN can express, we can automate.

CDN support matrix

CDN	Integration	Verified-bot primitive	Audit log
Cloudflare	Native	`cf.client.bot` + Super Bot Fight Mode	GraphQL, per-request
Akamai	Managed rules	Bot Manager Premier (Known Bot Directory)	Per-request
Fastly	Managed rules	NGWAF + ACL via VCL	Per-request
AWS CloudFront	On request	WAF Bot Control (paid) or custom Lambda@Edge	CloudWatch, coarse
Azure Front Door	On request	WAF managed rules + reverse-DNS Lambda	Log Analytics, coarse
Other	Forensics tier	Custom engagement	Varies

If you're on Cloudflare, onboarding takes one video call and the rule goes live the same day. Akamai and Fastly typically take a week end-to-end because of your ops team's change-control, not ours.

The workflow

You pick a stance (or we build one with you).
We push the rule to your CDN through a service account you own and can revoke.
The audit log records the rule, the fires, and the exemptions.
You get a weekly attestation: "Policy X was continuously enforced from date Y to date Z, N requests allowed, M denied."
If anything drifts, Observatory alerts fire within the hour.

The Honest Version

We don't host your content. We don't sit inline. We hand your CDN a managed rule and read the log back. If you fire us, the rules stay; you just stop getting updates and attestations. The lock-in is the maintenance and the receipts, not the enforcement point.