- Company sizes or stages where this product is overkill or insufficient
- Very small businesses with minimal phishing exposure and no SOC function may find the solution's cost and operational model disproportionate to needs.
- Industries or use cases where competitors are clearly superior
- Highly regulated sectors that require extensive, publicly documented compliance attestations, long-term archiving, and continuity features may prefer incumbent SEG vendors with established certifications and references.
- Technical requirements that this product cannot meet
- If an organization requires MX-based gateway enforcement only (no API-based post-delivery evaluation), or needs support for non-Microsoft/Google email platforms, this product may not meet technical requirements.
- Budget constraints that make alternatives more appropriate
- Organizations already licensed for Microsoft 365 E5 with Defender capabilities that meet their risk tolerance may find incremental ROI harder to justify without strong POC results.
- Specific workflows or integrations where the product falls short
- Integrated archiving, continuity, or eDiscovery features are areas where traditional SEG suites may provide more complete off-the-shelf solutions.
- Red flags in the buying process (e.g., requires annual commitment, no free trial)
- The vendor indicates many enterprise customers commit to 2–3 year terms; buyers who require month-to-month flexibility should negotiate terms or evaluate alternatives.
- Current limitations acknowledged by the vendor
- Public pages do not present a dedicated limitations section; this represents a documentation gap compared with more mature vendors.
- Features on the roadmap (not yet available) - note estimated dates if available
- No explicit public roadmap dates were found in the reviewed material.
- Scale limitations (at what volume/size does it break down?)
- Not publicly documented.
- Security or compliance gaps
- A public SOC 2 Type II report was not located, and ISO and pen-test documentation were not publicly available; these gaps should be addressed in procurement due diligence.
- Technical debt or architectural limitations mentioned in reviews
- No independent review data was available to assess historical technical debt.
- API limitations or integration constraints
- The product relies on Microsoft Graph and Google Workspace API integrations; organizations with strict constraints on Graph scopes or third-party access may encounter deployment friction.