- If procurement requires independently validated security/compliance artifacts upfront
- If procurement processes require SOC 2 Type II reports, ISO certificates, penetration test summaries, a sub-processor list, and a public trust portal, the currently accessible vendor documentation may be insufficient.
- If a large, prebuilt integration catalog is required
- If the primary need is connecting to hundreds of SaaS apps quickly, platforms such as Zapier or Workato may better meet that requirement.
- If the use case is not funnel-shaped
- Waniwani’s main differentiation is deterministic, multi-step intake/conversion flows. For open-ended research agents, complex planning agents, or non-linear toolchains, general agent frameworks or custom orchestration may be more appropriate.
- If platform policy volatility is unacceptable
- Businesses that cannot tolerate frequent changes to AI client policies or directory approval processes may prefer to maintain control via web or native app surfaces and use AI as an assistive layer rather than the primary distribution channel.
- If strong evidence of ROI is required immediately
- Public case studies with audited business metrics were not available in accessible sources; buyers seeking verified ROI benchmarks may require additional validation.
- Current limitations acknowledged by the vendor
- SDK ecosystem maturity risk
- A directory listing described the SDK as "pre-alpha (APIs change without notice)," indicating potential instability and breaking changes.
- Key rotation limitation
- Documentation indicates the SDK does not support automatic key rotation for encryption keys and describes a manual key rotation approach.
- Features on the roadmap (not yet available)
- No clear, verifiable public roadmap was accessible in this research run.
- Scale limitations
- Not documented in accessible sources.
- Security or compliance gaps
- Publicly verifiable SOC 2 and ISO evidence was not accessible.
- Public privacy and terms content could not be retrieved during this research session.
- Technical debt or architectural limitations mentioned in reviews
- No independent review corpus was found to assess technical debt.
- API limitations or integration constraints
- The SDK is TypeScript-first; organizations requiring multi-language SDKs may need additional integration work.