--- title: "QueryLlama FAQ" description: "Current availability, supported file types, multi-tenant isolation, bring-your-own-LLM, RBAC roles, and an honest list of what is still being built." url: "https://royalsoftworks.com/products/queryllama/faq/" source: "https://royalsoftworks.com" format: "markdown" note: "Markdown rendering of the HTML page at `url`. Same content, same canonical URL." --- FAQ # Straight answers, including 'not yet.' What QueryLlama does, what's actually built today, and how to get involved before general availability. 01 What is QueryLlama? QueryLlama is a hosted, multi-tenant document search platform: upload your organization's documents, search them by keyword, by meaning (semantic), or both at once, and — for enterprise customers — ask questions and get answers grounded in your own documents using your own choice of LLM. Access is governed by a 5-role permission system enforced at the database layer. 02 Is QueryLlama available today? QueryLlama is in active early development. The database schema, multi-tenant isolation, and the document-ingestion pipeline's chunking and embedding step are built; hybrid search, the question-answering layer, and bring-your-own-LLM proxying are in progress. We're taking on design partners ahead of general availability — join the waitlist and we'll loop you in as capabilities ship. 03 Is this the same kind of product as the old 'natural language to SQL' pitch? No — that was a mismatch with the real product and has been corrected. QueryLlama doesn't generate SQL and isn't a local/offline tool. It's a hosted SaaS document-search and question-answering platform. There's no local-Llama, zero-egress story here: documents and queries are processed by QueryLlama's hosted infrastructure, with strict per-organization data isolation. 04 What file types can I search? PDF, Word (DOCX), Excel (XLSX), PowerPoint (PPTX), plain text, Markdown, HTML, CSV, and common image formats are on the supported list. Image OCR and some of these formats are still being wired into the ingestion pipeline — ask us about your specific format if you're evaluating an early-access deployment. 05 How is my organization's data kept separate from other customers'? Every table in the database carries an organization ID, and Postgres Row-Level Security policies enforce that a query can only ever return rows belonging to the requesting user's organization — at the database layer, not just in application code. That means even an application bug can't leak one customer's documents into another's results. 06 What does 'bring your own LLM' mean? Enterprise customers can point QueryLlama's question-answering step at their own LLM endpoint — anything that speaks an OpenAI-compatible API — instead of the platform's default model. Your organization's API key and endpoint are stored per-organization, not shared across tenants. This capability is actively being built and is not yet available for general use. 07 What are the five roles, and what can each one do? Super admin (cross-organization platform operator), org admin (manages an organization's users, documents and settings), group admin (manages a subset of users/documents within an org), member (searches and asks questions), and viewer (read-only search). Fine-grained, group-level permission rules are still being built out. 08 Is there an audit trail? The database includes an append-only audit-log table — a database trigger blocks edits and deletes on it outright, so a log entry can't be quietly altered after the fact. Wiring every user and document action through to that log is part of the active build, not finished yet. 09 What does the architecture look like? A NestJS API, a Next.js frontend, Cloudflare Workers for document ingestion, Cloudflare R2 for file storage, and Supabase Postgres with pgvector for both relational data and embeddings. See the whitepaper for the full breakdown, including what's running today versus what's still being built.