Choose your StyloBot setup

StyloBot sits between the internet and your application. Pick the route that matches what you already have; all three preserve your app and start in observe-only mode.

flowchart LR
    A[Your visitors] --> B{How should traffic arrive?}
    B -->|Existing Compose stack| C[Add the gateway service]
    B -->|Public VPS ports 80 + 443| D[Caddy + Let's Encrypt]
    B -->|No inbound ports| E[Cloudflare Tunnel]
    C --> F[StyloBot]
    D --> F
    E --> F
    F --> G[Your existing app]

The safe rollout

Every quickstart follows the same sequence:

1. Put StyloBot on the public request path.
2. Run in observe-only mode and verify normal visitor traffic in the dashboard.
3. Start with a low-blast-radius policy such as throttling obvious automation.
4. Tighten protection only for the routes where a false positive is inexpensive.

Your application does not need to change. The one rule is important: do not leave an alternate public route around the gateway, or bots can bypass detection.

What you get on day one

• A live view of visitors, likely bots, and the signals behind each decision.
• Header, behaviour, and request-sequence detection in front of any HTTP app.
• A reversible rollout: observe first, then choose throttle, challenge, or block.
• A path to the commercial control plane when you need shared policies and fleet visibility across more than one site.

Already know your topology? Pick a guide above. If something does not behave as expected, troubleshooting covers the common failure modes.