Short answer: use a staged retrieval design with explicit collections, bounded queries, and traceable source context; for a one-person SaaS, keep ingestion, search, and citation as separate contracts so freshness problems do not become support tickets.
I run a marketplace help center where every article belongs to a tenant, and I judge infrastructure by revenue per hour. Shipping weekly means the retrieval path must be understandable six weeks later, when I am fixing billing instead of admiring an elegant index. The useful boundary is simple: fetch web material, normalize it, store chunks, retrieve a bounded set, then let the answer layer cite what it actually saw.
Decision note: choose the retrieval boundary before the vendor
Option Best fit Freshness and tenancy posture Main trade-off
Postgres with pgvector A team already operating Postgres Tenant and version filters live beside application rows I own index tuning and vacuum capacity
Pinecone A managed vector-first workload Namespace isolation and…