Skip to main content

Operations Roadmap

This is deliberately separate from the Roadmap and Detailed Roadmap. Those describe the product - what Yew Search does for the people using it. This page describes the supporting software needed to actually run and understand Yew Search as a service: observing whether the system is healthy, and understanding whether anyone is actually using the marketing/docs sites. None of this is user-facing product functionality.

Observability in production​

Resolved (this section originally described a gap in an AWS-hosted deployment; production now runs entirely on the homelab, not AWS - see Server Deployment). Verified directly: yew-backend-prod's own environment has LOGGING_ENABLED, TRACING_ENABLED, and METRICS_ENABLED all true, pointing at loki/tempo hostnames also on the homelab, and loki, tempo, grafana, and prometheus are all running containers there today. The observability stack isn't just built and documented - it's live, wired up, and actually receiving data from production.

Why this matters independent of the product roadmap: none of the knowledge-engine capabilities (search quality, the MCP server, the conversational assistant) can be responsibly operated without knowing whether the system is actually healthy - a search-quality regression or an MCP server outage should be caught by observability tooling, not by a user complaining first.

Website/docs traffic analytics (Matomo)​

Resolved. A matomo + matomo-db container pair is running on the homelab today. Not independently verified here: whether it's actually wired into the live website/docs frontend (a running container doesn't by itself confirm the tracking snippet is deployed) - worth a follow-up check specifically on that, separate from "is the container up."

Open questions, not yet decided​

  • Whether Matomo's tracking is actually integrated into the deployed website/docs pages, not just running as a container (see above - genuinely unverified, not assumed either way).
  • Whether this work is a prerequisite for V2/V3 (operating a multi-tenant SaaS without observability seems clearly wrong) or can continue to be deferred through V1.