Supported hosts
This is a candid status page. We publish it so you know what works and what doesn't before you sign up. The policy is simple:
- Tier 1+2 (HTTP + Playwright headless) is supported and reliable. Most
Shopify, WooCommerce, BigCommerce, and Magento storefronts that don't put Cloudflare in front of the platform sit in this bucket. Our adaptive selector memory and per-host sitepacks survive template drift on these reliably.
- Cloudflare-as-add-on stores (Shopify+CF, BigCommerce+CF, etc.) are
currently not reliably supported on v1. Our tier-3 stealth implementation doesn't reliably get past Cloudflare's enterprise-tier filtering. We're working on it (residential proxies + provider-specific solvers); track progress in our changelog.
- Major retailers behind enterprise anti-bot (Akamai BotManager,
PerimeterX/HUMAN, layered defenses) — Walmart, Best Buy, Target, Macy's, etc. — are out of scope for v1. Don't sign up if these are your primary targets. They're solid v2 territory once we have residential proxies + custom solvers.
Last benchmark — 2026-05-05
10-host benchmark from the mid-sized DTC long tail (Shopify-platform stores). Tier 1+2 only, no proxies, no solvers. Source: scripts/longtail_targets.yaml. Reproducible:
python scripts/tier3_spike.py --targets scripts/longtail_targets.yaml --tiers 1,2 --gate 70 --no-llm
| Host | Platform | Result | Latency |
|---|---|---|---|
allbirds.com | Shopify | ✅ extracts product | ~1s |
bombas.com | Shopify | ✅ extracts product | ~5s |
casper.com | Shopify | ✅ extracts product | ~7s |
hellotushy.com | Shopify | ✅ extracts product | ~7s |
kettleandfire.com | Shopify Plus | ✅ extracts product | ~6s |
outdoorvoices.com | Shopify | ✅ extracts product | ~1s |
rothys.com | Shopify | ✅ extracts product | ~13s |
brooklinen.com | Shopify + Cloudflare | ❌ anti-bot block (hcaptcha) | n/a |
deathwishcoffee.com | Shopify + Cloudflare | ❌ anti-bot block (hcaptcha) | n/a |
solostove.com | BigCommerce + Cloudflare | ❌ anti-bot block (CF interstitial) | n/a |
Success rate: 7/10 (70%). The 3 failures are concentrated on stores that deploy Cloudflare in front of their commerce platform.
How we recommend you use this
- Test before you commit. Send a few representative URLs from your target
sites through the free tier. The free tier exists for exactly this — kick the tires before paying.
- Read the response, not just the status. Every failure response includes
a structured failure object with kind, tier_attempted, retryable, and hint. Branch on kind, not on free-text.
anti_bot_blockis a "this host won't work" signal. When you see it
on tier 2, our orchestrator's per-host learning will skip tier-3 on that host for 24h after 3 consecutive failures (so you don't burn 5 minutes on the inevitable timeout). Move on or wait for the v2 premium tier.
v2 roadmap (not committed dates)
- Residential proxy pool integration
- Per-provider solvers (Akamai BotManager, PerimeterX, HUMAN)
- Tier 4 (real Chrome via CDP attach) for the highest-friction sites
- Per-host sitepacks for sites where structured data is hidden behind dynamic
rendering