SITEY is self-service. You buy it online, download the installer, and deploy it inside your own infrastructure. There is no sales call, no onboarding consultant, and nobody from our side touching your network. This page is the whole path, from checkout to your first closed vulnerability. Getting started takes roughly an hour of hands-on work, and most of that hour is spent waiting for the first discovery scan to finish.
Step 1: Choose a plan
Two options, both on the pricing page:
- Monthly, $599/month. Recurring, cancel anytime. Includes the full platform: all 23 modules, all 17 scanner integrations, all 8 automation phases.
- Lifetime, $5,999 one time. Perpetual license, plus one year of updates and engine feed, plus priority support. That is ten months of the monthly plan, so it pays for itself in month eleven.
Prices are in USD. Checkout is handled by Stripe; we never see your card details. Nothing is metered by asset count, user count, or scan volume.
Step 2: Your account is created at checkout
An account is created automatically when payment clears, using the email you enter at checkout. You need it: the license key, the installer downloads, the agent packages, and the engine feed bundles all live behind it. Use a mailbox that outlives one person, such as a security team alias, rather than a personal address.
Step 3: Download the installer
Sign in and open your account area. You will find the installer bundle for Linux, its SHA-256 checksum, your license key, and the agent packages for Linux and Windows. Verify the checksum before you run anything. The bundle is self-contained: it ships the platform, the scanner integrations, and the offline remediation knowledge base, because we assume your production server may have no general internet access at all.
Step 4: Check system requirements
SITEY runs on one Linux server that you own and control. Minimums below are real minimums, not marketing numbers.
| Component | Minimum | Recommended |
|---|---|---|
| Operating system | 64-bit Linux (Ubuntu 22.04/24.04 LTS, Debian 12, RHEL or Rocky 9) | Ubuntu 24.04 LTS |
| CPU | 4 cores | 8+ cores |
| Memory | 8 GB RAM | 16 GB RAM |
| Disk | 100 GB SSD | 250 GB+ SSD |
| Database | PostgreSQL 14+ (installed by the bundle, or point it at your own) | Your own managed PostgreSQL with backups |
| Outbound network | HTTPS (443) to siteyvm.com for license activation and engine feed only | Through your existing egress proxy |
| Inbound network | From your agents and your analysts’ browsers | Behind your VPN or internal load balancer |
| Privileges | root or sudo on the install host | Dedicated host, not shared with other workloads |
The minimum comfortably handles a few hundred assets. Past roughly 2,000 assets, add cores and memory before you add scanners, since AI validation and dedup are the heavy parts of the pipeline, not the scanning itself.
Step 5: Run the installer
Unpack the bundle and run the installer as root. It checks dependencies, installs or connects to PostgreSQL, creates a dedicated service user, generates a self-signed TLS certificate (or takes yours), writes a systemd unit, and starts the service. When it finishes, open the server in a browser and create the first administrator account. That account is yours; we have no ability to create, reset, or use accounts on your instance.
Step 6: Activate the license
Paste the license key from your account area into the activation screen. The server makes a single outbound HTTPS call to siteyvm.com and binds the license to that installation. That call carries the license key and an installation fingerprint. It does not carry asset names, scan results, or vulnerability data. If the host has no direct egress, point it at your outbound proxy. If activation is blocked by policy, email us at info@siteyvm.com before you start troubleshooting firewalls.
Step 7: Deploy agents to your hosts
Agent packages for Linux and Windows are in your account area and are also served by your own SITEY server. Generate an enrollment token in the Assets & Agents module and push the package with whatever you already use: Ansible, Group Policy, Intune, SCCM, or a shell loop. Agents connect outbound to your server, never to ours. If you cannot install anything on a host, cover it with credentialed network scanning instead; agentless targets work, they just produce less depth.
Step 8: Run the first discovery scan
Define a scope by CIDR range, hostname list, cloud tag, or agent group, then select scanners. SITEY orchestrates 17 of them, including Nessus, OpenVAS, Nmap, Nuclei, ZAP, Trivy, MobSF, Acunetix, SonarQube, and Semgrep. Phase 1 (Discovery & Scanning) and Phase 2 (Collection & Dedup) run automatically. Expect the raw output to be noisy and duplicated across scanners. That is normal, and it is exactly what the next phases exist to fix.
Step 9: Review findings, then enable automation
Look at the first results yourself before handing anything to the engine. Then turn on the remaining phases one at a time: AI Validation & Triage, Risk Scoring, Smart Assignment, AI Remediation Plan, Automated Patching, and Retest & Closure. Keep Automated Patching behind manual approval until you have watched it propose fixes for a few cycles and agree with them. Our 72-hour target for closing critical findings assumes the first six phases are enabled and that patch windows are pre-approved; it is not magic, it is the removal of the queue time between “found” and “assigned”.
Where your data lives
On your server. Asset inventory, scan output, vulnerabilities, remediation plans, task assignments, reports, and audit logs all sit in your PostgreSQL database, on hardware you control. There is no tenant of yours on our side and no copy of your findings anywhere else. Backups are yours to take and yours to restore. Compliance mapping to ISO 27001, PCI DSS, SOC 2, GDPR, KVKK, and BDDK is computed locally against your own data, and the evidence never leaves the box.
What talks to us
Two things, both outbound HTTPS to siteyvm.com. First, license activation and periodic license validation. Second, the engine feed: vulnerability definitions, scanner plugin updates, and updates to the remediation knowledge base. Neither carries your scan data. If your environment is air-gapped, download the feed bundle from your account area on a connected machine and import it into the platform by hand.
Getting help
Email info@siteyvm.com with your license ID and a diagnostic bundle exported from the platform; that pair answers most questions in one round trip. Lifetime licenses go into the priority queue. Product documentation is installed with the platform, so it works even when the server has no internet access. For anything pre-purchase, use the contact page or read the feature breakdown first.
Frequently asked questions
Do I have to give you access to my network?
No. You install the platform, you deploy the agents, you hold the admin credentials. We have no inbound path into your environment and no remote support tooling that reaches it.
What happens if I cancel the monthly plan?
The platform keeps running to the end of the period you paid for. After that the license deactivates and the engine feed stops. Your database and everything in it stay on your server; you can export before or after.
Do I need my own Nessus or Acunetix licenses?
For commercial scanners, yes. SITEY orchestrates them using credentials you already own. The open-source engines, including OpenVAS, Nmap, Nuclei, ZAP, Trivy, Semgrep, and MobSF, ship configured and need no extra licensing.
How long does installation actually take?
Budget 30 to 45 minutes for the server, from unpacking the bundle to a working login. Agent rollout depends entirely on your fleet size and your existing deployment tooling.
Can I install it on more than one server?
A license activates one production deployment. If you need a separate staging or lab instance, email info@siteyvm.com and we will sort it out; we do not charge twice for the same team testing an upgrade.