One platform, two ways to own it. Buy online, deploy it on your own Linux servers, and keep your findings database on infrastructure you control.
Monthly
Full platform, billed monthly. Cancel anytime.
- All 28 modules & 8-phase automation
- AI validation & remediation (bring your own AI key)
- Unlimited scans, no per-asset fees
- Self-service deployment, your infrastructure
- Email support
- Cancel anytime
Lifetime
Own it forever. One payment, perpetual license.
- Everything in Monthly
- Perpetual license, no recurring fees
- 1 year of updates & engine feed included
- Priority support
- Pays for itself in 10 months
All prices in USD. Secure checkout by Stripe.
What you gain, and how you stay protected.
Every line below describes what the shipped software does today, checked against its code. No roadmap promises.
What you gain
What your team gets once SITEY is running.
One findings list for 16 scanners
Import results from Nessus, Qualys, OpenVAS, Burp Suite, Nuclei and 11 more into one list sorted by severity. SITEY also starts Nessus and OpenVAS scans on your own scanner servers.
Fixes written for each host
For Windows and Linux hosts running the SITEY agent, the engine prepares the fix from that host's OS, installed software and diagnosis. The agent runs it after the approvals your policy requires.
Closure you can check
An engine fix closes the finding only after a follow-up check confirms it: fresh host inventory, a scanner re-test or a screened check script. The closing note records who approved, the method and the result.
Evidence before any false-positive call
Suspected false positives are checked on the host, and at default settings a person makes the final call.
Fewer AI calls over time
Scripts that ran successfully are saved and reused on closely matching findings on the same OS family, instead of paying for a new AI call.
One screen for the whole engine
The autonomy dashboard shows active and closed workflows, approvals waiting, verified closures, success rate and a filterable activity log, plus the network view of the engine's parts.
Reports and approved patch jobs
Export findings as PDF, Excel or Word. Fix jobs you send to hosts wait for admin approval and for the maintenance window you set.
A license without meters
The license sets an expiry date, an IP limit and an agent limit. It does not count scans and does not switch modules on or off.
How you stay protected
Built in and on by default, with switches you control.
Your approval comes first
Dashboard policies start at Gate 1 for critical and high findings: the engine diagnoses, prepares a fix and waits for an admin to approve it. With no matching policy it starts no work.
Destructive commands are refused
Diagnostic scripts must pass a read-only check before they are sent, and the agent refuses scripts that match its blocklist, such as disk formatting or download-and-run code.
Automatic changes stay small
Before the engine approves a fix on its own, it checks the kill switch, the change pause, a per-host backlog breaker and a cap of 5 active automatic changes per policy. In full auto, only your canary or rollout-wave hosts change without approval.
One switch halts new work
The kill switch halts new engine work. A change pause, fleet-wide or per agent group, blocks automatic changes while diagnosis continues.
Nothing is left hanging
Checks time out after 15 minutes and fixes after 30 by default, with the reason recorded. Work for an offline host waits for its next check-in, and a fix that times out goes to your team.
A person takes over, with the reason
When the engine hands a finding back, it cancels its pending fix, keeps the finding open, records what it saw and why, and does not restart work on it by itself.
Agents and accounts locked down
Each agent authenticates with its own secret, stored as a salted hash, and sees only its own jobs. Stored AI keys and mail passwords are encrypted, and five failed sign-ins in 15 minutes block further tries from that address.
Your servers, a short outbound list
SITEY and its PostgreSQL database run on your Linux servers. It calls siteyvm.com for license checks and your AI endpoint, which receives finding and host details to analyze. If siteyvm.com is unreachable, SITEY keeps working for up to 14 days after its last successful check.