How client separation actually works
We'll state this precisely, because it is the question that matters for a service provider: client separation is per-installation and architectural, not container-level. Each client gets its own licensed installation, deployed inside that client's own environment, scanning that client's own accounts with that client's own read-only credentials, writing findings and evidence to that client's own storage. Nothing is pooled: no shared tenant, no shared datastore, no scan data crossing a client boundary, and nothing flowing back to Nsasoft. Your operators work across installations the same way they work across client environments today.
What this is not: the product does not spawn an isolation container per scan, and there is no centralized multi-tenant console pooling client data — by design, because pooling client evidence in your infrastructure would recreate exactly the data-custody burden the architecture exists to avoid. The shipped GRC push connectors are likewise single-workspace and operator-configured — each client's connector pushes to that client's own compliance workspace, not to yours.
Why it fits a managed practice
The compliance line-item
One scan produces eight evidence packs — SOC 2, HIPAA, NIST CSF 2.0, PCI DSS, ISO 27001, CIS Controls v8, GDPR Article 32, and NIST SP 800-171 Rev 2 (evidence substrate for CMMC Level 2 preparation) — a deliverable your vCISO engagements can hand to a client's auditor.
No data custody you didn't ask for
Recommending most scanning stacks means routing client cloud data through your platform. Here, each installation writes to the client's storage — you operate the tool without inheriting a data-processing footprint for every client you serve.
Per-installation licensing that scales
Enterprise licensing is per installation with seat tiers, and the partner discount applies across your contracted installations. Adding a client is adding an installation, not renegotiating a platform.
A seat at the table
Quarterly Partner Council — a working roundtable on product direction, packaging, and what your client engagements need next. A joint case study when your first client installation completes onboarding.
Program structure
Volume discount
20–25% off the Enterprise tier for partners contracting five or more customer installations — rate confirmed per partner at onboarding.
Joint case study
Co-published when you bring your first customer installation through onboarding.
Quarterly Partner Council
Virtual roundtable: product feedback, pricing and packaging input, roadmap discussion.
Talk to us
Tell us about your practice
Write to partners@nsasoft.us with the details below.
- Firm name & website
- Managed clients — roughly how many, in which industries
- Clouds your clients run — AWS / Azure / GCP mix
- Compliance engagements you deliver — vCISO, audit-readiness, continuous compliance
- Installations you'd expect to contract in year one
Building a product rather than a practice? See OEM & Embedded Licensing. Product detail: NSAuditor AI Enterprise.