Question 1

What is RAGfly?

Accepted Answer

A RAG service for AI agents: it turns any document corpus —thousands or tens of thousands, scans included— into a secure, multi-tenant retrieval base that's ready for production, without building or maintaining a RAG pipeline.

Question 2

Who is it for?

Accepted Answer

For developers, consultancies and integrators building AI agents on private documents —sometimes for many different clients— who don't want to build or maintain a RAG pipeline at scale.

Question 3

How much does it cost?

Accepted Answer

Plans in USD: Free $0, Starter $39/month, Growth $149/month, Scale $590/month and Enterprise by agreement. Each plan shows active corpus, Simple Retrieval, Augmented RAG, Agentic RAG and entities; paid plans support manual add-ons and have no automatic overage. MCP, REST, CLI and SDK are available on every plan.

Question 4

How does it work?

Accepted Answer

You point RAGfly at your documents directory; the system scans, vectorizes and indexes them automatically. Then your agent retrieves by meaning and gets answers with citations to the source via MCP, REST or CLI, isolated by context and with the data handling that matches the deployment mode.

Question 5

How does an AI agent consume RAGfly?

Accepted Answer

Through a remote MCP server (SSE or HTTP) or the RAGfly Desktop CLI, authenticating with a JWT or an API Key. The catalog of operations is published at `https://ragfly.ai/agents.json` and `https://ragfly.ai/llms-full.txt`.

Question 6

What does RAGfly process, and where does my data end up?

Accepted Answer

RAGfly processes document information on the way in and relevant chunks on the way out. In Cloud it processes the original file but does not retain it after ingestion; chunks, embeddings and metadata persist. With Desktop, the original and its extraction are processed inside your network, although derivatives may be synchronized. On sovereign plans, the database and the derivatives at rest belong to the customer; RAGfly accesses the chunks it needs to retrieve and deliver context.

Question 7

How is one customer's data isolated from another's?

Accepted Answer

Multi-tenant by default: each customer lives in a corpus isolated at the database level, with a Groups → Entities → Areas structure. A consultancy or integrator can serve dozens of customers from a single platform without a single record crossing over.

Question 8

Can I use my own vector database and my own model?

Accepted Answer

It depends on the plan. Growth enables parsing-BYOK, embedding-BYOK and agentic-BYOK; Scale adds a customer-owned Supabase vector project; Enterprise supports customer LLMs and compatible vector databases.

Question 9

Which AI models does it work with — Claude, GPT, Gemini?

Accepted Answer

RAGfly is model-agnostic. It delivers retrieval with citations and permissions; your agent runs on whichever LLM you prefer —Claude, GPT, Gemini or another— and consumes RAGfly via MCP, REST or CLI.

Question 10

Which formats are supported? Does it work with scanned PDFs (OCR)?

Accepted Answer

PDF, Word, Excel and plain text, including scanned documents thanks to first-rate OCR and table and layout understanding. The focus is text and complex documents, not audio or video.

Question 11

Can I use it with regulated data (legal, healthcare, government)?

Accepted Answer

Yes. Desktop processes the original file and its extraction inside the customer's network. On sovereign plans, the customer owns the database where the derivatives persist. RAGfly still processes chunks on the way out to produce retrieval; a full in-situ runtime is the mode that keeps that processing inside the customer's infrastructure too.

Question 12

How long does it take to go from a directory to an agent answering with citations?

Accepted Answer

You point RAGfly at a directory and, with automatic ingestion, vectorization and indexing, you can have an agent answering with citations in a short time, with no human help — and without building or maintaining a RAG pipeline at scale.

Surface	List	Detail (input and output schema)	Run
REST	`GET /v1/operations`	`GET /v1/operations/{code}`	`POST /v1/operations/{code}:execute` with `{"input": {…}, "confirm": false}`
MCP	`list_operations`	`get_operation(code)`	`run_operation(code, input, confirm)`
CLI	`ragfly cloud operation list`	`ragfly cloud operation show CODE`	`ragfly cloud operation run CODE --input-json '{…}' [--confirm]`
Python SDK	`client.list_operations()`	`client.get_operation(code)`	`client.run_operation(code, input, confirm=False)`
TypeScript SDK	`client.listOperations()`	`client.getOperation({ code })`	`client.runOperation({ code, input, confirm })`

Operation	Kind	Minimum profile	Screens
`areas.add_location`	write	ADMINISTRATOR	`MANAGE_ENTITIES`
`areas.create`	write	ADMINISTRATOR	`MANAGE_ENTITIES`
`areas.delete`	write_confirm	ADMINISTRATOR	`MANAGE_ENTITIES`
`areas.list`	read	USER	`API_KEYS`, `MANAGE_ENTITIES`, `MANAGE_USERS`, `WORKSPACES`
`areas.list_locations`	read	ADMINISTRATOR	`MANAGE_ENTITIES`
`areas.remove_location`	write_confirm	ADMINISTRATOR	`MANAGE_ENTITIES`
`areas.update`	write	ADMINISTRATOR	`MANAGE_ENTITIES`

Operation	Kind	Minimum profile	Screens
`document_types.add_category`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.add_feature`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.create`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`, `GROUP_DOCUMENT_TYPES`
`document_types.delete`	write_confirm	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`, `GROUP_DOCUMENT_TYPES`
`document_types.get_boundary`	read	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.get_impact`	read	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.list`	read	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.list_categories`	read	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.list_features`	read	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.remove_category`	write_confirm	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.remove_feature`	write_confirm	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.set_boundary`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.summary_by_entity`	read	ADMINISTRATOR	`GROUP_DOCUMENT_TYPES`
`document_types.update`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`, `GROUP_DOCUMENT_TYPES`
`document_types.update_category`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`
`document_types.update_feature`	write	ADMINISTRATOR	`DOC_FEATURE_CATEGORIES`

Operation	Kind	Minimum profile	Screens
`documents.count_by_status`	read	ADMINISTRATOR	`DOCS_DASHBOARD`, `PROCESS_DOCUMENTS`, `PROCESS_PIPELINE`
`documents.delete`	write_confirm	USER	`DOCUMENTS`, `PROCESS_DOCUMENTS`
`documents.get`	read	USER	`DOCUMENTS`
`documents.get_chunks`	read	USER	`DOCUMENTS`
`documents.get_features`	read	USER	`DOCUMENTS`
`documents.list`	read	USER	`DOCS_DASHBOARD`, `DOCUMENTS`, `PROCESS_DOCUMENTS`
`documents.report_missing`	write_confirm	ADMINISTRATOR	`PROCESS_DOCUMENTS`
`documents.revert`	write_confirm	USER	`DOCUMENTS`, `PROCESS_DOCUMENTS`
`documents.set_ingestion_order`	write	ADMINISTRATOR	`PROCESS_DOCUMENTS`

Operation	Kind	Minimum profile	Screens
`entities.create`	write	ADMINISTRATOR	`MANAGE_ENTITIES`
`entities.delete`	write_confirm	ADMINISTRATOR	`MANAGE_ENTITIES`
`entities.get_dependencies`	read	ADMINISTRATOR	`MANAGE_ENTITIES`
`entities.list`	read	ADMINISTRATOR	`MANAGE_ENTITIES`, `MANAGE_USERS`, `SECURITY-DASHBOARD`
`entities.update`	write	ADMINISTRATOR	`MANAGE_ENTITIES`

Operations reference

Operations reference

Call any operation, on any surface

Operations (108: 41 read, 50 write, 17 write_confirm)

`applications`

`areas`

`audit`

`document_statuses`

`document_types`

`documents`

`entities`

`feature_categories`

`functions`

`group_processes`

`group_tasks`

`groups`

`ingestion_runs`

`locations`

`parameter_categories`

`parameter_types`

`parameters`

`pipeline_runs`

`processes`

`queue`

`roles`

`session`

`spaces`

`users`

Not published, and why (34)

Operation	Kind	Minimum profile	Screens
`group_processes.create`	write	ADMINISTRATOR	`MANAGE_GROUP_PROCESSES`
`group_processes.delete`	write_confirm	ADMINISTRATOR	`MANAGE_GROUP_PROCESSES`
`group_processes.list`	read	ADMINISTRATOR	`MANAGE_GROUP_PROCESSES`
`group_processes.reorder`	write	ADMINISTRATOR	`MANAGE_GROUP_PROCESSES`
`group_processes.update`	write	ADMINISTRATOR	`MANAGE_GROUP_PROCESSES`

Operation	Kind	Minimum profile	Screens
`group_tasks.create`	write	ADMINISTRATOR	`MANAGE_GROUP_TASKS`
`group_tasks.delete`	write_confirm	ADMINISTRATOR	`MANAGE_GROUP_TASKS`
`group_tasks.list`	read	ADMINISTRATOR	`MANAGE_GROUP_TASKS`
`group_tasks.reorder`	write	ADMINISTRATOR	`MANAGE_GROUP_TASKS`
`group_tasks.update`	write	ADMINISTRATOR	`MANAGE_GROUP_TASKS`

Operation	Kind	Minimum profile	Screens
`groups.update`	write	ADMINISTRATOR	`MANAGE_ENTITIES`
`groups.update_parameters`	write	ADMINISTRATOR	`MANAGE_ENTITIES`

Operation	Kind	Minimum profile	Screens
`ingestion_runs.advance`	write	ADMINISTRATOR	`PROCESS_PIPELINE`
`ingestion_runs.cancel`	write_confirm	ADMINISTRATOR	`PROCESS_PIPELINE`
`ingestion_runs.start`	write	ADMINISTRATOR	`PROCESS_PIPELINE`

Operation	Kind	Minimum profile	Screens
`locations.create`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.delete`	write_confirm	ADMINISTRATOR	`DOC_LOCATIONS`, `PROCESS_PIPELINE`
`locations.generate_md`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.get_acquisition_skill`	read	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.list`	read	USER	`CHAT-FINAL-USER`, `CHAT-USER`, `DOC_LOCATIONS`, `MANAGE_ENTITIES`, `PROCESS_DOCUMENTS`, `PROCESS_PIPELINE`
`locations.materialize_web`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.preview_delete`	read	ADMINISTRATOR	`DOC_LOCATIONS`, `PROCESS_PIPELINE`
`locations.rebuild_hierarchy`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.research_web`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.review_web`	write	ADMINISTRATOR	`DOC_LOCATIONS`
`locations.sync`	write	ADMINISTRATOR	`DOC_LOCATIONS`, `PROCESS_PIPELINE`
`locations.update`	write	ADMINISTRATOR	`DOC_LOCATIONS`, `PROCESS_PIPELINE`

Operation	Kind	Minimum profile	Screens
`parameters.list_group`	read	ADMINISTRATOR	`MANAGE_GROUP_PARAMS`
`parameters.update_group`	write	ADMINISTRATOR	`MANAGE_GROUP_PARAMS`

Operation	Kind	Minimum profile	Screens
`pipeline_runs.list`	read	ADMINISTRATOR	`PROCESS_DOCUMENTS`, `PROCESS_PIPELINE`
`pipeline_runs.update`	write	ADMINISTRATOR	`PROCESS_DOCUMENTS`

Operation	Kind	Minimum profile	Screens
`processes.delete`	write_confirm	USER	`PROFILE_PROCESS`
`processes.get`	read	USER	`PROFILE_PROCESS`
`processes.list`	read	USER	`PROFILE_PROCESS`
`processes.profile_dashboard`	read	USER	`PROFILE_PROCESS`
`processes.reorder`	write	USER	`PROFILE_PROCESS`
`processes.update`	write	USER	`PROFILE_PROCESS`

Operation	Kind	Minimum profile	Screens
`queue.batch_status`	read	ADMINISTRATOR	`PROCESS_DOCUMENTS`
`queue.list_orphans`	read	ADMINISTRATOR	`PROCESS_PIPELINE`
`queue.list_run`	read	ADMINISTRATOR	`PROCESS_DOCUMENTS`
`queue.pipeline_summary`	read	ADMINISTRATOR	`DOCS_DASHBOARD`, `PROCESS_PIPELINE`
`queue.process_batch`	write	ADMINISTRATOR	`PROCESS_DOCUMENTS`, `PROCESS_PIPELINE`
`queue.resolve_llm_alerts`	write	ADMINISTRATOR	`PROCESS_PIPELINE`

Operation	Kind	Minimum profile	Screens
`spaces.create`	write	USER	`WORKSPACES`
`spaces.delete`	write_confirm	USER	`WORKSPACES`
`spaces.list`	read	USER	`CHAT-FINAL-USER`, `CHAT-USER`, `WORKSPACES`
`spaces.list_documents`	read	USER	`WORKSPACES`
`spaces.promote`	write	USER	`WORKSPACES`
`spaces.reapply_skill`	write	USER	`WORKSPACES`
`spaces.refresh`	write	USER	`WORKSPACES`
`spaces.set_criteria`	write	USER	`WORKSPACES`
`spaces.update`	write	USER	`WORKSPACES`

Why	Screens	Operations
Plan changes, purchases and cancellations move money or a contract: a person does them in the web app.	`PAYMENT_METHODS`, `SUBSCRIPTION_CANCELLATIONS`	10
An agent credential does not manage credentials (API keys).	`API_KEYS`, `SECURITY-DASHBOARD`	5
Connector secrets need a person's session.	—	4
Ingestion steps driven by the web app's session. How an agent drives them is still to be decided.	`PROCESS_DOCUMENTS`, `PROCESS_PIPELINE`	4
Already published as `GET /v1/organization`.	`MANAGE_ENTITIES`	1
Already published as `GET /v1/skills`.	`PROCESS_PIPELINE`	1
Already published as `GET /v1/usage`.	`LLM_COSTS_GROUP`	1
Already published as `POST /v1/ask`.	`CHAT-HISTORY`	1
Already published as `parameters.list_group`.	`MANAGE_ENTITIES`	1
Internal machinery (LLM model registry), outside the DOCS application.	`DOC_FEATURE_CATEGORIES`	1
Internal machinery (prompt engine), outside the DOCS application.	`DOC_FEATURE_CATEGORIES`, `DOC_LOCATIONS`	1
Internal machinery (translation engine), outside the DOCS application.	`DOC_FEATURE_CATEGORIES`	1
Revealing a private parameter value needs a person's session.	`MANAGE_GROUP_PARAMS`	1
Revealing encrypted content needs a person's session. The document text never crosses the boundary.	`DOCUMENTS`	1
The full document text is shown only to a person in the web app. Agents get the summary and chunks.	`DOCUMENTS`	1
The payment portal needs a person's session.	`PAYMENT_METHODS`	1

Operation	Kind	Minimum profile	Screens
`users.add_entity`	write	ADMINISTRATOR	`MANAGE_USERS`
`users.add_role`	write	ADMINISTRATOR	`MANAGE_USERS`
`users.create`	write	ADMINISTRATOR	`MANAGE_USERS`
`users.delete`	write_confirm	ADMINISTRATOR	`MANAGE_USERS`
`users.list`	read	ADMINISTRATOR	`MANAGE_USERS`
`users.list_entities`	read	ADMINISTRATOR	`MANAGE_USERS`
`users.list_roles`	read	ADMINISTRATOR	`MANAGE_USERS`
`users.remove_entity`	write_confirm	ADMINISTRATOR	`MANAGE_USERS`
`users.reorder_roles`	write	ADMINISTRATOR	`MANAGE_USERS`
`users.update`	write	ADMINISTRATOR	`MANAGE_USERS`