- Company sizes or stages where this product is overkill or insufficient
- Very small teams without infrastructure engineering capacity may be better served by hosted APIs with published pricing and minimal operational burden.
- Industries or use cases where competitors are clearly more appropriate
- Highly regulated industries (healthcare, finance, government) that require documented certifications and detailed security documentation prior to procurement.
- Technical requirements that this product cannot meet (based on public information)
- Workloads that require contractually guaranteed enterprise controls (SAML/SCIM/audit logs/data residency) if those controls cannot be documented or provided by the vendor.
- Budget constraints that make alternatives more appropriate
- Buyers that cannot accept pricing opacity or potential enterprise minimums may prefer providers with published pricing or pure open-source options.
- Specific workflows or integrations where the product may fall short
- Buyers needing a validated ecosystem of marketplace integrations for observability, IAM, and governance should evaluate maturity and documented integrations of alternatives.
- Red flags in the buying process
- If pricing, SLAs, data retention, training on customer data, and security attestations are not clearly documented or contractually available, procurement risk may outweigh potential performance benefits.
- Current limitations acknowledged in public materials
- Public materials reviewed did not include a detailed public list of limitations or a dated roadmap with commitments.
- Features on the roadmap (not yet available)
- The vendor indicates ongoing investment in SGLang and Miles and plans for managed infrastructure and tooling, but public roadmaps with timelines were not available in the sources reviewed.
- Scale limitations (at what volume/size does it break down?)
- No public, quantified scale limitations were located in the materials reviewed.
- Security or compliance gaps
- No public SOC 2 / ISO 27001 / ISO 27017/27018 documentation was located in the sources reviewed; buyers should request security and compliance documentation directly.
- Technical debt or architectural limitations mentioned in community discussions
- Community discussions reference practical constraints such as VRAM limits for certain multimodal configurations; these are common concerns across inference engines and often depend on workload and environment.
- API limitations or integration constraints
- Public documentation reviewed did not provide comprehensive API limits, quotas, SLAs, or detailed data retention policies beyond general Terms and Privacy statements.