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

# MainWP Introduction

> Learn what MainWP is and how it works. MainWP is a free, open-source, self-hosted WordPress management solution using the MainWP Dashboard and Child plugins with signed requests and HTTPS for secure communication.

This is Part 1 of the MainWP Getting Started guide. [Continue to Part 2: Get Started with MainWP →](https://docs.mainwp.com/getting-started/get-started-with-mainwp.md)

## What is MainWP

MainWP is a free, open-source, self-hosted solution for managing multiple WordPress sites. Whether maintaining personal blogs or client sites, MainWP provides centralized management.

MainWP consists of two essential plugins:

* **MainWP Dashboard** - Your control center, installed on a dedicated WordPress site
* **MainWP Child** - Deployed on each WordPress site you want to manage

> [!NOTE]
>
> MainWP is not designed for WordPress Multisite setups.

### MainWP Dashboard

The Dashboard plugin operates as your control center for all managed sites. We highly recommend installing it on a clean, dedicated WordPress installation to avoid plugin conflicts.

### MainWP Child

The Child plugin enables secure communication between your Dashboard and managed sites, allowing remote management and automated actions.

## Is it Secure?

### Request Signing and Encryption

MainWP Dashboard creates a 2048-bit RSA key pair for each child site and signs requests with that site's private key. MainWP Child verifies the signatures using the public key saved during connection. New connections have their private keys encrypted automatically. For connections created before version 5.3, complete the [private-key encryption steps](https://docs.mainwp.com/advanced/openssl-keys-encryption.md) if you have not already done so.

OpenSSL is the default signing library and uses SHA-256 by default. PHPSecLib is an alternative you select in the global or per-site [connection settings](https://docs.mainwp.com/advanced/custom-signature-algorithm-and-phpseclib-as-alternative-to-openssl.md).

Use HTTPS URLs for your child sites to encrypt requests and responses in transit. SSL certificate verification is enabled by default and can be configured globally or per site.

To disconnect a child site, you need access to that site's WordPress admin credentials.

### Privacy Philosophy

Since MainWP operates entirely on your server with open-source, unencrypted code, you can audit the complete codebase via [GitHub](https://github.com/mainwp/mainwp). We do not track or keep any information about your child sites.

## How it Works

### Communication Protocol

MainWP communicates with your child sites using:

* **Ports**: 80 (HTTP) and 443 (HTTPS)
* **Request signing**: OpenSSL by default, or PHPSecLib when selected
* **Transport encryption**: HTTPS (TLS) when the child site uses an HTTPS URL
* **User-Agent**:

```text theme={null}
Mozilla/5.0 (compatible; MainWP/[version]; +https://mainwp.com)
```

### No Footprint

By default, MainWP leaves no server footprint, maintaining complete privacy on your installation.

***

**Next Step**: [Get Started with MainWP →](https://docs.mainwp.com/getting-started/get-started-with-mainwp.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.