Hosted
Fastest pilot — shared operational intelligence layer with private incident stores.
+ Low setup time · Managed updates · Standard export workflows
− Shared control plane · Data residency by region
Trust & compliance
Enterprise
Operational failure intelligence for production retrieval teams — private deployment, audit trails, and SOC 2 readiness program.
Architecture
Operational debugging platform layers.
- Operational RAG debugging API (symptom, root cause, remediation, trust)
- RAG failure debugger (paste logs/traces → evidence-grounded analysis)
- Investigation workflow (timeline, share links, compare)
- Private incident + design-partner stores (server-side)
- Citation evidence index (allowlisted sources, no raw customer logs in public index)
┌─────────────────────────────────────────┐ │ Enterprise UI (debugger, investigations) │ ├─────────────────────────────────────────┤ │ Operational APIs + export (Slack/Jira) │ ├─────────────────────────────────────────┤ │ Private stores (incidents, investigations)│ ├─────────────────────────────────────────┤ │ Citation evidence (allowlisted corpus) │ └─────────────────────────────────────────┘
Deployment models
VPC
Dedicated environment in your cloud with private networking and customer-managed keys.
+ Network isolation · CMK option · Audit log export to your SIEM
− Higher setup effort · Customer-operated upgrades
On-prem
Air-gapped or regulated deployments with offline operational corpus options.
+ Maximum control · Custom retention · No egress by default
− Longest integration timeline · Customer-operated HA
Supported stacks
LangChainLlamaIndexLangGraphQdrantpgvectorPineconeWeaviateOpenSearchother
Ingestion boundaries
- Public citation corpus is allowlisted expert + documentation — not your proprietary documents unless ingested to a private workspace.
- Operational incident and investigation stores are server-side JSON — never sitemap-listed or public API.
- Debugger paste inputs are not used for model training.
- VPC/on-prem pilots can disable shared multi-tenant corpus paths entirely.
Security FAQ
- Do you train on our incidents?
- No. Submissions stay in your private store. Anonymized patterns require explicit consent.
- What is the pilot SLA draft?
- 99.5% API availability target during pilot, 4h Sev-2 response, weekly operational review — formal SLA in enterprise agreement.
- How is data deleted?
- Deletion requests processed within 30 business days for incident, investigation, and application stores.
Pilot process timeline
- Week 0Architecture review
Stack map, deployment model, readiness assessment.
- Week 1–2Debugger + investigations
Wire save flow, exports, eval gate design.
- Week 3–4Incident workflow
Slack/Jira/postmortem templates, remediation tracking.
- Week 5–6Pilot review
Readiness rescoring, rollout or VPC hardening plan.
Enterprise SLA draft: 99.5% pilot availability target, 4h Sev-2 response — formal terms in agreement.
What enterprise includes
- Operational RAG debugging API with explainability envelopes
- Private incident intake and RAG failure debugger for your team
- Dedicated environment option — no shared corpus bleed
- Structured audit metadata for intake and API routes
Data retention
Operational incident submissions and debugger paste inputs are stored in private server-side files for product improvement. Retention defaults to 24 months unless your enterprise agreement specifies otherwise. You may request deletion at any time.
No training on your incidents
Submitted operational incidents are not used to train foundation models. We may derive anonymized failure patterns (failure type, stack fingerprint, symptom shape) only when you explicitly consent — never raw company names, emails, or trace excerpts in public outputs.
Private deployment
Enterprise customers can run retrieval and incident intake in a dedicated environment with VPC boundaries, customer-managed keys, and no shared multi-tenant corpus access.
Raw logs not publicly indexed
Trace excerpts, retrieval logs, and chunk IDs you paste into the debugger or incident forms are never published, sitemap-listed, or exposed via public APIs. They remain in private operational stores.
Corpus access boundaries
Public operational answers cite allowlisted expert and documentation sources. Your private workspace corpus, if enabled, is isolated from the public citation index and from other tenants.
Deletion requests
Email enterprise support with incident IDs or submission windows. We delete matching records from operational stores within 30 business days and confirm in writing.
Audit trail position
API and intake events emit structured audit metadata (timestamp, route, anonymized outcome) for enterprise review. Full request payloads are available in private deployment logs you control.
SOC 2 roadmap
We are executing a SOC 2 Type II readiness program (access controls, change management, vendor review). We do not claim SOC 2 compliance today — ask for our current control matrix and timeline.
Questions: enterprise@youtubetimestampsearch.com
Enterprise contact
Private deployment, deletion requests, and security questionnaires: enterprise@youtubetimestampsearch.com