Skip to content

Self-hosted Web

Self-hosted Web comes from the open-source PromptHub project. You operate its server and data. It is separate from official PromptHub Cloud, including accounts, credentials, and backups.

Deploy on a NAS, VPS, or local machine. Manage Prompts, Folders, Skills, MCP, Plugins, Rules, and media with resource editing, version history, and complete package import/export. The browser cannot scan your computer or distribute assets to its local Agents.

From a checkout of PromptHub v0.6.2:

Terminal window
cd apps/web
cp .env.example .env

Edit .env first: configure your JWT_SECRET and persistent storage. Then start the service:

Terminal window
docker compose up -d --build
  • JWT_SECRET: use a random value at least 32 characters long.
  • ALLOW_REGISTRATION=false: keep unnecessary public registration disabled after setup.
  • DATA_ROOT: verify the data root and persistent mounts, retaining data, config, logs, and backups.

The default address is http://localhost:3871. Initial setup at /setup creates the administrator. Use HTTPS for public access. Consult the versioned deployment guide for complete configuration.

In desktop data settings, select Self-Hosted PromptHub, enter the address and credentials, and test backup support. Server and desktop versions must match exactly.

Manual and automatic backups create independent snapshots without replacing the live server workspace. Startup and scheduled jobs upload only. Restoration requires confirmation and creates a local safety snapshot first. See Backup and Restore.

Experimental Cloudflare Workers deployment

Section titled “Experimental Cloudflare Workers deployment”

The experimental version uses Workers for the API, D1 for data and sync metadata, and R2 for media and resources. It still exposes the older live-sync API. Until it provides the dedicated /api/backups/desktop capability, it is not a safe snapshot target for the newer desktop backup flow.

Read the versioned Cloudflare guide before choosing it. Do not assume feature parity with the Node deployment.

Back up persistent directories before upgrades and check restoration steps. A database-only copy omits Skill and Plugin package files and images. Keep secrets and private deployment configuration out of public repositories.