- Company sizes or stages where this product is not appropriate
- Very early prototypes where the impact of zero-rated access on growth is unproven—start with a commodity platform to validate the hypothesis.
- Large enterprises with strict vendor risk and procurement requirements that demand documented compliance and long-term contractual commitments.
- Industries or use cases where competitors are more suitable
- Highly regulated industries requiring documented compliance controls and security attestations.
- Global products where zero-rating would apply to a small minority of users and does not materially affect core metrics.
- Technical requirements the product cannot reliably meet
- Use cases requiring guaranteed support for specialized streaming or niche networking protocols that may be incompatible with a proxying model.
- Budget constraints that favor alternatives
- If an organization's CAC/LTV cannot support paying per-MB zero-rated egress at scale, alternative platforms may be more cost-effective.
- Specific workflows or integrations that are not yet supported
- If deep integrations with CI/CD, observability, and IAM tooling are required and well-documented integrations are a procurement condition.
- Red flags in the buying process
- If security documentation, incident history, and contractual terms are not provided during diligence, treat this as a procurement escalation item.
- Current limitations acknowledged by the vendor
- Public documentation describes proxying behavior but does not clearly enumerate limits for protocol support, file size, caching behavior, or incompatibilities.
- Features on the roadmap
- No public roadmap details were discovered in accessible sources.
- Scale limitations
- No explicit public documentation was found describing practical scale limits or breakpoints.
- Security or compliance gaps
- No public SOC 2 or ISO attestations were found.
- Privacy and compliance posture for the platform is not clearly documented in public materials.
- Technical debt or architectural constraints
- No credible public review corpus was found that describes technical debt or long-term architectural issues.
- API limitations or integration constraints
- Integration capabilities and API limits were not comprehensively documented in public marketing or docs reviewed here.