// platform
How HackEx works_
A scan is a snapshot. HackEx is the loop that runs it continuously: watch, detect, explain, contain, fix, then verify. One engine, around the clock.
// always_watching
ALWAYS WATCHING
Your projects get re-checked on a schedule you choose: hourly, daily or weekly. Anything new that shows up opens an incident; anything you fixed closes itself. The changes come to you.
hourly · daily · weekly// server_agent
SERVER AGENT
One command installs it. It quietly reads your server's own logs for break-in attempts, sends us only the summary, never the logs themselves, and can carry out fixes you approve.
your data stays on your box// github_app
GITHUB APP
One click connects your repositories. Every push and pull request gets checked, and results land as a comment right on the commit, before bad code merges.
checks on every push// drift_detection
DRIFT DETECTION
HackEx remembers what normal looked like. When something changes (a new open port, a file that suddenly went public) you hear about it immediately, not at the next quarterly review.
knows what changed, and when// incident_inbox
INCIDENT INBOX
Everything that matters lands in one inbox with severity, history and notes. Your team acknowledges, assigns and resolves, with a full record kept automatically.
ack → resolve → audit// escalation
ESCALATION
Small stuff waits for a digest. Big stuff pings Slack, Telegram or WhatsApp instantly. Criticals page everyone: email and PagerDuty included. You set the rules once, in settings.
slack · telegram · whatsapp · email · pagerduty// threat_intel
THREAT INTEL
HackEx cross-checks what it finds against CISA's catalog of vulnerabilities being exploited right now. If your stack matches, it jumps to critical immediately.
cisa kev · live feed// ai_code_fixes
AI CODE FIXES
Deterministic patches for known patterns, AI-generated diffs for everything else: verified to apply cleanly, linted, and opened as a pull request. You merge it, or grant deploy permission and HackEx merges the PR and pulls the fix onto your server.
verified diffs · optional auto-deploy// hex_assistant
HEX ASSISTANT
Your security co-pilot lives inside the dashboard. Ask HEX anything by text or voice: it reads your real scans, incidents and credits, explains what matters, navigates you to the right page and can even kick off a scan.
talk or type · knows your data// voice_core
VOICE CORE
Every incident ships with a briefing you can listen to and a core you can talk to. Say "acknowledge" or "resolve" and it acts. The orb pulses while it speaks, and glows hotter as severity climbs.
briefing + spoken commands// learns_your_system
LEARNS YOUR SYSTEM
Your project's own history is part of the evidence. Repeat offenders get longer blocks, recurring incidents weigh heavier, and the decision engine scores every action against what it has already seen.
memory, not just rules// fire_drills
FIRE DRILLS
Launch a simulated attack against your own pipeline whenever you like. Watch detection, escalation and containment fire end to end, safely, before a real attack ever tests them.
practice before it counts