Skip to main content
This guide gets Presenton running locally with Docker, persistent storage, and a text provider. It also explains what the deployment includes and where to go for custom enterprise capabilities.

​
Before you start

You need:
  • Docker
  • Credentials for a supported text provider, or a reachable local model
  • Port 5001 available on your computer
Presenton Cloud needs no hosting setup. Use this guide only when you want to run Presenton in infrastructure you control.
Self-hosting the application does not make every workflow local. Configured hosted AI, image, or search providers receive the content sent to them. Choose local providers and disable external integrations when content must remain inside your network.

​
1. Start Presenton

The host folder is mounted at /app_data so presentations and settings survive container replacement.

​
2. Open Presenton

Visit http://localhost:5001. If the page does not load, check the container:

​
3. Connect a text provider

Follow the first-run Settings flow and choose a provider. For the shortest hosted-provider setup, enter an API key and supported model in the application. To keep administrator-supplied credentials out of the UI, restart the container with environment variables instead:
Do not paste real keys into source files or commit a .env file. Use your deployment platform’s secret manager for a remote instance.

​
4. Generate and persist a test deck

Create a short two- or three-slide presentation. Restart the container with docker restart presenton, reopen the dashboard, and confirm the deck remains available.
The application loads, a text provider generates a deck, export completes, and the deck remains after restart.

​
What you are self-hosting

The container runs the Presenton web application, REST API, and MCP server. A self-hosted deployment 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
  • Multi-user authentication with private workspaces and administrator-managed access
  • A built-in MCP endpoint for compatible clients
  • Docker and GPU-capable Compose services

​
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.

​
Enterprise support

Role-based access control

Scope custom roles and permissions for teams with different responsibilities.

OAuth and SSO

Discuss OAuth, OpenID Connect, and identity-provider integration for your organization.

Custom deployment

Plan private, on-premise, air-gapped, or hybrid deployments around your requirements.

Custom integrations

Connect Presenton to internal systems, workflows, templates, and data sources.
Need capabilities beyond the open-source self-hosted deployment? Contact the Presenton enterprise team to discuss RBAC, OAuth and SSO, custom integrations, deployment assistance, onboarding, and support.

Explore enterprise support

Review common enterprise requirements and contact the team to scope a solution.