Enterprise-grade security and regulatory compliance for quantum computing optimization
Built with security and compliance at the core
Your jobs run on your own IBM/AWS/Rigetti accounts. QuantFenix only orchestrates. We never store your raw input data.
When eu_only is enabled, our control plane and database are hosted in the EU.
We keep only execution metadata needed for auditability and reproducibility (hashes, timestamps, backend/version, cost estimates vs. actuals). No raw inputs.
Standard Data Processing Addendum and Standard Contractual Clauses available. QuantFenix acts as a processor with minimized data exposure.
Schema checks block uploads that contain PII columns according to your policy.
Secrets managed by KMS with least-privilege access and scheduled rotation.
IP/org/country deny-lists enforced; customer attestation at onboarding.
Every run produces a PDF/Markdown report and a run manifest.
QuantFenix routes jobs using a multi-objective policy balancing quality, cost, and latency, with budget-capped exploration. Canary runs monitor drift. The exact heuristics are proprietary; you get clear budgets, envelopes, and auditable results.
Our goal is that most runs complete within the per‑run budget you set.
PDF/Markdown report and reproducible run manifest for every execution.
Storage pinned to the EU when eu_only is active.
We do not store raw inputs; only minimal metadata.
You start a run via CLI/SDK (local file, S3 URL, or in-memory DataFrame).
QuantFenix scores eligible backends, performs a dry-run, applies your budget guards.
The job executes on your accounts. QuantFenix receives only result telemetry.
We generate the audit report and update policy hints if outcomes change materially.
Common questions about our security and compliance approach
No. We orchestrate compute on your credentials and store only execution metadata for auditability.
Yes—when it makes sense for your objective and budget. Otherwise we use strong classical baselines.
Yes. Enable compliance.data_residency: eu_only.
We use quality/cost/latency-aware routing with limited exploration and canaries under strict budget caps. Details are proprietary; outputs are fully auditable.