Skip to content
SECURITY WORKSPACE / DDoSly

Infrastructure security, without blind spots.

Explore the monitoring, investigation and controlled-response workflows DDoSly is being engineered to support on cPanel/WHM hosts.

SPECIFIC CAPABILITIES DEPEND ON THE VERIFIED PRODUCT RELEASE
PRODUCT CAPABILITIES

One platform. Distinct operational jobs.

Monitoring, change control and deployment readiness are different tasks. Each deserves its own interface.

01 / OPERATIONAL VISIBILITY

Investigate the signal before acting on it.

Review observed connections, originating sources, time windows and known policy context. The console concept distinguishes evidence from decisions.

Illustrative connection activity · not real measurements

Firewall review

Make rule intent and backend outcome visible as separate states.

Policy context

Understand when a threshold matches—and when no action is permitted.

Host-first integration

Designed around Linux hosting environments with a cPanel/WHM administrative workflow. Confirm compatibility per release before enabling enforcement.

Explore compatibility →
AVAILABILITY & SCOPE

Product capabilities versus roadmap

Capability labels are intentionally conservative.

01 / PRESENT IN PRODUCT DIRECTION

Host monitoring

Local observations and server diagnostics are central to the plugin design; exact deployed behavior must be verified.

02 / VALIDATION REQUIRED

Controlled firewall actions

Backend support, command results and rollback behavior must be checked against the installed release.

03 / FUTURE WORKSPACE

Central fleet visibility

A multi-server cloud console is a roadmap concept, not an available live service.

04 / FUTURE INTEGRATIONS

Notifications and alerts

Alert delivery requires configured and tested channels, delivery tracking and permissions.

EXPLORE NEXT

From capability to deployment.