- Company sizes or stages where this product is overkill or insufficient
- Very small prototypes or hobby projects that only require a minimal MCP endpoint and basic monitoring; simple serverless functions or self-hosted solutions may suffice.
- Highly regulated enterprises that require publicly available and audited compliance artifacts during procurement; the vendor's public compliance documentation is limited.
- Industries or use cases where competitors are clearly superior
- Highly regulated industries that require comprehensive procurement-ready compliance documentation and long vendor track records.
- Deployments requiring guaranteed data residency controls without relying on BYO Cloud.
- Technical requirements that this product cannot meet
- Organizations that require official, out-of-the-box support for runtimes other than Node.js 22 or Python 3.13 as documented publicly.
- Budget constraints that make alternatives more appropriate
- For predictable, high-volume request patterns, implementing observability on existing cloud infrastructure may be more cost-effective than a request-metered platform with overage rates.
- Specific workflows or integrations where the product falls short
- If exposing non-MCP custom HTTP endpoints from the same deployment is a core requirement, document-level warnings about custom endpoints should be validated; alternative architectures or vendors may be preferable.
- Red flags in the buying process
- If the vendor cannot supply requested security documentation (SOC 2 report, penetration-test summaries, DPA) during procurement, this may be a procurement-blocking issue.
- If the definition and metering of "requests" is not clearly defined in contract terms, clarify before committing.
- Current limitations acknowledged by the vendor
- Skybridge roadmap gaps include certain MCP Apps spec features still in development, such as full tool metadata exposure, CSS theming variable support, advanced display mode options, and some streaming capabilities.
- Features on the roadmap (not yet available) - note estimated dates if available
- No firm dates for roadmap items were provided in the sources accessed.
- Scale limitations (at what volume/size does it break down?)
- Public documentation lists plan tiers up to 2M requests/month before Enterprise custom pricing; no public quantitative scale failure points were disclosed.
- Security or compliance gaps
- Beyond marketing references to SOC 2, detailed certification reports and procurement-facing compliance artifacts are not publicly documented.
- Technical debt or architectural limitations mentioned in reviews
- No independent reviews documenting technical debt were found; vendor documentation lists common integration/configuration issues.
- API limitations or integration constraints
- Documentation indicates constraints around exposing custom HTTP endpoints and the requirement to mount the MCP handler correctly at /mcp for correct operation.