CauseWorkHub Hosting Requirements

1 · Dedicated address

Create a private Hub subdomain.

Provision a dedicated WordPress installation at an address such as hub.yournonprofit.org. Do not install CauseWorkHub into the nonprofit’s public marketing website. Use valid HTTPS and redirect HTTP to HTTPS.

2 · Supported runtime

Use a current production server.

Configure PHP 8.3, current WordPress core, a supported MySQL/MariaDB database, PHP Fileinfo and libsodium. Allow WordPress loopback requests and scheduled tasks. The environment must support private directories outside the public document root.

Do not add a page builder, SEO plugin, cache plugin, analytics plugin, form plugin or security plugin to the private Hub. CauseWorkHub must be the only standard WordPress plugin installed there.

3 · Private storage and backups

Back up the database, encrypted Vault and separate key material.

The host must back up the WordPress database, CauseWorkHub’s private Vault directory and the separate secrets directory or server-configured Vault key. CauseWork Central does not retain a recovery copy of nonprofit files or the master key.

4 · Host hardening

Keep production errors and executable editing out of the browser.

Set WP_DEBUG_DISPLAY to false. Configure PHP with display_errors = Off, display_startup_errors = Off and expose_php = Off. Provide host-level firewalling, monitoring, backups and malware protection. Local ClamAV can be used by CauseWorkHub’s upload gate when available.

5 · Readiness check

Install CauseWorkHub and run System Health.

After installation, CauseWorkHub verifies the private storage path, cryptographic operation, plugin boundary, HTTPS, authentication protections and production configuration. Resolve failed checks before operational data or documents are imported.

Continue to migration

CauseWorkHub hosting requirements.