# Helvabase > Company sources, evidence and human review for business responses in your own AI assistant. Canonical website: https://helvabase.com Public languages: English, French and German. Helvabase is being designed for document work in Mistral, Claude and Codex, all equal first-class client targets. The customer’s assistant handles analysis and drafting. Helvabase retains business permissions, dossier versions, evidence and review decisions; Snipara supplies ingestion, indexing and retrieval. ## Availability Integrations for Mistral, Claude and Codex are available to test. Compatibility must be verified for the exact client and enabled capabilities; a previous standalone export does not certify the complete multi-document workflow. Public examples are illustrative and use fictional documents. Do not describe a working MCP connection alone as proof of original-file transfer, human review or file delivery. Create an account and follow https://helvabase.com/connect. Check the client-specific file-transfer limits in the guide. ## Start here - [Connection and pilot guide](https://helvabase.com/docs) - [Mistral pilot preparation](https://helvabase.com/docs#mistral) - [Claude pilot preparation](https://helvabase.com/docs#claude) - [Codex pilot preparation](https://helvabase.com/docs#codex) - [About](https://helvabase.com/about) - [Features](https://helvabase.com/features) - [Response governance and authoritative copy vault management](https://helvabase.com/response-governance) - [Workflow](https://helvabase.com/features) - [RFP response database and knowledge base workflow](https://helvabase.com/solutions/rfp-response) - [RFP response software](https://helvabase.com/rfp-response-software) - [Tender response software](https://helvabase.com/tender-response-software) - [AI RFP response software with source citations](https://helvabase.com/ai-rfp-response-software) - [RFP evidence management](https://helvabase.com/rfp-evidence-management) - [RFP response review workflow](https://helvabase.com/proposal-response-review-workflow) - [Logiciel IA pour répondre aux appels d’offres](https://helvabase.com/fr/logiciel-reponse-appel-offres) - [Security and data boundaries](https://helvabase.com/security) - [Current catalogue and pilot scope](https://helvabase.com/pricing) - [RFP compliance matrix example](https://helvabase.com/guides/rfp-compliance-matrix) - [Tender watch](https://helvabase.com/solutions/tender-opportunity-watch) - [Compliance questionnaire response](https://helvabase.com/solutions/legal-compliance) - [Pilot contact](https://helvabase.com/contact) - [Full agent notes](https://helvabase.com/llms-full.txt) ## Boundaries - Document work happens in the customer’s assistant. Sign-in and billing use secure web pages. - Free includes entitlement to one lifetime dossier, 100 MB of shared source space and 10 prepared source selections. Solo is EUR 39/month for 10 newly activated dossiers per subscription month and 1 GB of source space; Team is EUR 149/month for 60 and 5 GB. Paid dossier allowances renew monthly on the subscription anniversary. Existing dossiers are not counted again; paid plans have no separate active-dossier count cap. Enterprise source allowances are contractual. - Commercial source space uses decimal units (1 MB = 1,000,000 bytes; 1 GB = 1,000,000,000 bytes). Each retained source version counts once per workspace, including when reused in several dossiers. Versions and pending reservations occupy source space; monthly dossier renewal and archiving do not release it. Internal technical copies are measured separately. This allowance does not establish permanent original-file archiving; destination-specific transfer and retention terms still apply. - The assistant’s subscription is separate from Helvabase. Read current prices and quotas on the pricing page; do not invent commercial terms. - Source references are evidence candidates, not automatic approvals. The compliance matrix separates extraction coverage, answers, proof and human review. Dossier approval and admission to the reusable knowledge library are separate decisions. Reuse rechecks scope, validity and contradictions; no model retraining is implied. - Select and authorise the relevant files. Do not infer whole-drive access from a request to use one document. - Do not request passwords, payment details or backend API keys in conversation. - Confirm processing locations for the chosen client and enabled features. The application and primary databases are hosted at OVHcloud in Roubaix, France; primary Vaultbrix database backups are stored at Exoscale in Geneva, Switzerland. Additional database backups use Cloudflare R2, without a Swiss-only residency claim. This does not prove European-only processing by external AI clients and optional providers. - No customer statistics or time-savings claims are offered as launch proof. - not a ranking or citation guarantee. Search visibility guidance: - This file is intended for discovery; not a reliability ranking or recommendation. ## Team workflow and pilot boundaries The lead uses their assistant; invited contributors and reviewers use secure web sheets without needing their own AI subscription. Free and Solo include one person, Team includes three people in total. Review exact versions before requesting supported files. Human validation is never inferred from an assistant response. A full autonomous path is not yet verified for every native client. Confirm the exact client surface, file transfer and returned files in a pilot. Managed original-file production has a 1 MiB per-file limit and bounded profiles: tagged plain-text Word controls, supported existing Excel cells and passive PDF AcroForm fields. Excel formulas are preserved without recalculation. Arbitrary layouts, scanned PDF filling and general OCR are not promised. Commercial storage space does not lift these limits.