Business users
Use the web app first. Workspace setup, source review, and handoff happen inside Helvabase.
Create accountDocumentation
How to onboard and use Helvabase.
Most teams do not install anything locally. They work in Helvabase, review what can be used, then either copy the Free handoff pack into their own agent or use paid Helvabase-managed Mistral drafting for a sourced dossier with a readiness gate.
Agents and LLMs
Use the AI-readable Helvabase agent notes in llms.txt and llms-full.txt.
Read agent notesUsage flow
Use Helvabase in five steps.
Step 1
Create the workspace
Set the company or team account that owns sources, reviewers, projects, and billing.
Step 2
Add sources
Upload real files or URLs and sort them into company context, products, templates, and references.
Step 3
Review authority
Approve what can be reused, keep historical references separate, and block unsupported material.
Step 4
Handoff or draft
Free users copy reviewed context into their own agent. Paid workspaces can draft a sourced dossier inside Helvabase.
Step 5
Check readiness
Review the Dossier Intelligence brief: source gaps, section risks, verification actions, and export status.
Business users
The normal path is web-first and review-first.
Helvabase is for teams preparing high-stakes business documents. The normal workflow starts in Helvabase itself, with real sources, a visible review gate, and a clear choice: copy the Free handoff into your own assistant or generate a paid server-drafted dossier for review.
What to add
Company context, product and service material, response templates, and past project references.
Accepted inputs
Real files, browser-supported folders, and http or https URLs.
Review rule
Approve current truth and reusable material, but keep historical references separate from live claims.
Outcome
A readiness preview and copy-ready context pack on Free, or a gated server-drafted dossier on paid plans.
Agent handoff
Once at least one supported source is approved, Helvabase prepares a paste-only handoff. The copied block carries reviewed context, source priorities, workflow packs, readiness warnings, blockers, and citation rules.
Copy for Claude: paste a CLAUDE.md-style instruction pack with reviewed sources, citation rules, blockers, and requested output.
Copy for Codex/OpenAI GPT: paste an AGENTS.md-style instruction pack with the same reviewed context and task constraints.
Copy for Mistral: paste Mistral Agent instructions with reviewed context and optional connector verification notes.
Copy portable pack: paste a Markdown instruction pack for Euria or another approved assistant that can accept copied context.
The Free plan stops at readiness preview and handoff. It does not generate server-side dossier prose or open DOCX export.
Paid AI drafting
Paid plans draft the dossier inside Helvabase.
Server-side Mistral generation uses the approved context pack and dossier workflow. The result is a review artifact: sections carry citations, unsupported claims stay visible, and export still requires human validation.
Solo
EUR 39/month, 10 server-drafted dossiers.
Team
EUR 149/month, 60 server-drafted dossiers.
Business
EUR 449/month, 200 server-drafted dossiers.
Enterprise
EUR 5k-15k/year, custom generation volume.
Overage
EUR 3 per additional dossier on paid plans.
Dossier Intelligence
Readiness explains why a dossier can or cannot move forward.
The readiness brief is deterministic product logic over reviewed sources, the dossier plan, the generated document, and proof checks. It helps reviewers decide what to verify; it is not an autonomous legal or commercial judgment.
What changed
Shows the current context pack, dossier plan, generated sections, and proof report state that changed the dossier status.
Evidence quality
Summarizes source confidence, citation coverage, unsupported claims, and missing evidence without treating the model as the final judge.
Section risk
Highlights sections that need human review because sources are weak, caveats remain, or support checks are incomplete.
Export status
Free remains handoff-only. Paid DOCX export opens only when the gate has no unresolved blockers.
Projects and outputs
Move from reviewed sources to controlled project outputs.
Once backend workspace and project access are ready, Helvabase can stage context packs, dossier plans, paid server-drafted dossier documents, and readiness briefs. These are review artifacts, not unreviewed final deliverables.
1
Create or load the workspace and let Helvabase provision backend mapping automatically.
2
Approve at least one real source before any generation step.
3
Open the project command center to generate a project context pack.
4
Build the dossier workflow and review the proposed response sections.
5
Generate the server-drafted dossier on a paid plan, then clear the Dossier Intelligence gate before DOCX export.
Troubleshooting
What to do when a step is blocked.
Helvabase makes blocked states visible. That is intentional. The product should not quietly pretend a source, backend mapping, or output is ready when it is not.
Sign-in is blocked
Use another enabled sign-in option or contact the workspace administrator for access.
A source is unsupported
Convert or replace the file with a supported format before trying to apply it.
Backend apply is pending
You can still review sources and prepare the agent handoff. Live apply needs backend workspace and scoped project access.
Project output generation is unavailable
The workspace may still be on Free, the generation provider may be unavailable, the readiness gate may be blocked, or backend project access may still be provisioning.
Next step
Start the workspace or sign in to continue.
Business users should start with the workspace and source workflow. Agents and operators can use the AI-readable notes at /llms.txt when they need the hosted Helvabase agent rules.