Skip to main content
Presenton stores more than database records. Plan persistence for /app_data first, then add an external database or tune document and memory processing when the workload requires it.

​
Persistent app data

/app_data contains presentations, uploaded files, generated assets, templates, exports, settings, authentication state, the default SQLite database, and local memory data.
Use a named volume or durable platform disk in production. Back it up before image upgrades, migrations, or authentication recovery.

​
Database

Without DATABASE_URL, Presenton uses SQLite in /app_data. This is suitable for personal and small single-instance deployments. Set DATABASE_URL to move application records to PostgreSQL or MySQL. Keep /app_data persistent as well—generated assets, uploads, exports, templates, and local memory are still stored there.
The repository’s Compose services enable startup migrations. For production, take a database backup before applying a new release and avoid running multiple instances through a migration until you have verified the release’s deployment behavior.

​
Presentation memory

Presenton uses Mem0 OSS with local Qdrant and SQLite storage. Memory is scoped to a presentation and helps the assistant preserve relevant context during iterative edits. The official Docker image includes the required spaCy model. Disable Mem0 if your deployment does not need iterative presentation memory or cannot reach the configured memory model.

​
Document parsing

LiteParse extracts content from uploaded documents before the presentation outline is generated.
Increase DPI when image-heavy or scanned documents need clearer extraction, at the cost of memory and processing time. Increase workers only after measuring available CPU and memory under concurrent uploads.

Supported document formats

Review supported office documents, PDFs, spreadsheets, text files, and images.

​
Telemetry

Disable anonymous tracking with:
This setting controls anonymous product telemetry; it does not prevent a configured hosted AI, image, or search provider from receiving the content sent to that provider. Use local providers and disable external search and images when the workflow requires local-only processing.

​
Backup checklist

  • Back up /app_data on a regular schedule.
  • Back up the external database separately when DATABASE_URL is set.
  • Test restoration in a separate instance.
  • Protect backups because they may contain uploaded documents and generated presentations.
  • Keep the application version and configuration used by each backup.