- Company sizes or stages where this product is overkill or insufficient
- Overkill
- Solo prototyping where a local agent and simple scripts plus a lightweight evaluation harness are sufficient.
- Insufficient
- Large enterprises requiring mature, publicly documented compliance artifacts and deep governance controls prior to procurement.
- Industries or use cases where competitors are better suited
- If the primary need is tracing and evaluations for existing agent code, LangSmith, Langfuse, or Phoenix may provide faster time-to-value without adopting a new execution model.
- If durable, long-running workflow orchestration across many services is required, Temporal or similar workflow engines are typically better suited as the primary orchestrator.
- Technical requirements that are unclear or not met
- Strict data residency requirements for specific regions: Jetty claims Enterprise flexibility, but public details were not found; contractual confirmation is advised.
- Detailed SSO/SCIM requirements: these were not clearly documented publicly and should be confirmed.
- Budget considerations
- If run quotas are difficult to forecast, quota-based billing can be risky.
- Open-source or self-hosted alternatives for observability (e.g., Langfuse self-host, Phoenix) may be preferable when budget constraints exist and engineering resources are available.
- Specific workflows or integrations where the product may not be ideal
- Workflows with many parallel child tasks: Jetty’s counting of child tasks as separate runs can increase costs significantly.
- Red flags in the buying process
- If the vendor cannot provide written details on security controls, data retention/deletion, incident response, audit logging access controls, and how provider keys are stored and rotated, proceed with caution.
- Current limitations acknowledged by the vendor
- Proxy timeout behavior
- Jetty documents that synchronous runs exceeding around 100 seconds may return a Cloudflare 524 response while the run continues server-side. The recommended practice is to poll recorded trajectories rather than retrying.
- Features on the roadmap (not yet available)
- No explicit public roadmap items were found in the reviewed materials.
- Scale limitations
- Public materials did not document explicit volume or throughput limits beyond stated run quotas and team member caps.
- Security or compliance gaps
- Jetty describes Enterprise support for SOC 2, HIPAA, BAAs, and DPAs, but publicly accessible validation artifacts (trust center pages or report availability statements) were not identified.
- API limitations or integration constraints
- While the API is OpenAI-compatible, advanced runbook mode requires Jetty-specific request fields and operational patterns (including async polling for long runs).