Clear answers.
Confident decisions.
Understand compatibility, crawler handling, operational behaviour, and the path to a controlled rollout.
A little more
peace of mind.
Intelligent bot protection.
Is TraBotPro a CDN or a replacement for my hosting?
No. It adds a local decision layer to your existing Hypernode setup. NGINX continues handling TLS and forwarding traffic to Varnish or PHP-FPM.
Will it block search engines and AI crawlers?
Known bots are verified, then handled according to policy. Search engines, AI search, AI training, social previews, and SEO tools can have different policies, with site-specific overrides.
What happens if the central console is unavailable?
The edge keeps its last known good configuration. Requests do not depend on the console or its database. Local decision-service failures are designed to fail open; already installed deny rules can remain effective.
Can payment callbacks and integrations keep working?
Scoped exceptions let TraBotPro account for payment providers, monitoring, and integrations. These are reviewed during onboarding and monitoring before enforcement is enabled.
Do I need access to the management console?
No. TraBotPro operates the console and manages site policies. Customers install an edge on their Hypernode with guided onboarding.
How do browser challenges work?
TraBotPro adapts verification to the visitor and route: invisible browser checks, proof-of-work, and interactive challenges. Human interaction signals and clearance tokens help legitimate visitors continue, while machine integrations use dedicated policies instead of browser puzzles.
Your traffic deserves
a smarter gatekeeper.
Start with your setup. Build a rollout brief for your TraBotPro contact.