Skip to content

Run it on your own infrastructure

WPCloudCMS can run on your own infrastructure instead of ours. Nothing about the product changes: the same panel, the same agent, the same jobs.

A self-hosted deployment has the same two pieces as the hosted one:

  1. The panel is the dashboard, the API and the AI/MCP endpoint. It stores its data in a SQLite-compatible database that it manages and migrates itself.
  2. An agent per server is a single static binary you install on each server you want to manage, with a systemd unit and a restricted sudo rule that permits only the specific operations the panel performs.

The panel signs every request to an agent with a shared secret, so neither side trusts the network.

Piece Requirement
Panel host A host that can run a container or a single binary, and can reach each agent
Database A SQLite-compatible store; the panel runs its own migrations
Agent hosts Linux with systemd, one per server you manage
DNS A hostname for the panel, and a hostname or IP for each agent
Certificates TLS on both; the agent refuses plain HTTP from anything but localhost
Providers API credentials for Hostinger and Pressable, issued per account

There is no separate edition to learn and no separate documentation to follow. Move from hosted to self-hosted, or back, without re-learning the product: the panel, the screens and the jobs are the same.

Questions about an install: speak to your account contact.