Direct answers on deployment options, air-gapped installations, verification gates, and editions. Have a specific question? Contact us.
Yes. The On-Prem edition runs entirely inside your network perimeter with no outbound connectivity required to operate the pipeline. Repositories are cloned, redacted, and analysed on infrastructure you control.
Model inference can point to a local GPU host (such as Ollama), an enterprise endpoint under your own contract, or a host-side CLI subscription agent. Provider credentials stay outside scan containers, and Stage 0 strips secrets and PII before prompts are built. See Security & Trust for full boundary details.
Yes. The On-Prem edition is built to operate disconnected from the public internet, with no phone-home telemetry or third-party network calls. Every stage of the pipeline (redaction, mapping, discovery, validation, and reporting) executes inside your perimeter.
Yes. Single-tenant On-Prem clones directly from internal Git hosts (GitHub Enterprise, self-hosted GitLab, Bitbucket Data Center, or internal mirrors), runs Stage 0 secret redaction locally, and stores all evidence artifacts, signed gate ledgers, and reports on your own storage.
Yes. Because secret redaction runs deterministically before analysis and inference can target local offline weights, the On-Prem edition supports deployments with no network path out of your enclave. Contact our architecture team to scope specific accreditation and landing-zone requirements.
Yes, for Enterprise and Private Plus engagements. Get in touch to discuss your location and requirements.
An engineer responds the same working day to confirm your repository setup, identity provider, and deployment preference. From there, we either provision an isolated cloud workspace or scope a private deployment, and run a scan against a repository you select.
Questor is available in three deployment models: Questor Cloud (SaaS) with isolated tenant workspaces, Private Cloud running single-tenant inside your own Azure or Kubernetes subscription, and On-Premises running fully inside your own data centre or air-gapped network. See Pricing for edition details.
Rule-based scanners flag pattern matches without proving whether untrusted input can actually reach a sensitive sink across files and services. Questor requires every candidate finding to pass eight signed checks across Gates A–H, including source-to-sink tracing, static exploitability verification, and negative controls. Candidates that fail negative controls are recorded as Disproven rather than left for manual triage. See Evidence for details.
A Disproven case is a candidate finding that Gate D or Gate F ruled out because an upstream sanitizer, parameterized query, or authorization check prevents exploitation. Questor displays disproven findings in the Defender portal so AppSec teams have a complete audit record of what was tested and dismissed, without cluttering developer queues.
Questor operates strictly read-only and never modifies your repositories or generates unreviewed code patches. Instead, it opens a governed Case in the Case Registry (with optional Jira and GitHub SARIF sync) containing the exact source-to-sink file-and-line trace, static exploitability check, and calibrated impact so your engineers can fix the root cause. When a fix is merged, Stage ∞ re-scans the repository and closes the case automatically.
Questor offers Verify, Team, Business, and Enterprise / Private editions. Every edition runs the same six-stage verification pipeline and produces Ed25519-signed case records; higher tiers add multi-repository limits, OIDC SSO, executive compliance packs, and private deployment options. See Pricing for the full comparison matrix.
Yes. The Verify plan ($49/mo) scans public repositories with full Ed25519-signed case records, or you can schedule a live demo where we scan a repository of your choice together.
Share your deployment constraints, compliance framework, or repository setup and our team will respond the same working day.