- Company sizes or stages where this product is overkill or insufficient
- Small teams conducting low-stakes assessments where manual review or simpler controls are adequate.
- Very large or highly regulated programs where early-stage maturity and a lack of publicly documented certifications are blockers.
- Industries or use cases where competitors are clearly superior
- Organizations requiring a full turnkey proctoring solution (identity verification + live proctors + recorded review + LMS-native workflows) where incumbent vendors provide established, documented solutions.
- Technical requirements that this product cannot meet (based on public information)
- Broad device coverage requirements (Chromebooks, Linux, tablets) are not clearly supported by the vendor's public materials.
- Programs that require persistent lockdown environments across many exam formats may be better served by established lockdown/proctoring suites.
- Budget constraints
- Lack of public pricing complicates budget planning; buyers that require published, predictable pricing may prefer alternatives that document costs publicly.
- Specific workflows or integrations where the product falls short
- If an exam platform requires deeply embedded, proven integrations with LMS/test engines, incumbent vendors may offer more mature documented compatibility and reference customers.
- Red flags in the buying process
- Claims presented without independently published methodologies or third-party validation should be evaluated with caution.
- Reliance on vendor demos rather than independent peer reviews is a procurement consideration.
- Current limitations acknowledged by the vendor
- The vendor describes the product as being in alpha, and the secure browser is stated to be in beta on public materials.
- Features on the roadmap
- The vendor lists a secure browser product on the roadmap, indicating movement toward application-layer enforcement in addition to network controls.
- Scale limitations
- No public benchmarks, uptime SLAs, or scale claims were identified in the materials reviewed.
- Security or compliance gaps
- No public SOC 2 or ISO documentation was found during this review.
- No public subprocessor list or data residency matrix was identified.
- API limitations or integration constraints
- No public API documentation or extensive integration documentation was found during this research.