Adobe Commerce bot protection depends on your hosting model. Start by naming your deployment and who can change its security rules. Peakhour offers bot policy, rate limits and request logs for teams that want to manage these controls together.
What Adobe Commerce provides
Adobe separates Commerce into SaaS, Cloud Infrastructure (PaaS) and on-premises deployments. Each gives merchants a different level of control. Adobe deployment comparison.
For PaaS projects, Adobe offers the Fastly-powered Advanced Security add-on with bot management and advanced rate limiting. Bot-rule changes currently go through Adobe Commerce Support. Confirm which services your project has enabled. Adobe Advanced Security.
Adobe documents origin cloaking that enforces Cloud Infrastructure traffic through Fastly. Added security needs a design that preserves this path. Fastly services.
Where Peakhour can help
Peakhour bot management combines IP and proxy information, network fingerprints, request behaviour and route context. Policies can allow, log, challenge, rate limit or block traffic. Logs connect the action to the request for review.
Advanced rate limiting supports counters keyed by IP, headers, cookies, TLS fingerprints or HTTP/2 fingerprints. Response-based counters can track failed requests. Test these controls against repeated login failures and catalogue scraping.
The Magento integration supports cache tags and cache variation. The caching plugin has a separate role from bot policy. Check your Commerce version and extension support before a trial. For Adobe’s SaaS service, confirm which integrations Adobe supports before planning changes.
Why keep the existing stack?
Keeping Adobe and Fastly may suit a PaaS store whose support process and bot controls meet its needs. It preserves an established delivery path and team workflow. For merchant-hosted Commerce, inventory your host and edge services.
Peakhour supports deployment alongside an existing edge. Agree on routing, how rules are applied, logs and support responsibilities before making changes.
Evaluate with real store traffic
- Test catalogue scraping, repeated login failures, search crawlers and approved integrations.
- Run shopper journeys through login, cart and checkout, including mobile clients.
- Compare unwanted requests reaching Commerce, blocked valid requests and time needed to tune a rule.
- Confirm who changes each policy, reviews logs and handles urgent exceptions.
Start with observation, agree on exceptions, then enable a limited policy with a rollback plan. Use the same routes and review period for each option.
Contact Peakhour to review your Commerce deployment and plan a bot-management evaluation.
Official sources checked: 6 November 2026.