- When you need enterprise security assurances now
- If your organization requires SOC 2 Type II reports, DPAs, SSO/SAML/SCIM, audit logs, or explicit data residency options, these controls are not publicly documented and should be validated before purchase.
- When you already have a stable LaTeX production pipeline
- Teams that are LaTeX-fluent and require guaranteed compilation fidelity and package support may find established LaTeX tooling (Overleaf or local workflows) to be lower risk.
- When you need an integrated compute environment
- If reproducible computation, package management, and notebook-style collaboration are primary needs, a platform that integrates those features (e.g., CoCalc) may be more appropriate.
- When budget predictability is mandatory
- Public pricing information was not found; lack of published pricing can be a procurement blocker.
- Current limitations acknowledged by the vendor
- The vendor has signaled that the product is early-stage and some features may be incomplete or unstable.
- Roadmap signals
- Public updates indicate rapid iteration (for example, features for inline computation and improved matrix entry). These are indications of planned work rather than contractual commitments.
- Scale limitations
- Not publicly documented; no enterprise-scale adoption metrics were available in the reviewed sources.
- Security or compliance gaps
- Security certifications and enterprise controls are not publicly documented.
- The privacy policy page could not be fully accessed in the research environment, which is a practical diligence gap.
- API limitations / integration constraints
- Not publicly documented in available sources.