WEBO Multisite Server Installer

From a clean VPS.
To WordPress Multisite.

Set up the web stack and operations tools on Ubuntu through a workflow with checks at every stage.

Discuss deployment
  1. Check the environment
  2. Build the web stack
  3. Configure Multisite
  4. Check the installation

A consistent baseline

Less variation between servers.
Easier to operate and maintain.

From server preflight to network handoff, each deployment has clear steps that can be reviewed.

Know the requirements before installation
Check Ubuntu, RAM, disk, swap and services that may conflict.
Agree on the technical foundation
Configure the web stack, database and WordPress Multisite as agreed.
Keep operating after handoff
Give the operations team tools for checks, backups, updates and recovery.

Each step has inputs.
Each step has an outcome.

  1. 01

    Preflight

    Confirm resources, root access, domain or IP, database and existing services.

    OutcomeConfiguration reviewed

  2. 02

    Build the infrastructure

    Install the web stack, cache, firewall and cron according to the deployment choices.

    OutcomeNetwork foundation ready

  3. 03

    Create the Multisite network

    Configure WordPress, WEBO Multisite, permissions and SSL for the target environment.

    OutcomeNetwork configured

  4. 04

    Verify and hand over

    Check services, Redis, cron, backups and administrator access before handoff.

    OutcomeOperations tools and handoff details

Target stack

Platform layers.
One clear configuration.

Use a local database or a prepared remote database. The WordPress version can be pinned in the deployment plan.

View server requirements
Service and website managementWEBO Multisite
Network and administration toolsWordPress Multisite + WP-CLI
Web runtimeNginx + PHP 8.3 FPM
Data and cacheMariaDB + Redis
Operating systemUbuntu 22.04 / 24.04

SSL, UFW and fail2ban are configured for the deployment.

Installation is the start.
Operations have a path forward.

Tools to understand the system's current state and prepare for the next change.

Status
Server overview

Review RAM, disk, services, network, health and the latest backup with the status tool.

Health
Scheduled checks

The default schedule checks services, Redis, cron, disk capacity and backups every five minutes. A cooldown limits repeated alerts; email needs a working transport.

Backup
Backup and recovery

Daily backups cover the database, uploads, plugins and themes, with 14 days of local retention. Remote storage through rclone needs separate configuration and a restore test.

Update
Controlled updates

WordPress core and installer source updates follow separate processes. The new signed release channel is still a candidate and needs acceptance before release.

Network
Scale with resources

Additional networks can use separate hosts or ports. Suitable capacity depends on CPU, RAM, traffic and each site's workload.

Start with your environment.

Testing

Lab / internal

Use a separate IP or port to test the network and integrations before moving to a production domain.

Prepare a clean VPS

New deployment

New production environment

A clean Ubuntu VPS, a ready domain, and a plan for DNS, SSL, SMTP and backups outside the server.

Agree on configuration and acceptance

Assess first

Existing system

Audit the stack, data and rollback path before proposing migration or suitable tools.

Do not run the full installer directly

A server with aaPanel, production WordPress or customer data is not a clean VPS.

Prepare properly from the start.

These details help WEBO confirm a suitable deployment approach.

Server and resources

  • Ubuntu 22.04 / 24.04 and root access.
  • The suggested platform baseline is at least 1.5 GB RAM; size real workloads separately.
  • Less than 5 GB of free disk space triggers a warning. Production needs more room for data and backups.

Domain, DNS and SSL

  • Planned domain or IP and an administrator email address.
  • DNS or Cloudflare access when needed.
  • Choose subdomain, subdirectory and mapped-domain models.

Data and operations

  • A local database or a prepared remote database with restricted access.
  • Working SMTP if email is required.
  • Backups outside the VPS and a restore test plan.

Keep a copy outside the server. Local backups do not protect data if the entire VPS is lost.

Change control

Know the package source.
Keep a recovery path.

The new release channel is still completing signature, checksum and configuration-preservation controls for installer source updates.

Candidate 0.10.1 has not replaced the production channel. Release requires clean-install and update/rollback acceptance.

  1. Get the package and instructions through a confirmed WEBO channel.
  2. Verify signatures and checksums for the release channel.
  3. Keep private configuration and the previous source before updating.
  4. Review, back up and confirm the production rollback path.

Focused on
WordPress Multisite.

The installer standardizes a defined stack and related operations tools.

Its scope differs from cPanel, DirectAdmin and aaPanel. Migration, high availability and broader integrations need a separate assessment.

The number of sites a server can run depends on resources and actual load. The plugin license and Server Installer entitlement are confirmed separately.

Learn about WEBO Multisite

Before you
begin.

Can I use it on a server with aaPanel?

Do not run the full installer there. A running server needs an audit and a backup/rollback plan before choosing a suitable approach.

Must the database be on the same VPS?

No. A remote MariaDB instance needs a prepared database and user, and must allow connections only from the web server. The installer does not install or tune the remote database server.

How is SSL handled for mapped domains?

The pipeline supports SSL according to its configuration. DNS, integration access and the origin must meet the chosen approach's requirements.

Are backups stored outside the VPS by default?

No. By default, backups stay on the VPS for 14 days. Sending them to remote storage requires separate rclone configuration. Test restores regularly.

How many networks can one VPS run?

A tool can add networks on separate hosts or ports. Determine capacity from actual CPU, RAM, traffic and plugins; unlimited capacity is not promised.

Can I buy and download the installer myself now?

WEBO currently handles deployments under review. The package, support scope and entitlement are confirmed after assessing the infrastructure. This page does not offer a self-service download yet.

Controlled deployment intake

Start with your system's
real configuration.

Share your current environment, expected number of networks and sites, and deployment needs so WEBO can define the scope with you.

Discuss deployment