WhyLabs (LangKit): Pricing, Tiers and What's Actually Covered
AI observability and LLM safety libraries. The hosted WhyLabs platform was discontinued after the team was acquired by Apple in January 2025; the open-source libraries continue.
Pricing tiers
Verbatim from the WhyLabs pricing page on 2026-06-19. Quote-only tiers are surfaced as such, never with an inferred price.
| Tier | Price | Free allowance | Notes |
|---|---|---|---|
| whylogs / LangKit (open source) | Free / month | Unlimited self-hosted use | Commercial WhyLabs SaaS discontinued; libraries remain open source. |
Source: https://whylabs.ai/ | Verified 2026-06-19
OWASP LLM Top 10 coverage
What WhyLabs defends against, as claimed on its product pages and security documentation. Coverage flags are binary: an item is listed only if the vendor names the attack class explicitly.
- LLM01 Prompt injection
- LLM02 Sensitive information disclosure
- LLM03 Supply chain
- LLM04 Data and model poisoning
- LLM05 Improper output handling
- LLM06 Excessive agency
- LLM07 System prompt leakage
- LLM08 Vector and embedding weaknesses
- LLM09 Misinformation
- LLM10 Unbounded consumption
Hidden costs
Beyond the line-item price, every runtime AI guardrail carries operating costs the vendor page does not surface. Plan for these in any board paper.
- Per-call latency overhead. Guardrail check sits in the request path; budget 50 to 300 ms extra per LLM call.
- False-positive remediation. Allocate engineering time to tune policies after every guardrail rule change.
- Logging and retention. Guardrail decisions need to land in your SIEM. See siemcostcalculator.com.
- On-call coverage. Treat AI security alerts like SOC alerts. See securityoperationscost.com.
What WhyLabs is best for
AI observability and LLM safety libraries. The hosted WhyLabs platform was discontinued after the team was acquired by Apple in January 2025; the open-source libraries continue.