- Company sizes or stages where this product is overkill or insufficient
- Very early-stage startups without dedicated computational chemistry capability may prefer established classical workflows before investing in quantum experimentation.
- Industries or use cases where alternative platforms are more suitable
- Non-chemistry quantum applications (optimization, QML) may be better served by broader platforms (Qiskit, Cirq, Zapata) rather than a chemistry-focused tool.
- Technical requirements that this product may not meet
- If an organization requires proven support for a specific in-house quantum device or strict on-premises-only execution, a dedicated enterprise arrangement will likely be necessary; alternative vendors with established on-prem options may be preferable.
- Budget constraints
- If €30k/year plus hardware runtime costs are not feasible, open-source toolchains and academic collaborations may be more appropriate.
- Specific workflows or integrations where caution is advised
- If a workflow relies on deep integration with an existing computational chemistry suite (e.g., Schrödinger, OpenEye, or internal pipelines), interoperability should be validated; public documentation focuses more on Qrunch’s SDK and quantum backends than on integrations with mainstream drug-discovery suites.
- Procurement red flags
- If procurement requires documentation of certifications, penetration tests, or detailed security whitepapers and the vendor cannot provide them, this should be treated as a potential concern.
- Current limitations acknowledged by the vendor
- Quantum hardware access is billed separately and is subject to limitations of NISQ devices (noise, limited qubit counts, queue times), as noted in partner content.
- Features on the roadmap (not yet available)
- Roadmap details were not found in public sources reviewed.
- Scale limitations (at what volume/size does it break down?)
- Public benchmarking on scale was not found.
- The Basic tier limits runs to up to 35 qubits; Pro advertises unlimited qubits in licensing terms but practical limits depend on available backends and cost considerations.
- Security or compliance gaps
- No public SOC 2 or ISO certification claims were found; procurement teams should request formal documentation if these controls are required.
- Technical debt or architectural limitations mentioned in reviews
- Not found due to lack of a credible, attributable review corpus.
- API limitations or integration constraints
- Qrunch is Python-API oriented; the breadth of enterprise integrations is not clear from public documentation.