Skip to main content
This page lists what Quivr 2.0 does not do, and the limits you are most likely to meet. Versions and compatibility says what stays stable across 2.x releases.

​
What Quivr does not do

  • Text only. Quivr searches text. It does not search images, audio or video, and it does not read text inside images, so a scanned PDF is stored but not searchable (there is no OCR). Microsoft 365 attachments are stored as files, but their text is not extracted.
  • Files it can read. Text files (text/*) are read directly. Other file types need a reader plugin; Quivr ships one for PDF. Anything else is refused.
  • No user accounts, quotas or billing. Quivr is an engine: an API key belongs to an organization, not to a person. Your application manages its users, their limits and what they pay.
  • No emails or push notifications to people. Quivr records matches and can send webhooks to your system; telling people is your application’s job.
  • Alerts do not look back. An alert judges documents that become searchable after it is switched on. A preview shows what it would have caught among recent documents, but there is no way to run it over the past.
  • No keyword stemming. Keyword alerts match whole words, ignoring case and accents: strike does not match strikes. Use meaning alerts, or list the forms you need.

​
Size limits

A version over the indexing limits is stored and readable, but not searchable; its receipt says which limit it hit. Add content and Search give the details.

​
History you can lose on purpose

To keep storage bounded, Quivr reclaims old detail, at the earliest after 30 days by default: the full copies of old import requests and the evidence of old matches. The matches themselves stay. Reading expired evidence returns 410 evidence_expired, so export what you need to keep. The operator can change or disable this; see History retention.

​
Notifications

  • A webhook can arrive more than once, and it stops being retried at the end of its retry window (24 hours by default). A receiver that stays down misses webhooks, but your application can still read the matches through the API.
  • Quivr refuses webhook destinations on private or internal addresses, but it has no egress proxy or per-destination allowlist: a public address the operator configures is trusted.
  • A meaning alert judged by Jev sends the article’s text to TypeSafe. While TypeSafe is down, the keyword alerts on the same article wait too.

​
Platforms and installation

  • Local development (make dev) runs on Linux x86_64 and on Apple Silicon Macs. The full verification (make verify) runs on Linux x86_64 only.
  • Release images are published for linux/amd64 only.
  • The single-machine installation runs Temporal without high availability and is meant for one Linux amd64 host. A consistent backup needs a short full stop.
  • Upgrading from a pre-release. Upgrading in place from a 2.0.0-alpha release is not supported: start a fresh installation and send your documents again.

​
Scale

Quivr has run about one million news articles on one installation. Ten million documents per collection is not yet measured. Scale Quivr gives capacity budgets and what to watch as you grow.

​
Operations

  • Quivr exposes Prometheus metrics and OpenTelemetry traces, but ships no dashboards or alerting rules. Its in-process counters reset when a process restarts.