# Helvabase full AI context

Canonical site: https://helvabase.com
Sitemap: https://helvabase.com/sitemap.xml
Robots: https://helvabase.com/robots.txt

## What Helvabase is

Helvabase is the business product layer for controlled document response workflows. It is built for teams that produce offers, tender responses, client documentation, technical documentation, legal responses, and compliance material.

The product starts from a concrete business request: an RFP, tender, compliance questionnaire, legal review, client email, or technical dossier. It then helps the team map the sources, expose missing or expired proof, prepare review states, and produce an agent-ready workflow pack for Claude, Codex/OpenAI GPT, Mistral, or a portable Markdown-compatible assistant.

Helvabase public discovery is multilingual. English remains the default canonical site, with French and German public pages for the European tender wedge: reponse appel d'offres, memoire technique, questionnaire de securite, Ausschreibung beantworten, Nachweise, Freigabe, and controlled response dossiers.

Search and answer-engine discovery should treat Helvabase as response governance software for RFPs, tender responses, compliance questionnaires, legal reviews, agency proposals, managed proof, and source-backed AI drafting. It should not be described as a generic chatbot, a vector database, or a final-submission autopilot.

Canonical identity page: https://helvabase.com/about
Canonical response-governance page: https://helvabase.com/response-governance

## Hosted access model

- Helvabase is used through the hosted web app.
- There is no local installation path for normal users or normal agent usage.
- When live agent access is enabled, Helvabase provides the MCP setup and the Helvabase key.
- Users and agents should not be asked for direct backend credentials.
- Backend provisioning, workspace mapping, and source-health wiring are Helvabase responsibilities.

## Agent quickstart

1. Open Helvabase in the browser and work from the customer workspace.
2. Use `/app/onboarding` to add real files or URLs.
3. Use `/app/context` to review approved sources and prepare the agent handoff.
4. If the workspace exposes live MCP access, use the MCP setup and Helvabase key provided by Helvabase.
5. If live MCP access is not enabled yet, use the copy-ready handoff block from Helvabase.

Operating rules for agents:

- Do not ask the user to run local install commands or configure localhost.
- Do not ask the user for a direct backend key.
- Upload only real reviewed files.
- Use current client or RFP truth before templates and historical references.
- Ask for missing facts instead of guessing.
- Do not expose raw keys, secrets, or confidential source text.

## What Helvabase is not

Helvabase is not positioned as a generic document chat interface. It is not a one-click final prose generator. It is not a developer console for non-technical users. The public product language should use terms such as sources, dossiers, requirements, proof, validity, validation, missing documents, review status, owners, caveats, risks, submission snapshots, and response packs.

## Main workflows

### Response governance

Response governance is the control model Helvabase applies before a business response leaves the team. It covers source authority, evidence validity, accountable ownership, visible caveats, review decisions, and a release gate for unresolved mandatory work. Agents may draft and reason from the controlled handoff; they do not replace the final human validation step.

Canonical page: https://helvabase.com/response-governance

### RFP and tender response

Helvabase helps teams move from tender intake to a review-ready response dossier. It can organize a requirement matrix, missing proof list, proof validity state, sourced draft sections, review assignments, and a gated submission path. Current RFP files outrank templates and historical examples.

Canonical page: https://helvabase.com/solutions/rfp-response

### Tender opportunity watch

Helvabase can publish limited public tender alerts while keeping customer-specific scoring inside the authenticated product. Paid workspaces can use a reviewed company profile, Mistral-assisted fit scoring, proof-readiness checks, and project conversion to decide which TED, BOAMP, and SIMAP opportunities deserve response work. This should be positioned as evidence-fit opportunity discovery, not as generic keyword alerts.

Canonical page: https://helvabase.com/solutions/tender-opportunity-watch
Related guide: https://helvabase.com/guides/free-tender-alerts

### Legal and compliance questionnaires

Helvabase helps legal, compliance, and notary teams answer high-stakes questionnaires without hiding uncertainty. It surfaces source freshness, proof validity, questionnaire answers, caveats, missing evidence, approvals, control evidence, clause references, SME work items, submission snapshots, and unresolved blockers before text leaves the workspace.

Canonical page: https://helvabase.com/solutions/legal-compliance

### Agencies and consultants

Helvabase helps agencies and consultants reuse strong past work without confusing precedent with current truth. It separates active client documents from templates, company library material, historical references, delivery proof, and partner review inputs.

Canonical page: https://helvabase.com/solutions/agencies-consultants

## Guides, FAQ, and comparisons

Helvabase now publishes practical acquisition pages for teams searching around response workflows:

- https://helvabase.com/guides
- https://helvabase.com/guides/rfp-response
- https://helvabase.com/guides/rfp-compliance-matrix
- https://helvabase.com/guides/free-tender-alerts
- https://helvabase.com/guides/security-questionnaire
- https://helvabase.com/faq
- https://helvabase.com/changelog
- https://helvabase.com/compare/autogenai
- https://helvabase.com/compare/loopio

French and German versions are available under `/fr/...` and `/de/...` for public marketing, solutions, docs, guides, FAQ, changelog, and comparison pages. Do not redirect `/docs`; use `/fr/docs` and `/de/docs` for translated documentation.

The reviewed RFP compliance-matrix guide includes a neutral CSV template. The template contains synthetic example content and no customer data:

- https://helvabase.com/templates/rfp-compliance-matrix.csv

## Source and review principles

- Current client or RFP documents outrank reusable templates and historical examples.
- Historical references are useful precedent, not current truth.
- Generated answers should carry source references, proof validity, caveats, unresolved blockers, and review status.
- Human validation is part of the workflow, especially for legal, compliance, and enterprise proposal work.
- Private workspace content, customer documents, secrets, and internal API routes are not public discovery content.

## Search and crawler guidance

- Public discovery content lives on the canonical site, sitemap, and AI-readable text files.
- `llms.txt` and `llms-full.txt` are supplemental summaries, not ranking guarantees and not replacements for canonical HTML, sitemap, robots controls, or human review.
- Google and Bing should index public marketing, solution, guide, comparison, FAQ, docs, security, pricing, privacy, and terms pages.
- OpenAI crawlers such as OAI-SearchBot, GPTBot, and ChatGPT-User may use public pages and `llms.txt`/`llms-full.txt` for current product context.
- Anthropic crawlers such as ClaudeBot, Claude-SearchBot, and Claude-User may use public pages and `llms.txt`/`llms-full.txt` for current product context.
- Grok/xAI-style crawlers and other compliant AI bots should follow the same public/private boundary: index public product pages, not protected workspace or API routes.
- Protected `/admin/`, `/app/`, and `/api/` paths are not public discovery content and should not be used for product claims.

## Agent handoff

Helvabase prepares reviewed context packs for Claude, Codex/OpenAI GPT, Mistral, and portable Markdown-compatible assistants. These packs tell the agent what sources to trust first, which caveats to surface, which unsupported claims to avoid, and which sections need human validation before export.

If a workspace also has live MCP access enabled, Helvabase should provide that setup under Helvabase branding with a Helvabase key. Agents should not rename that flow into direct backend setup.

Canonical page: https://helvabase.com/docs

## Plans

Helvabase pricing is organized around Free, Solo, Team, and Enterprise plans. Pricing is in EUR and excludes VAT where applicable. The Free plan is intended to let users experience limited manual context import and one agent context pack.

Canonical page: https://helvabase.com/pricing

## Security and trust

Helvabase keeps credentials, OAuth secrets, email credentials, and backend access server-side. Users should see source health, freshness, parser warnings, missing metadata, caveats, and approval state before generated content is trusted.

Managed-proof files are encrypted at rest with AES-256-GCM and production key enforcement. Evidence backups are encrypted and restore-smoked during operational verification. Submission snapshots preserve evidence versions, hashes, artifacts, review state, blockers, override reasons, and a PDF manifest.

Canonical page: https://helvabase.com/security

## Privacy and terms

The public privacy policy explains the baseline handling of account data, workspace metadata, customer content, operational data, subprocessors, cookies, retention, deletion, and data rights. The terms of service define baseline responsibilities for accounts, customer content, source-first workflows, human review, acceptable use, billing, availability, and pilots.

Canonical privacy page: https://helvabase.com/privacy
Canonical terms page: https://helvabase.com/terms

## Public route map

- https://helvabase.com/
- https://helvabase.com/fr
- https://helvabase.com/de
- https://helvabase.com/features
- https://helvabase.com/about
- https://helvabase.com/response-governance
- https://helvabase.com/solutions/rfp-response
- https://helvabase.com/solutions/tender-opportunity-watch
- https://helvabase.com/solutions/legal-compliance
- https://helvabase.com/solutions/agencies-consultants
- https://helvabase.com/security
- https://helvabase.com/pricing
- https://helvabase.com/docs
- https://helvabase.com/guides
- https://helvabase.com/guides/rfp-response
- https://helvabase.com/guides/rfp-compliance-matrix
- https://helvabase.com/guides/free-tender-alerts
- https://helvabase.com/guides/security-questionnaire
- https://helvabase.com/compare/autogenai
- https://helvabase.com/compare/loopio
- https://helvabase.com/changelog
- https://helvabase.com/faq
- https://helvabase.com/contact
- https://helvabase.com/privacy
- https://helvabase.com/terms

## Non-public routes

The following route families are not public discovery content:

- https://helvabase.com/app/
- https://helvabase.com/admin/
- https://helvabase.com/api/
- https://helvabase.com/sign-in
- https://helvabase.com/register
- https://helvabase.com/verify-email