Data Storage and Hosting
Witzo stores operational and AI data using systems like Postgres, Redis, and vector indexing, based on your deployment environment.
Overview
Witzo uses multiple storage layers to manage conversations, leads, usage, and AI retrieval. Hosting location depends on where you deploy the system.
Database (Postgres)
Primary application data is stored in Postgres. This includes:
| Item |
|---|
| User accounts |
| Widget configurations |
| Usage tracking |
| Leads |
| Conversations metadata |
| Plan details |
Note:Retention policies depend on your deployment configuration.
Redis
Redis is used for:
| Use |
|---|
| Caching |
| Session-related performance improvements |
| Rate limiting |
| Queue support (if configured) |
Redis improves speed but does not replace persistent storage.
Vector Storage
Website content and uploaded documents are:
| Step |
|---|
| Extracted |
| Chunked |
| Embedded |
| Stored for retrieval |
Vector storage enables Retrieval-Augmented Generation (RAG).
Note:The exact vector service depends on your configured AI provider.
Deployment-Dependent Hosting
Witzo does not enforce a single hosting provider. It supports:
| Hosting Option |
|---|
| Self-hosted deployments |
| Cloud infrastructure |
| Managed database providers |
Hosting determines:
| Factor |
|---|
| Data residency |
| Backup policy |
| Encryption at rest |
| Regional compliance controls |
Important Notes or Limitations
Data residency depends entirely on your hosting provider.
Backup and retention are infrastructure responsibilities.
Vector storage provider configuration affects data flow.