> ## Documentation Index
> Fetch the complete documentation index at: https://docs.presenton.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Host Presenton

> Run Presenton in your infrastructure with control over data, providers, access, and integrations.

Self-hosting runs the Presenton web application, REST API, and MCP server in infrastructure you control. Presenton Cloud needs no hosting setup.

## Why self-host

<CardGroup cols={2}>
  <Card title="Control deployment and data" icon="database">
    Choose the network, persistent storage, database, backup policy, and geographic location.
  </Card>

  <Card title="Bring your own providers" icon="microchip">
    Combine hosted or local text, image, and search providers without coupling them to one vendor.
  </Card>

  <Card title="Automate presentations" icon="brackets-curly">
    Use the built-in REST API and remote HTTP MCP server from your own tools.
  </Card>

  <Card title="Customize the source" icon="code">
    Inspect and modify the Apache-2.0-licensed application for your environment.
  </Card>
</CardGroup>

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

<Warning>
  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.
</Warning>

## Recommended path

<Steps>
  <Step title="Get a local instance working">
    Follow the five-minute quickstart and generate one small presentation.
  </Step>

  <Step title="Make the deployment repeatable">
    Use Compose or a cloud platform with explicit environment variables and persistent `/app_data`.
  </Step>

  <Step title="Secure remote access">
    Enable authentication, terminate HTTPS, restrict network exposure, and store secrets outside source control.
  </Step>

  <Step title="Prepare for production">
    Test backups and restores, monitor a complete generation workflow, and pin the application release.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Five-minute quickstart" icon="rocket" href="/archive/v0.9.1-beta/self-hosted/quickstart">
    Start locally with the smallest supported Docker configuration.
  </Card>

  <Card title="Docker deployment" icon="docker" href="/archive/v0.9.1-beta/hosting/docker">
    Configure Run, Compose, ports, persistence, and GPU access.
  </Card>

  <Card title="One-click cloud deployment" icon="cloud-arrow-up" href="/archive/v0.9.1-beta/hosting/one-click-deployments">
    Deploy to Railway or DigitalOcean.
  </Card>

  <Card title="Environment variables" icon="rectangle-terminal" href="/archive/v0.9.1-beta/hosting/environment-variables">
    Look up supported runtime and provider settings.
  </Card>
</CardGroup>