Documentation

Documentation for operators and product teams

Argonia documentation is organized around the real product flow: configure Argo, ingest trusted knowledge, deploy a hosted assistant, and operate it with tenant-scoped control.

Quick start

From workspace to first answer

1. Access your workspace — Sign in, open the `/app` surface, and confirm the tenant attached to your operator account.
2. Upload source files — Send curated PDF or TXT documents into the knowledge base and keep source visibility under control.
3. Queue processing — Documents move through an async-ready flow so heavy ingestion can be handled by isolated workers later.
4. Configure Argo — Set the hosted assistant name, welcome message, branding, and activation state from one form.
5. Deploy — Open the hosted page directly or embed Argo into your own product surface via iframe.

What the product already supports

Tenant-scoped workspace

Navigation, knowledge base, hosted assistant configuration, and protected app routes are already wired.

Object-backed documents

Uploads are stored through the configured backend and prepared for asynchronous ingestion and retrieval.

Hosted and embedded delivery

Argonia already exposes a hosted assistant page and a reusable iframe contract for deployment.

Documentation map

The sections below show how the documentation set is intended to grow without changing product structure.

Workspace setup

Account access, tenant attachment, first login, and dashboard orientation.

Knowledge base operations

Upload, queueing, processing status, deletion, and source visibility rules.

Hosted assistant

Hosted page behavior, branding options, iframe integration, and deployment notes.

Platform operations

Container deployment, storage strategy, async jobs, and operational checks.

Integration

Deploying Argo in your surface

Argonia keeps integration deliberately simple. You can use the hosted page directly, open it from the operator surface, or embed it into your product with a stable iframe snippet.

The hosted page and API routes stay stable while the product grows, so deployment documentation can expand without rewriting the fundamentals.

Operations

Operating the knowledge flow

The ingestion model is already structured for asynchronous workers: documents are uploaded, queued, processed, and marked ready or failed with explicit run tracking.

Documents remain tenant-scoped across upload, retrieval, sessions, and citations.
Storage is object-compatible and does not depend on persistent local disk.
The same product surface can support local development and future Scaleway jobs.

Who these docs are for

Argonia documentation is written to work for operators, product teams, and technical stakeholders at the same time.

Operators

Need clear steps for uploads, status tracking, and hosted assistant management.

Product teams

Need deployment guidance, embed behavior, and a clean understanding of the product surface.

Technical stakeholders

Need confidence in storage, async processing, isolation, and deployment architecture.

Need a faster path into Argonia?

Start from pricing if you are evaluating the product, or go straight to login if your workspace is already provisioned.

Review pricing Access Argonia