- Review platform availability snapshot (important context)
- G2
- PromptQL has a G2 profile but no reviews were visible at the time of access; this limits the ability to use G2 for balanced sentiment. (G2 product page)
- G2 does list “alternatives” pages for PromptQL; those are not customer testimonials about PromptQL itself.
- Gartner Peer Insights
- No accessible Gartner Peer Insights product listing for PromptQL was found in the searches run. (Gartner search/results pages; similarly named product pages surfaced)
- TrustRadius
- No accessible TrustRadius product page for PromptQL was found in the searches run. (TrustRadius product directory/search)
- Community / social proof and user commentary (more accessible, but lower verification)
- Reddit (r/PromptQL)
- Example (feature detail via comment): “Natively inside PromptQL. Each thread has a persistent file system.” (This is a community claim; not independently verified.) (Reddit thread)
- The r/PromptQL subreddit appears small; posts shown have very low vote counts, suggesting limited community-scale signal so far. (Reddit subreddit view)
- PromptQL Forum (vendor-hosted community)
- A user reports: “getting the following error about a significant portion of the time” for “PromptQL DDN 503 connect error” in the console. This is one of the clearest negative user reports accessible. (Vendor forum thread)
- Hacker News
- Show HN threads exist:
- “Show HN: Hasura PromptQL: A new way of talking to your data” (Hacker News thread)
- “Show HN: PromptQL – Solving Context Size and Accuracy Issues in LLM Tool Calling” (Hacker News thread)
- These threads are likely to contain candid feedback, but this run did not open and extract specific comment quotes.
- Vendor testimonials (positive, but marketing context)
- PromptQL’s website includes testimonial-style quotes (e.g., “I am always in a flow state now,” “I am more confident (and less overwhelmed),” “I don’t keep a TODO list anymore”). These are positive signals but are not equivalent to verified third-party reviews. (Vendor product and testimonial pages)
- Why customers chose this product over alternatives (evidence level: mostly vendor positioning + inference)
- Teams attracted to “shared context” and collaborative correction rather than a single-user agent.
- Organizations needing stricter permissioning boundaries and auditability for AI actions, especially with cross-system data access. (Vendor security and feature pages)
- Why some customers left for competitors (churn reasons)
- No credible churn narratives were accessible from review platforms in this run.
- One likely churn driver (inferred) is reliability issues (e.g., intermittent connect errors) or integration friction.
- Specific outcomes customers achieved (with metrics when available)
- PromptQL case studies are presented as customer stories but require careful validation; the landing content itself doesn’t provide detailed metrics in the excerpted lines. (Vendor case study and customer story pages)
- Deal-breakers and reasons customers didn’t purchase
- Not directly available in review data for PromptQL (limited third-party review coverage).
- Common enterprise deal-breakers (inferred from typical procurement)
- Inability to verify certifications/scope (if trust center access is limited)
- Unclear pricing predictability (usage-based pricing model)
- BYOC complexity / operational overhead
- Vendor case study landing page
- PromptQL publishes a case studies index and claims it “powers some of the boldest AI initiatives” at global enterprises; it displays logos including Cisco, McD, Instacart, Swiggy, and Lightspeed. (Vendor case studies page)
- Critical evaluation
- The landing page alone does not validate that these are paid, full-scale deployments, nor does it provide independent benchmarks.
- Buyers should request:
- A customer reference call
- Quantified metrics with methodology
- Scope of deployment (number of users, systems connected)
- Security review artifacts (SOC report, ISO statement of applicability)
- Example: security architecture claims with incident framing (vendor narrative)
- The security page discusses breaches involving AI integrations and argues BYOC reduces blast radius; while the general risk theme is plausible, the specific incident narratives and claimed protection boundaries are vendor-authored and should be validated in a customer’s own threat model. (Vendor security page)