stylobot
Bot defense for teams that need control and evidence across the fleet
Run detection where your traffic already lives. Tune policy by path, push changes without redeploying, and keep the full signal trace behind every challenge, throttle, or block.
Start with the open-source core. Add the commercial control plane when you need shared operations, live configuration, and managed rollout across multiple gateways.
runs in your VPC, your data stays there
signals, deltas, action, policy
layered protocol + behavior signals
HMACed IDs + stripped UAs
Enterprise operating model
The commercial layer is for teams running StyloBot as an operational control surface, not just a library.
Live policy editing
Change thresholds, actions, and detector overrides without shipping a new build. Tighten `/api/login`, relax `/docs`, and stage changes before wider rollout.
Fleet visibility
Register gateways, track heartbeat and telemetry, and see which instances are enforcing which configuration. This is built for multi-node operation, not one-off tuning.
Decision evidence
Keep raw and derived signals, detector-level reasons, confidence shifts, aggregation output, and action mapping attached to each decision. Security teams can review what happened instead of accepting a black-box verdict.
Private deployment
Run the control plane and supporting services inside your own environment. Traffic inspection stays close to the application and does not require a third-party SaaS hop.
Postgres and Redis backing services
Move from in-memory MVP components to shared persistence and coordination when you need durable overrides, reporting, and cluster-aware behavior.
Support for real operators
Get help on rollout, tuning, and incident response from people working on the detection stack itself. The goal is faster decisions under pressure, not generic customer success.
Compliance & data governance
Compliance packs supporting GDPR, CCPA/CPRA, CNIL, PCI-DSS, and SOC2 configure retention, anonymization, and audit logging to support your compliance program. Active compliance guardians re-verify posture on a schedule instead of trusting it once at config time. Full DSAR workflow handles subject access export, cascading deletion, and audit trail. Operator override feedback loop uses LLM root cause analysis to explain why a signature was reclassified.
Where enterprise actually matters
These are the environments where shared policy, evidence retention, and coordinated rollout stop being optional.
High-risk login and account flows
Credential stuffing, account takeover, and API token abuse need stricter actions than brochure pages or docs traffic. Enterprise controls let teams express that difference cleanly.
Multi-gateway deployments
Once protection runs across several gateways or regions, config drift becomes a security problem. Central policy and fleet reporting solve that directly.
Teams that need reviewable outcomes
Fraud, platform, and security teams need a record of what the system saw and why it acted. Enterprise StyloBot keeps that chain of reasoning available.
Run StyloBot like an operating system, not a toggle
Tell me about your traffic, how you want to enforce, and where you deploy. I will keep the discussion technical.
Email me directly
Tell me about your traffic, protected paths, and deployment model. Expect a technical response, not a drip campaign.
scott@stylobot.netTypical first response in 24h.