Why self-host
Control deployment and data
Choose the network, persistent storage, database, backup policy, and geographic location.
Bring your own providers
Combine hosted or local text, image, and search providers without coupling them to one vendor.
Automate presentations
Use the built-in REST API and remote HTTP MCP server from your own tools.
Customize the source
Inspect and modify the Apache-2.0-licensed application for your environment.
What self-hosting includes
- Browser-based presentation generation, editing, templates, and export.
- Persistent presentations, uploads, generated assets, settings, and local memory under
/app_data. - Configurable text, image, search, and database providers.
- Optional single-administrator authentication for the browser and REST API.
- A built-in MCP endpoint for compatible clients.
- Docker and GPU-capable Compose services.
Recommended path
1
Get a local instance working
Follow the five-minute quickstart and generate one small presentation.
2
Make the deployment repeatable
Use Compose or a cloud platform with explicit environment variables and persistent
/app_data.3
Secure remote access
Enable authentication, terminate HTTPS, restrict network exposure, and store secrets outside source control.
4
Prepare for production
Test backups and restores, monitor a complete generation workflow, and pin the application release.
Five-minute quickstart
Start locally with the smallest supported Docker configuration.
Docker deployment
Configure Run, Compose, ports, persistence, and GPU access.
One-click cloud deployment
Deploy to Railway or DigitalOcean.
Environment variables
Look up supported runtime and provider settings.