Self-hosted fits when
Your policy or your regulators expect sensitive data and findings to remain on infrastructure you control, or sources sit on networks with no route out.
Category comparison. Deployment.
Who runs the tool, where scan results are stored and what leaves your network, answered as a vendor questionnaire.
By Dipal Panchal, co-founder and CEO · Updated November 8, 2026
A self-hosted data security tool runs on infrastructure you control, on-premises or in your own cloud account. Its scanner, its database and its findings sit with your team. A SaaS (software as a service) tool runs in the vendor’s cloud. In NIST’s definition of SaaS, the customer doesn’t manage or control the underlying infrastructure, apart from limited application settings.
For a DSPM tool the choice matters twice: it reads your most sensitive data, and its findings are a map of where that data is. Decide where that map should live, then test the claim.
Explore deploymentCells describe the typical tool in each model; the NIST Cybersecurity Framework (CSF) row is our reading. Many tools mix the two, so ask where each part runs.
| Aspect | Self-hosted | SaaS |
|---|---|---|
| Acts on | Sources reachable from your network, including internal databases and file shares | Sources the service can reach: cloud services, or your network through a route you open |
| Main strength | Findings and credentials stay inside your infrastructure | No servers for your team to run, patch or back up |
| What it cannot do | Remove the operating work: hosting, backups, upgrades and capacity stay with you | Keep findings out of the vendor’s cloud, or run with no route to the vendor |
| Best fit | Policy or regulators expect sensitive data and findings to stay on infrastructure you control | Mostly cloud sources and a team that doesn’t want more infrastructure |
| A typical scenario | A bank scans databases on a network with no route to the internet | A software company scans its SaaS apps and cloud storage |
| Where it runs | On servers or cloud accounts you control | In the vendor’s cloud, shared with other customers or set apart |
| Who operates it | Your team: hosting, backups, upgrades and capacity | The vendor, under a contract and service levels |
| Updates | Installed when your team decides | Applied by the vendor, usually without action from you |
| Supplier risk (NIST CSF 2.0 GV.SC) | Covers the software and how its releases are built and delivered | Covers the service, where it runs, who operates it and its subprocessors |
Ten questions a security reviewer sends before approving a data security tool. The answers describe each model in general; get the vendor’s own in writing.
| Questionnaire item | Self-hosted | SaaS |
|---|---|---|
| 1. Where is data processed? | In your infrastructure | In the vendor’s cloud, in the regions it names |
| 2. Where are findings stored? | In a database you host | In the vendor’s cloud, under its retention rules |
| 3. Who can read findings? | Your staff, by your access rules | Your staff, plus any vendor staff the contract allows |
| 4. What leaves our network? | Only the outbound connections the tool makes | Depends on design: samples, metadata or only results |
| 5. Where are source credentials held? | Inside your infrastructure | By the service, or in your account, by design |
| 6. How is it updated? | You install releases on your schedule | The vendor applies updates |
| 7. Can it run with no internet route? | Where the tool allows it | No; it needs the vendor’s service |
| 8. Who are the subprocessors? | None run your scans; ask about licensing and support | Listed in the data processing agreement |
| 9. How is data deleted at exit? | You delete it from your own database | The contract sets a deletion period and proof |
| 10. How does the vendor access support cases? | Only if you grant access | Per the vendor’s support process; ask who and how it is logged |
Your policy or your regulators expect sensitive data and findings to remain on infrastructure you control, or sources sit on networks with no route out.
Your sources are mostly cloud services, your team doesn’t want to run more infrastructure, and the vendor’s processing terms pass your review.
A SaaS tool covers your cloud services, and a self-hosted tool covers databases and file shares that can’t be reached from outside.
Put the questionnaire to the vendor in writing, then check the answers on a running system.
IRIS is customer-hosted by default. Sylox-hosted environments are used only for demos and agreed pilots.
IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment.
IRIS runs on infrastructure you control. Findings, coverage records and evidence are stored in the IRIS database there.
The license service, once at activation and when an admin chooses to validate. A time source, which can be your own. SaaS services only during scans of those sources.
Releases arrive as verified bundles. IRIS pulls no updates at run time, so the release you approved is the one that runs.
Capabilities vary by edition.
Run IRIS in your own cloud account or data center, from a verified release bundle.
Each component, where it runs, what it reads and what it stores.
Our security program and how we handle data, stated plainly.
No. Self-hosting moves the work to your team: patching, backups, access and network rules. The safer choice is the one whose risks you can see and manage.
Where scanning happens, what leaves your network, what is stored and for how long, and who at the vendor can see findings. Ask for the data processing agreement and the subprocessor list.
Yes, with a way in. That is usually a component you host inside the network, or a network route you open for the vendor.
IRIS runs on infrastructure you control, on-premises or in your cloud account. Need Sylox to run it for you? Talk to us.
Yes. After a one-time license activation, IRIS can run in isolated and air-gapped networks for sources inside your network. Microsoft 365 and other SaaS sources need access to those services, and the host needs a time source, which can be your own.
Send the ten questions to your shortlist this week, then book a demo to plan hosting with a specialist.