- Requirement: enterprise-grade compliance
- If procurement requires SOC 2 Type II, SSO/SAML, SCIM, audit logging, and a vendor trust center, the vendor’s publicly documented posture (as found in this review) appears insufficient.
- Requirement: deep custom native functionality
- Reports indicate limitations in installing custom SDKs, libraries, or native modules; applications requiring niche device integrations should consider traditional development stacks such as React Native or Flutter, or platforms that explicitly support custom native modules.
- Requirement: predictable cost model
- If predictable spend is crucial, platforms with clearer per-message, per-token, or workload-unit predictability (or fully manual development) may offer lower financial risk than agentic, credit-metered systems.
- Requirement: mature DevOps workflows today
- GitHub sync is listed as "coming soon" in export documentation; development teams requiring integrated repo workflows and CI/CD may prefer platforms with established repo integrations.
- High dependence on third-party app store tooling via a builder
- Public reporting indicates App Store policy enforcement can affect third-party builders producing mobile apps; this adds platform-level risk outside the vendor’s direct control.
- Credit burn loops
- Multiple reviews describe scenarios where agent processes repeat attempts to fix issues until credits were exhausted.
- App Store ecosystem risk
- Reporting indicates Apple enforcement actions affected the vendor’s iOS app at times, which introduces platform distribution risk.
- Extensibility constraints
- Reviewers report limited ability to install arbitrary SDKs/libraries/native modules.
- Security/compliance opacity
- No public SOC 2 or ISO certification evidence was found in the reviewed materials.
- Roadmap signals
- GitHub sync and some developer workflow features are listed as forthcoming in documentation.