SITEBORNE SIGNAL MODULE
ResourceMatch — guided tool and resource recommendations
Ranks resources by requirement fit, reliability, privacy, accessibility, cost, portability, and support—never commission first.
BUSINESS OUTCOME
What this capability changes.
- Reduce research burden
- Disclose limitations
- Preserve migration options
Best for
Field Guide readers, Cost-conscious businesses, Buyers comparing tools
From $2,000
Care from $150/month
PLAIN LANGUAGE, TECHNICAL PROOF
What ResourceMatch does.
Compares tools and resources against what a buyer actually needs, not which link pays the most.
A buyer gets a reasoned shortlist with costs, limitations, privacy, and migration concerns visible before choosing.
A real-world use
A privacy-focused team sees Cloudflare Web Analytics ahead of more invasive products, with the implementation tradeoffs stated.
FOR TECHNICAL READERS
How the control model works
Typed criteria and freshness rules produce the ranking. Affiliate status is a disclosed attribute and cannot improve rank.
Failure path: Typed filters and visible comparison table.
INTERACTIVE WALKTHROUGH
Use ResourceMatch before discussing it.
Choose the factor that matters most and inspect both the recommendation and its limitation.
The interaction uses your input and identifies whether it runs locally, checks this live site, or previews a production control. It does not disguise seeded output as intelligence.
System view
Required
cloudflare-d1, cloudflare-workers
Optional
cloudflare-vectorize, cloudflare-workers-ai
Fallback
Typed filters and visible comparison table.
cloudflare-d1, cloudflare-workers, cloudflare-vectorize, cloudflare-workers-ai
2026-08-02
Provider limits, terms, model availability, and pricing may change. Production accounts remain client-owned.
Data classification
- Preference selections
- Public resource metadata
LAUNCH ALLOWANCE
Semantic retrieval
Prototype and low-volume vector storage and query capacity.
Upgrade triggers
- verification age — over 90 days. Mark review due or quarantine.
- affiliate conflict — any. Show alternative and disclosure.
View implementation proof
Decision rationale
The implementation favors semantic HTML, static rendering, typed content, and isolated on-demand routes. Optional AI never controls pricing, eligibility, or emergency routing.
Controls
- WCAG 2.2 AA target
- Provider-neutral adapters
- Usage caps and kill switches
- Client-owned production accounts
- Conventional fallbacks
Verified evidence
- The browser demonstration runs from a clean clone without a paid credential.
- Kill switch and allowance states are typed configuration.
- Primary navigation and contact paths remain independent of this module.
Known limitation
External provider allowances and production behavior require owner accounts and deployment-time verification.