A knowledge engine, not a search wrapper.
Most "AI search" is a thin wrapper around a search index plus an LLM that paraphrases the top results. That shape pays full cost on every query, leaks injection-shaped content into the prompt, and gives the calling agent no durable memory of what it has already learned.
Why the distinction matters for agents
An agent runs in a loop. It calls retrieval, reasons over the result, calls retrieval again. If retrieval has no memory, the agent pays full cost on every call and the same fact gets re-retrieved every iteration. If retrieval has no firewall, a single poisoned page can hijack the agent's prompt context. If retrieval gives no provenance, the agent cannot tell its user where the answer came from.
DeepTap inverts the search-wrapper shape. The fact cache gives the agent durable memory across calls. The seven-layer pipeline turns retrieval into something operators can reason about layer-by-layer instead of black-box. The firewall keeps poisoned content out of the cache and the response. Every fact carries source attribution because every fact came out of the structured-extract step with attribution attached.
The Fact Cache as the architectural differentiator
Without the fact cache, DeepTap is a well-engineered retrieval pipeline. With the fact cache, every query a tenant runs compounds into a private knowledge store that the next query reuses at a fraction of the cost. The cache is what turns retrieval into a knowledge engine. It is the single most expensive thing to copy and the single most useful thing to have. See Fact Cache.
Relationship to the rest of the portfolio
- Veritize, drift tracking and output verification. Twin in the trust stack. DeepTap retrieves; Veritize verifies what the agent did with the retrieved facts.
- R1, agent substrate. R1 agents call DeepTap as their retrieval layer. The fact cache is per-tenant, so an R1 deployment compounds knowledge across the agents inside that tenant.
- RelayOne, governance plane. RelayOne sits in front of DeepTap when an enterprise needs identity-scoped access, residency tracking, and policy enforcement on retrieval.
- TrueCom, signed receipts. Powers the TrueCom auth mode. Every DeepTap response can ship with a TrueCom-signed receipt for downstream audit.
DeepTap composes with these but does not require any of them. The graceful-degradation principle holds: a DeepTap deployment without RelayOne still has auth; without Veritize still has firewall; without R1 still has retrieval; without TrueCom still has receipts.
Team
DeepTap is built by a small team inside Good Ventures Lab. The team composition is intentionally private during pre-GA preview.
Contact
Pre-GA evaluation requests, partnership inquiries, and sovereign deploy discussions: [email protected]. For pricing-specific inquiries, the form on Pricing routes through the same address.