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

# Self-hosted Apps

> Deploy and operate popular self-hosted applications on an Arct Cloud Linux VPS.

Run automation tools, deployment platforms, monitoring services, content systems, and private data applications on an Arct Cloud Linux VPS.

Arct Cloud provides the unmanaged virtual machine. The applications in these guides are not preinstalled or managed by Arct Cloud. You remain responsible for installation, domains, TLS, application security, data protection, backups, and updates.

<Note>
  Plan recommendations are practical starting points, not performance guarantees. Check each application's current upstream requirements and monitor real CPU, memory, storage, and [outbound transfer usage](/compute/virtual-machines/overview) after deployment.
</Note>

## Automation and Deployment

<Columns cols={2}>
  <Card title="n8n" icon="diagram-project" href="/apps/n8n">
    Run workflow automation with persistent data, HTTPS webhooks, backups, and controlled updates.
  </Card>

  <Card title="Coolify" icon="cloud-arrow-up" href="/apps/coolify">
    Operate a self-hosted application platform on a dedicated Linux server.
  </Card>

  <Card title="Dokploy" icon="rocket" href="/apps/dokploy">
    Deploy applications and databases through a Docker-based platform.
  </Card>

  <Card title="Sidekick" icon="terminal" href="/apps/sidekick">
    Provision an Ubuntu VPS and deploy Dockerfile-based apps with HTTPS and encrypted secrets.
  </Card>

  <Card title="Portainer" icon="cubes" href="/apps/portainer">
    Manage Docker containers, volumes, networks, and Compose stacks from a web UI.
  </Card>
</Columns>

## Operations and Analytics

<Columns cols={2}>
  <Card title="Uptime Kuma" icon="heart-pulse" href="/apps/uptime-kuma">
    Monitor services and publish a private or public status page.
  </Card>

  <Card title="Umami" icon="chart-line" href="/apps/umami">
    Collect privacy-focused web analytics with a self-hosted PostgreSQL database.
  </Card>
</Columns>

## Content and Data

<Columns cols={2}>
  <Card title="WordPress" icon="wordpress" href="/apps/wordpress">
    Host a WordPress site with HTTPS, backups, and an update workflow.
  </Card>

  <Card title="Nextcloud" icon="cloud" href="/apps/nextcloud">
    Operate a private file-sync and collaboration service.
  </Card>

  <Card title="Paperless-ngx" icon="file-lines" href="/apps/paperless-ngx">
    Archive, OCR, search, and organize private documents.
  </Card>

  <Card title="Immich" icon="images" href="/apps/immich">
    Back up and browse a private photo and video library.
  </Card>
</Columns>

## Security, Development, and AI

<Columns cols={2}>
  <Card title="Vaultwarden" icon="shield-halved" href="/apps/vaultwarden">
    Run an unofficial Bitwarden-compatible password vault with HTTPS and backups.
  </Card>

  <Card title="Gitea" icon="code-branch" href="/apps/gitea">
    Host private Git repositories with separate web and SSH access.
  </Card>

  <Card title="Appwrite" icon="layer-group" href="/apps/appwrite">
    Run a backend platform for authentication, databases, storage, and functions.
  </Card>

  <Card title="Hermes Agent" icon="robot" href="/apps/hermes-agent">
    Install Hermes Agent and keep its messaging gateway running as a service.
  </Card>

  <Card title="OpenClaw" icon="robot" href="/apps/openclaw">
    Run an always-on personal AI assistant with private dashboard access and messaging channels.
  </Card>
</Columns>

## Shared Responsibilities

Every public deployment should include:

* A supported Linux image and current application release
* A domain with valid DNS records
* HTTPS on port `443`
* A firewall that exposes only required ports
* Unique secrets and protected administrator accounts
* Persistent storage with monitored free space
* Automated off-server backups and tested restoration
* A planned update window with release-note review and rollback data

Start with [Deploy a Server](/compute/virtual-machines/deploy), then follow the application-specific guide above.