Known limitationsBeta

Researcher Center works end to end, but the items below are known constraints during beta. We aim to be honest about current scope.

Supported files and limits

Up to 25 MB per file.
PDF, Word (.docx), Markdown/text, CSV/TSV, and common code/text files; any text file.
No OCR for scanned images, and no audio/video in beta.

AI answer-quality caveats

Answers come from your uploaded sources only - not web search or general knowledge.
Quality depends on what your documents contain; verify against the cited sources.
Every answer cites its sources; when the sources do not support an answer, the system declines rather than fabricating.
Beta uses a single embedding model and dimension; switching is a later capability.

AI provider modes and disclosure

Provider mode is set at the organization level: platform-managed, bring-your-own-key, or local/self-hosted.
On the platform-managed path, your document and question text is sent to the external OpenAI API to produce embeddings and answers. This is opt-in; local/self-hosted is the default architecture.
Bring-your-own-key uses your provider key (they process and bill you); local/ self-hosted runs on your own hardware so data stays in your environment.

AI credits and caps

Each plan includes monthly AI credits at the organization level.
Managed usage is hard-capped; at the cap, AI requests are blocked (HTTP 402) until the next period. There is no unlimited platform-paid usage.
Bring-your-own-key and local usage are metered but never platform-capped. Cost figures shown are estimates, not a bill.

Other beta limitations and data handling

No SSO yet - sign-in is email and password.
Single region during beta; no multi-region failover.
Data isolation: each group's data is isolated per tenant. We do not log your document text, prompts, answers, or secrets.
Retention: uploaded documents and derived data are kept for the life of the workspace until you delete them; deleting removes them from the database and object store. A formal retention window is being finalized.
No formal uptime SLA during beta (best-effort; see support).

For sensitive or regulated data, prefer bring-your-own-key or local/self-hosted mode and confirm compliance with your institution's data-handling policies before uploading. See the privacy page.