Skip to main content
Scanning in every SCANOSS cloud service runs inside the customer environment. Only file fingerprints (cryptographic hashes) and metadata go to the SCANOSS knowledge base for matching. SCANOSS never receives or stores proprietary source code. SCANOSS designs its cloud services to meet SOC 2 Type II, ISO/IEC 27001 (ISMS), and GDPR requirements for security, availability, and confidentiality.

Dedicated SaaS deployment

A Dedicated SaaS deployment is a private SCANOSS cloud environment that SCANOSS hosts and manages. It runs on infrastructure provisioned for a single customer, so no other organisation shares its compute resources or API capacity. You get a fully managed cloud service with stronger isolation and predictable performance. A Dedicated SaaS deployment has:
  • A single-tenant environment. Infrastructure and service capacity are reserved for one organisation.
  • Dedicated throughput, with no resource contention from other tenants.
  • High availability. Deployments include redundant infrastructure and failover to keep the service running.
  • Managed infrastructure. SCANOSS handles maintenance, updates, monitoring, and scaling.
  • Hosting in European data centres.
  • Access through dedicated API credentials.
  • Privacy-preserving scanning. Only fingerprints and metadata go to the SCANOSS knowledge base, and source code stays in the customer environment.
This model suits organisations that need more isolation, predictable performance, and dedicated capacity in a fully managed cloud service.

Shared SaaS deployment

The Shared SaaS deployment gives access to SCANOSS through a multi-tenant cloud environment that SCANOSS manages. Several organisations use the same service infrastructure, and each one accesses it with its own API keys. You can add SCANOSS to your workflows at lower cost, without deploying or operating infrastructure. A Shared SaaS deployment has:
  • A multi-tenant environment. Several organisations share the same cloud service infrastructure.
  • API-based access. Each customer uses its own API keys.
  • Shared throughput. Tenants share a common pool of system resources.
  • High availability. Redundant systems and failover keep the service running if a component fails.
  • A fully managed service. SCANOSS manages infrastructure, updates, scaling, and monitoring.
  • Hosting in European data centres.
  • Privacy-preserving scanning. Only fingerprints and metadata go to SCANOSS for matching, and source code stays in the customer environment.
This model suits organisations that want a lower-cost, fast way to add SCANOSS to their development or security workflows.