- When mature, publicly documented enterprise compliance is mandatory
- If procurement requires publicly available SOC 2 Type II and/or ISO 27001 attestations, the vendor did not surface such certifications in public materials and may not meet a hard requirement without additional evidence provided under NDA.
- When dedicated inference capacity is required immediately
- Dedicated Inference was documented as not yet generally available; customers requiring guaranteed dedicated capacity today should consider vendors with GA dedicated deployments.
- When a large review footprint and proven deployments are required
- The vendor has limited presence on major review platforms and in published customer case studies, which increases procurement risk for highly risk-averse organizations.
- When proprietary frontier model access is a strict requirement
- Organizations that require specific closed-source/proprietary models should consider other providers or hybrid approaches.
- When very low usage and simplest costing are required
- Subscription-with-credits models may be less cost-efficient for sporadic, very low-volume usage than pure pay-per-use providers.
- Vendor-acknowledged limitations and early-stage behavior
- The vendor has publicly indicated the product was launched while still under active development and has addressed early operational incidents. This suggests that the platform has undergone rapid iteration and may present integration or stability considerations typical of early-stage infrastructure products.
- Historical downtime related to model fitting and GPU capacity has been described in vendor update posts.
- Roadmap items not yet available
- Dedicated Inference and some broader platform functionality are identified as not yet generally available.
- Scale limitations and SLAs
- No public capacity or throughput SLAs or comprehensive benchmark reports were located; buyers should request workload-specific performance data.
- Security and compliance gaps
- Publicly visible evidence of third-party certifications (SOC 2, ISO 27001) was not found; clarify contractual offerings and request relevant reports.
- Clarify the scope of marketing statements on retention versus contractual ToS retention windows.
- API compatibility limitations
- OpenAI-compatible claims should be validated for the specific features the buyer depends on (for example, tool/function calling, streaming modes, embeddings formats, and batching behavior).