Frequently asked questions

Quantum as a Service: quantum-powered AI that cuts your AI processing costs, explains every decision in plain English, and protects your data against future threats — all delivered as a service, inside your own systems.

Yes and no. You can apply quantum principles through our Quantum API, run your quantum infrastructure on a PaaS tenancy, or stand up your own quantum hub — all options are available.

90 days, inside the client's own infrastructure. That is our standard deployment, everywhere.

Nowhere. Everything runs inside your own cloud, on-premise, or air-gapped systems. Your data never leaves your building.

Fixed-scope engagements tied to a measurable outcome inside one quarter — money saved, risk reduced, or speed gained.

It is not for anyone who just wants a chatbot. We build for organisations where decisions carry regulatory, financial, or safety weight — banks, hospitals, defence, government.

Interface and documentation in English, Hindi, Arabic, German, Japanese and Mandarin, with full Indian-language coverage. Engineered to the client's regulatory framework — India (DPDPA, RBI, SEBI, IRDAI, CERT-In), Gulf (PDPL, NESA, SAMA, ADGM/DIFC), EU (GDPR, DORA, EU AI Act), Japan (APPI, FSA), China-facing (PIPL, MLPS 2.0), Australia (Privacy Act, APRA CPS 234/230), and US (HIPAA, SOC 2, NIST CSF).

JAQL's layer that sits on top of your existing AI, analytics or workflow stack and adds the human-decision context the underlying model can't see — operator cognitive load, stress signals, attention state, policy constraints and explainability.

Protecting data, identities and infrastructure against threats that exploit quantum computing. Migrating to NIST PQC standards (ML-KEM, ML-DSA, SLH-DSA), adopting crypto-agility, and protecting long-lived secrets against harvest-now-decrypt-later attacks.

An adversary intercepts and stores encrypted traffic today knowing they can't break it yet, then decrypts it later once a sufficiently capable quantum computer exists. The defence is to move to post-quantum cryptography now.

Classical AI brute-forces patterns by scaling compute. Quantum-inspired AI uses superposition- and entanglement-style mathematics to explore many candidates in parallel — up to 70% lower token and inference cost in production.

Protects the human side of the security stack — analyst attention, decision quality under load, susceptibility to social engineering and AI-generated deception — combining cognitive-load monitoring, provenance and grounding against Mythos-class attacks, human-in-the-loop gates and red-teaming.

Every credit, fraud, AML, KYC or suitability decision ships with the features used, their weights, a confidence band, the policy rules triggered and a counter-factual. Required under RBI, SEBI, IRDAI, EU AI Act, GDPR Article 22, BaFin and SAMA guidance.

Model inventory, risk-tiering, approval gates, monitoring for drift and bias, incident response, and regulator-ready audit trails. Aligned to NIST AI RMF, ISO/IEC 42001, the EU AI Act and sector regulators (RBI, SEBI, SAMA, MAS, APRA, FCA).

Publish before we sell (citable SSRN preprints), no offensive quantum tooling, crypto-agility first, energy honesty on compute footprint, and dual-use review on every defence or government engagement.

A family of cryptographic algorithms (ML-KEM, ML-DSA, SLH-DSA standardised by NIST in 2024) designed to resist attack by both classical and quantum computers, replacing RSA, ECDSA, ECDH and DH.

HNDL is already happening. NIST mandates deprecation of RSA/ECC by 2030 and disallowance by 2035. RBI and SEBI are aligning. A 5-phase migration takes 24–36 months for a typical BFSI estate.

Phase 1 Cryptographic Inventory; Phase 2 Risk & HNDL Threat Model; Phase 3 Crypto-Agility & HSM Upgrade; Phase 4 Hybrid TLS / Application Migration; Phase 5 Full PQC & Continuous Assurance.

A structured 90–180 day engagement — from cryptographic inventory to regulated production. Booked via a 30-minute intro call with the JAQL founders.

ML-KEM (FIPS 203) for key establishment, ML-DSA (FIPS 204) for signatures, and SLH-DSA (FIPS 205) for hash-based signatures, in hybrid mode with classical algorithms during the transition.