Product

The whole system, one page.

Truvyo is intentionally small. One engine, two agents, four governance pieces, one Cloudflare deployment. Here's everything.

The Evidence Standard

The single rule that everything else falls out of. An answer may never make a substantive claim it cannot trace to an evidence-graded article that passed the audit.

Evidence levelMeansWhen it shows up
OfficialAuthoritative manufacturer / technical documentation.Starlink install guides, Peplink user manuals, vendor specsheets.
Field-corroboratedMultiple independent real users reported the same fix; audit confirmed no conflict with official guidance."The Mini sometimes needs a second reboot after a firmware push." True, widely reported, not in any PDF.
Corrected to officialA community claim that contradicted the official docs. Rewritten to match.Bad community fix → audit gate caught it → served the right answer instead.
Unverified - needs reviewBenched. Mirrored to your human review queue. Never reaches a customer.Single-user anecdotes, edge cases with no corroboration.

How an answer comes together

Every question takes this path. Average end-to-end time: 1.4 seconds.

  1. Request hits the edge. Cloudflare Worker resolves your tenant via the API key (KV-cached SHA-256, sub-millisecond).
  2. Routes to a Durable Object. One DO per conversation — serializes concurrent messages, holds working history hot in memory.
  3. Hybrid retrieval. Semantic arm (Vectorize) + keyword arm (D1 FTS5) run in parallel. Reciprocal Rank Fusion picks the top 5 articles. Filters enforce tenant scope, audience scope, and Published-only.
  4. Agent generates. Claude Haiku (Customer) or Sonnet (Companion). Evidence Standard restated in every system prompt. Mandatory inline [KB-N] citations.
  5. Persist + return. Both turns to D1 for the flywheel. Answer + citations + escalation flag back to the customer.

What's inside the knowledge base

Truvyo's KB is layered. The Shared Knowledge Library is curated by us — manufacturer docs, audited community fixes, current as of the most recent quarterly refresh. It compounds across every customer.

Your tenant overlay is yours alone. Internal SOPs, return policies, private-label SKU mappings, brand voice overrides. Only your instance sees it. Never extractable.

A per-tenant preference controls which layer wins when both contain content on the same topic: your POV first, canonical answer first, or blend.

Shared Library
Starlink Mini — Install guide, p.7
Official · curated by Truvyo
Tenant overlay
Your tenant — RMA policy for replacement units
Field-corroborated · tenant-only

The flywheel

Every closed conversation grades the knowledge base. Every thumbs-down flags an article for review. The KB gets better while you sleep.

  1. Per-message feedback — thumbs up/down on each agent reply, optional comment.
  2. Resolution counter — only "resolved" outcomes count toward billable resolutions. Escalations are free.
  3. Empty-retrieval logging — every question that returned nothing is logged with the SKU + product family.
  4. Nightly aggregation — per-article scores get updated. Articles with consistent thumbs-down get auto-benched.
  5. Gap-driven pipeline — the most-asked unanswered questions become research targets for the next pipeline run.

On the roadmap

What's shipping next. Each item is in active build; early-access customers help shape the spec and lock in launch pricing.

FeatureWhat it doesShip target
WhatsApp / SMS / Email channels Same engine, additional inbound channels. Dispositions count under the existing pool. Q3 2026
Billing Connect Connect Stripe, QuickBooks, NetSuite, or your customer DB. Agent answers customer-specific billing questions grounded in the actual record. Data flows IN, never extracted out. Q4 2026
Voice channel Inbound phone-call agent on the same evidence-grounded engine. Architecture shipped: Twilio Media Streams ↔ Deepgram streaming STT ↔ runAgent() ↔ ElevenLabs streaming TTS, with barge-in and hot-transfer escalation. Per-call Durable Object holds state. Streaming end-to-end token plumbing is the remaining work. Architecture: shipped · Implementation: Q1 2027
Multi-language (50+) Full agent fluency across the major business languages. Locale-aware retrieval. Q2 2027

One Cloudflare deployment. Zero servers.

Truvyo is a single Cloudflare Worker plus D1, Vectorize, KV, and R2. Free-tier capable for Phase 0; the only real variable cost is the Anthropic API — and our pricing tracks that cost directly.

Start free Read the architecture