Data Storage | Alephant Documentation

AIvis persists data across relational storage, search storage, object storage, cache, and deployment logs. The exact storage backend depends on the deployment mode and managed services selected by the operator.

Storage inventory

Store	Typical contents	Protection focus
Postgres	Users, roles, groups, sessions, configuration, connector state, job state, and credential metadata.	Database authentication, network isolation, backups, restore tests, and encryption at rest where available.
OpenSearch	Searchable document text, metadata, chunks, vectors, and retrieval indexes.	Private network access, disk capacity, index snapshots or rebuild plan, and document visibility testing.
MinIO or S3-compatible storage	Uploaded files, connector objects, attachments, and files needed for reprocessing.	Bucket policies, access keys, object retention, encryption, and backup lifecycle.
Redis	Cache, coordination state, queue support, and short-lived runtime state.	Private network access, credential protection, memory limits, and restart behavior.
Logs and traces	Request IDs, service events, connector failures, runtime errors, and audit-relevant metadata.	Retention policy, access control, secret redaction, and SIEM export where required.

Data retention

Retention depends on deployment policy. At minimum, define retention for:

Chat and Agent activity.
Connector documents and deleted source content.
Uploaded files.
Indexes and derived chunks.
Logs, traces, and audit events.
Backups and snapshots.

Encryption and network protection

For self-hosted deployments, the operator is responsible for disk encryption, volume protection, private networking, firewall rules, and managed-service encryption settings. AIvis configuration should assume that storage services are private and reachable only by approved application services.

Backup and restore

Backups are not complete until restore has been tested. Production readiness should include a documented recovery path for Postgres, OpenSearch, object storage, and deployment configuration.

Storage review checklist

Every durable store has an owner, backup cadence, retention period, and restore test.
OpenSearch and object storage cannot be reached from the public internet.
Credential values are stored through approved secret handling.
Logs are useful for investigation without exposing raw user secrets.
Deleted or restricted source content has a documented reindex or purge path.