Business leaders
Assistants that put your documents to work and answer your teams or your end users, with no development project.
The platform
EasyRag brings together knowledge import, assistant configuration, publishing and administration. Here is how the pieces fit together, and what you do at each stage.
Functional architecture
Documents are analyzed, chunked and indexed once. For each question, the agent retrieves the relevant passages, queries your tools if needed, then writes an answer that cites its sources.
Sources
Ingestion
Knowledge
Agent
Publishing
Journey
This journey reflects how the application actually works. Each step is handled by a specific role, so responsibilities stay separate.
Register an API key from a provider (OpenAI, Mistral, Anthropic, Gemini) or the address of an internal model server. It is encrypted and can be shared.
Create a knowledge base and feed it: files, websites, scheduled sync. Content validation can screen each document before indexing.
Describe the goal: AI suggests an identity, system prompt and welcome message. Choose the model, link knowledge bases with their priorities, add tools.
Tone, response language, guided flow, pre-chat form, escalation to a human, web search, handover to an agent.
Test window, side-by-side comparison of two assistants, benchmarking of several models on the same questions.
Widget on your website, public page, internal chat portal, email, Slack or API.
Metrics, conversation review, AI-powered analysis, escalations, reports. Every adjustment creates a new version of the assistant.
An integrated platform
You can build a document assistant from separate components (vector database, RAG library, chat interface, monitoring tool). But then you have to connect them, secure them, maintain them and keep them evolving together.
EasyRag delivers these functions already connected, with shared administration: a newly added document can be queried right away, every conversation is monitored along with the sources it used, and a role applies everywhere.
Attach the paid invoice and the signed request form 1. Above €500, prior approval from your manager is also required 2.
Sources
Sourced answers
The assistant can only cite excerpts actually retrieved from your knowledge bases. If it finds nothing relevant, it says so.
Understand search and citationsRoles
Configuring, testing, monitoring, answering users: six roles keep responsibilities separate. Permissions are checked by the server, not just hidden in the interface.
Security and governance| Capability | Admin | Owner | Editor | Tester | Viewer |
|---|---|---|---|---|---|
| Manage users | ✓allowed | —not allowed | —not allowed | —not allowed | —not allowed |
| Configure assistants | ✓allowed | ✓allowed | ✓allowed | —not allowed | —not allowed |
| Manage corpora | ✓allowed | ✓allowed | ✓allowed | —not allowed | —not allowed |
| Keys, credentials, MCP | ✓allowed | ✓allowed | —not allowed | —not allowed | —not allowed |
| View monitoring | ✓allowed | ✓allowed | ✓allowed | ✓allowed | —not allowed |
| Test assistants | ✓allowed | ✓allowed | ✓allowed | ✓allowed | ✓allowed |
Who it’s for
Assistants that put your documents to work and answer your teams or your end users, with no development project.
Roles, SSO, retention, auditing, choice of models and installation in your infrastructure.
White-label multi-organization, migration between instances, tools and APIs to build client solutions.
Documented REST API, JSON responses with sources, MCP tools and webhooks.
Docker containers, self-hosted models for answer generation, data in your own database.
Step-by-step guides and documentation organized by profile to help you get started.
Try the demo assistant, or tell us about your project: we’ll get back to you with a concrete feasibility assessment.