📚 What this page is for
A walk through the AI-infrastructure market with one question per component:
is this still our differentiation, or has it become a commodity we should buy instead of build?
Drop-in vendors are flagged with a ↪ vendor pill across the prototype.
Sources: vendor websites · Crunchbase / PitchBook (early 2026) · public customer logos. Tier judgement is opinion, not endorsement.
📌 Summary · what to flag in the prototype today
✓ Already integrated
- Ragie — RAG / vector store (Chris's branch)
🟡 Drop-in candidates
- Langfuse → Inspector
- Braintrust → Quality Gate
- Portkey → Always-On AI
- PromptLayer → Prompt Studio
🟢 Build · still our differentiation
- Output Contract / Intent Validation
- Hypothesis Lab
- Usage Hub (cost optimization layer)
- AI Second Opinion / Coverage Report
- Impact Graph / Change Plan / Artifact Seal
- Risk Classification matrix
The asymmetry: 5 commodity layers can be bought (saves engineering quarters); the rest is what makes VelocityEngine recognizable to a customer.
📊 Grafana Cloud · pills across the prototype
Blocks tagged with a Grafana Cloud pill are realizable on our existing subscription with no new infra. Green live pills mark what's already shipped.
✓ Live today
- Quality Insights — structured-logging dashboard at
veprod.grafana.net
🟡 Realizable next
- Inspector → Cloud Traces (Tempo, OTel LLM)
- Always-On AI → Cloud SLO · OnCall · Incident
- Usage Hub → Cloud Metrics + anomaly-detection
- Hallucination Detector → Cloud Alerting rules
- Customer Feedback → NPS/CSAT panels
- Activity timeline → Cloud Logs (Loki)
- Weekly Review → Cloud Reporting (PDF export)
Why this matters: Grafana Cloud covers the ops infra (traces, metrics, logs, alerts, on-call, SLOs, incidents) — engineering time goes to the campaign-domain layer on top.
🧭 How to read the "buy vs build" call
Maturity tier — Funded Series A+ or OSS standard · multi-tenant · public API + docs · real customer logos. We do not bet on toys.
Replaces real engineering — genuine months-of-work substitute, not a thin wrapper. Building internally would compete with the vendor's full-time team.
Customer can tell the difference — if a customer can distinguish "this is vendor" from "this is you", flag it. If your part is just glue, you are not differentiated.
1 · Retrieval & vector store integrated
Chunking · embedding · multi-tenant retrieval · PDF/DOCX extraction
Vendors at our tier
Ragie in useManaged RAG with hi-res layout-aware extraction · partition-based isolation · reranker + hybrid search.
Pinecone primitive · DIY chunkingVector DB only — you own chunking and embedding pipeline. Series B+, enterprise grade.
Weaviate primitive · OSS+cloudOSS vector store with managed offering · same DIY trade-off as Pinecone.
What we still own
- Source-of-truth governance · Golden Cases collections · freshness-vs-source tracking · KB drift monitoring
- Grounding score · 6-signal cross-check
- Stale-KB consumer alerts · "38 prompts depend on a chunk not re-indexed in 6 weeks"
- Workflow integration · retrieval as first-class CC-item with type-checked I/O
- Audit grade · per-run RAG_QUERY events with chunk-level provenance
Verdict: ✅ Buy. Done. Chris has the integration in branch RAG-ccItem.
2 · LLM observability / tracing flagged
Per-call payload · resolved variables · cost · latency · retry markers · session grouping
Vendors
Langfuse recommendedOSS + cloud · ~10k GitHub stars · $4M YC W23 · Samsara, Khan Academy on logos. De-facto OSS standard.
Helicone YC W23 · proxyProxy-style observability + caching. 2k+ companies. Lower friction, higher per-call latency overhead.
Arize Phoenix / AX $70M Series BOTel-native · Uber · ServiceNow. Heavyweight — overkill if you only need per-call inspector.
What we still own · Inspector
- Business-context tagging · campaign ID · asset type · MCT lineage. Vendor sees calls; we see which campaign for which client
- Domain events · SEAL_VERIFIED · OUTPUT_CONTRACT_OK · INTENT_VALIDATED · RAG_UPLOAD_FAILED · ARTIFACT_SEAL_BROKEN. Our policy primitives, not observability
- "Reproduce in <5 min" · Inspector → Studio → Eval Gate → Customer Feedback — that's a product, not a trace viewer
- Audit-grade retention · 3-tier with PII redaction tied to risk classification
Verdict: 🟡 Strongest "buy" candidate. Frees engineering to focus on the campaign-context layer.
3 · Eval-as-a-Service flagged
Datasets · LLM-judge calibration · regression detection · CI integration
Vendors
Braintrust recommended$36M Series A (a16z) · Notion · Stripe · Airtable · Zapier. Vocabulary closest to our Quality Gate.
Langfuse Evals bundledEvals + dataset versioning + judge templates inside the same product as observability. One-vendor story is attractive.
Patronus AI $17M seedPre-built evaluators (hallucination, PII, toxicity) · good complement, not a Quality Gate replacement.
What we still own · Quality Gate
- Campaign-quality rubric · brand voice · promo correctness · regulated-industry tone. Vendors don't know what "good copy for Acme Bank" looks like
- Coverage Report · 6-dimension matrix telling where the suite is weak, not just which cases pass
- Auto-capture · from Inspector + Customer Feedback — complaint → permanent regression test
- Publish-gate enforcement · sits in the Studio publish flow with seal-and-revert mechanics
Verdict: 🟡 Strong "buy". Eval orchestration is commodity now.
4 · Prompt management flagged
Versioning · branches · A/B · labels · rollback · non-engineer editing
Vendors
PromptLayer recommendedProduction at ENS · Gorgias · Speak. Established 2022 · mature non-engineer editing UI.
Langfuse Prompts bundledVersioned prompts integrated with tracing. Single-vendor consolidation play.
Latitude OSS · youngOSS prompt platform with versioning + evals. Smaller ecosystem.
What we still own · Studio
- Risk tab · Output Contract · Intent Validation · runtime policy declared per CC-item
- Change-Plan-gated edits · can't open Studio for production prompts without an approved plan in scope
- Impact Graph reverse-deps · "this edit breaks 12 MCT tenants" — vendor doesn't see your DAG
- Domain linter · contract violation risk · role-tagging on user data · KB usage hygiene
- Multi-stakeholder review · AI Second Opinion + diligence checklist + reviewer reliability score
Verdict: 🟡 "Buy" storage / versioning. Keep our authoring UX wrapping it.
5 · LLM gateway / failover flagged
Multi-provider routing · retry · circuit breaker · cost cap · semantic caching
Vendors
Portkey recommended$3M seed · production at Postman · Springworks · 200+ models · cleanest gateway UX.
OpenRouter ~$100M ARR · routing-onlyMassive dev adoption · pure routing without observability/policy depth.
LiteLLM OSS · $6MOSS proxy + hosted · 100+ providers · virtual keys · budgets. Adobe · Lemonade as users.
What we still own · Always-On AI
- Per-CC-item policy · "MULTI_LAYER prompts must use claude-opus-4.7, no fallback" · vendor routes, we set policy
- Tier-aware enforcement · Risk Classification decides what fallback is allowed per tier
- Compliance guards · Require Exact Model + region restrictions tied to client contracts
- Reliability event correlation · fallback events surface in Inspector with cost overhead tagged
Verdict: 🟡 "Buy" the plumbing. Keep tier-aware policy as our governance layer.
6 · Guardrails / output validation careful
JSON schema · PII · topic filtering · structured output · hallucination check
Vendors
Guardrails AI $7.5M seed · OSS+cloudHub of validators · ~4k stars. Generic validators, not domain rules.
Patronus AI $17M seedRuntime guardrails · hallucination · retrieval relevance · custom policies · enterprise focus.
Why we did NOT flag this
- JSON schema validation is commodity (Pydantic / Instructor cover it)
- Output Contract is more than schema — 4-phase lifecycle (write · review · publish · runtime) tied to risk tier and downstream consumer analysis. Vendors don't model that
- Intent Validation is cheap-classifier-as-gate, lives before the LLM call · vendors validate after
- Domain rules (no competitor names, no hallucinated SKUs) need workspace-specific policies vendors don't host
Verdict: 🔴 Build. Category is real but immature · "drop-in" framing would mislead the customer.
7 · Feature flags & experimentation flag + our glue
Feature flags · A/B · stats engine · sequential testing · power calculations
Vendors
Statsig $100M Series C · OpenAI customerEx-Facebook experimentation team · built-in stats · AI experiment templates.
LaunchDarkly public · enterprise pricedMature feature flag platform with experimentation. Heavyweight for AI cadence.
Eppo $20M Series A · warehouse-nativeDraftKings · Perplexity · Cameo. Stats over your warehouse.
Why we did NOT flag this
- No vendor is purpose-built for "LLM Hypothesis Lab" — they're general A/B platforms
- PICO-style framing + AI-designed experiment + pre-registered analysis is our authoring layer · vendor would only run the math
- Cassette-replay-based experiments (no real prod cost) is unique to our stack
- Adopted-hypothesis → Change Plan transition is workflow logic, not statistics
Verdict: 🟢 Build now. Consider Statsig later as the stats engine if experiment volume grows.
8 · LLM FinOps / cost observability no winner yet
Per-call cost · per-customer/team rollups · budgets · anomaly detection · forecast
Vendors
Helicone primitive · per-callPer-call cost attribution + budgets. Useful primitive, not a finance product.
Langfuse Costs primitive · trace-basedCost per trace/user/session · alerts. Built for engineering, not FinOps.
Why we did NOT flag this
- No "Datadog for LLM cost" winner exists yet · everyone builds on Helicone / Langfuse primitives
- Usage Advisor ("switch this prompt to Haiku → save $78/mo") is a domain-aware optimizer · vendors give numbers, we give recommendations
- Per-team budgets + chargeback PDF + BYOK live in our workspace model · vendors blind to it
- Cost-bounded retries tied to risk tier · that's gateway + policy, not a cost dashboard
Verdict: 🟢 Build. Re-evaluate in 12–18 months.
9 · Red-teaming / adversarial testing security, not quality
Jailbreak detection · adversarial prompts · synthetic edge cases
Vendors
Promptfoo ~5k stars · OSS+paidRed-team plugins · adversarial datasets · CI integration. Shopify · Discord · Anthropic-internal usage.
Lakera $10M seed · enterpriseRuntime + offline red-teaming · "Gandalf" famous · Dropbox · Citi customers.
Patronus AI $17M seed · adversarial setsGeneric red-teaming suites · complement to in-house quality coverage.
Why we did NOT flag this
- Maturity is real for security red-teaming · we focus on quality coverage
- AI Second Opinion is workflow-aware (cassette + Coverage Report + contract risk) · vendor red-teams in isolation
- Coverage Report identifies which dimension is undertested · vendors generate cases without that targeting
- Promptfoo is interesting as a reference for case-generation patterns · not a drop-in
Verdict: 🟢 Build · quality coverage. Evaluate Lakera if security red-teaming becomes a sales requirement.