Applications

📄️Applications

The Websites section in the OpenPanel sidebar provides access to the Auto Installer, Site Manager and WP Manager pages, where you can install and manage WordPress, NodeJS or Python Applications.

📄️Auto Installer

Auto Installer allows you to one-click install applications.

📄️Website Builder

GrapeJS is a drag & drop website builder integrated into OpenPanel that you can use to create static HTML websites with tailwindcss.

Install and manage Joomla sites in an existing domain, via Joomla's own CLI installer — deliberately simpler than the WordPress Manager: no dedicated Joomla Manager sidebar page, no cloning, no filesystem scan for existing installs, no hardening rules, and no dedicated backup system. Install, a read-only overview with live status, cache clearing, one-time admin login, error logs, and uninstall.

📄️Drupal Manager

Install and manage Drupal sites in an existing domain, via Composer and Drush — deliberately simpler than the WordPress Manager: no dedicated Drupal Manager sidebar page, no cloning, no filesystem scan for existing installs, no hardening rules, no drush passthrough console, and no dedicated backup system. Install, a read-only overview, and uninstall.

📄️PrestaShop Manager

Install and manage PrestaShop sites in an existing domain, via PrestaShop's own install/index_cli.php CLI installer — deliberately simpler than the WordPress Manager: no dedicated PrestaShop Manager sidebar page, no cloning, no filesystem scan for existing installs, no hardening rules, and no dedicated backup system. Install, a read-only overview with live status, cache clearing, one-time admin login, error logs, and uninstall.

📄️OpenCart Manager

Install and manage OpenCart sites in an existing domain, via OpenCart's own CLI installer — deliberately simpler than the WordPress Manager: no dedicated OpenCart Manager sidebar page, no cloning, no filesystem scan for existing installs, no hardening rules, and no dedicated backup system. Install, a read-only overview with live status, cache clearing, one-time admin login, error logs, and uninstall.

📄️phpBB Manager

Install and manage phpBB forums in an existing domain, via phpBB's own dedicated CLI installer — deliberately simpler than the WordPress Manager: no dedicated phpBB Manager sidebar page, no scanning the filesystem for existing installs, no hardening rules, and no one-click self-update. Install, a read-only overview with live status, cloning, a full backup/restore system, and uninstall — updates are pointed at phpBB's own Admin Control Panel rather than automated.

📄️Flarum Manager

Install and manage Flarum forums in an existing domain, via a Composer project and Flarum's own console installer — deliberately simpler than the WordPress Manager: no dedicated Flarum Manager sidebar page, no scanning the filesystem for existing installs, no hardening rules, and no one-click admin login (Flarum's console has no login/session command to reach for). Install, a read-only overview with live status, cache clearing, error logs, cloning, a full backup/restore system, one-click self-update, and uninstall.

📄️MediaWiki Manager

Install and manage MediaWiki wikis in an existing domain, via MediaWiki's own non-interactive CLI installer — deliberately simpler than the WordPress Manager: no dedicated MediaWiki Manager sidebar page, no scanning the filesystem for existing installs, and no hardening rules. Install, a read-only overview with live status, error logs, one-time admin login, cloning, a full backup/restore system, and self-update.

📄️DokuWiki Manager

Install and manage DokuWiki wikis in an existing domain. DokuWiki stores everything as flat files — no database — so this module is simpler than most: no dedicated DokuWiki Manager sidebar page, no scanning the filesystem for existing installs, no hardening rules, and no admin login helper (there's no database-backed session table to issue tokens against, and the install form already sets the admin password directly). Install, a read-only overview with live status, cloning, a files-only backup/restore system, and self-update.

📄️SofaWiki Manager

Install and manage SofaWiki sites in an existing domain — considerably simpler than the WordPress Manager: no database at all, no admin account created by OpenPanel, no CLI installer to drive, no dedicated SofaWiki Manager sidebar page, no scanning for existing installs, no hardening rules, no maintenance mode, no admin auto-login, and no cache to clear. Install, a read-only overview, cloning, a files-only backup system, and uninstall.

📄️Matomo Manager

Install and manage Matomo — self-hosted, privacy-focused web analytics software, not a website CMS — in an existing domain or subfolder, the same install pattern as OpenPanel's other app managers even though Matomo serves an analytics dashboard rather than a public site. Simpler than the WordPress Manager in a few ways: no dedicated Matomo Manager sidebar page, no scanning the filesystem for existing installs, no hardening rules, and no maintenance-mode toggle (Matomo has no offline-mode primitive to switch). It does get its own backup/restore system, cloning, in-place updates, one-click admin login, cache clearing, and a log viewer.

📄️Nextcloud Manager

Install and manage Nextcloud sites in an existing domain, via Nextcloud's own occ maintenance no dedicated Nextcloud Manager sidebar page, no cloning, no filesystem scan for existing installs, no hardening rules, and no dedicated backup system. Install, a read-only overview with live status, cache clearing, one-time admin login, error logs, and uninstall.

📄️TinyPhotoGallery Manager

Install and manage TinyPhotoGallery in an existing domain — the simplest of OpenPanel's app managers. TinyPhotoGallery is a single PHP file plus an empty photos/ folder: no database, no admin account, no CLI installer, no versioning, and no update mechanism upstream. There is no dedicated TinyPhotoGallery Manager sidebar page, no cloning, no scanning for existing installs, no hardening rules, no maintenance mode, no admin auto-login, and no cache to clear.

📄️TinyFileManager Manager

Install and manage TinyFileManager in an existing domain. This installs a standalone, password-protected, web-based file manager as a regular PHP application into a domain's docroot — a separate tool visitors log into at the site's own URL — which is entirely distinct from OpenPanel's own built-in File Manager used for browsing your hosting account's files from inside the panel. TinyFileManager is a single PHP file with no database, no CLI installer, no versioning, and no update mechanism upstream, so this manager is deliberately minimal: no dedicated sidebar page, no cloning, no scanning for existing installs, no hardening rules, no maintenance mode, no admin auto-login, and no cache to clear.

📄️Moodle Manager

Install and manage Moodle — an open-source learning management system (LMS) — in an existing domain, via Moodle's own CLI installer. Install, a read-only overview with live status, cache clearing, error logs, maintenance mode, a dedicated backup/restore system, cloning, self-update, and uninstall.

📄️OJS Manager

Install and manage Open Journal Systems (OJS) sites — open-source journal and scholarly publishing management software from the Public Knowledge Project — in an existing domain, via OJS's own CLI installer. Install, a read-only overview with live status, cache clearing, one-time admin login, error logs, a dedicated backup/restore system, cloning, self-update, and uninstall.

📄️Node.js Applications

Containerized Node.js applications can be created and managed in OpenPanel Enterprise Edition.

📄️Python Applications

Containerized Python applications can be created and managed in OpenPanel Enterprise Edition.

📄️Ruby Applications

Containerized Ruby applications can be created and managed in OpenPanel Enterprise Edition.

📄️Java Applications

Containerized Java applications can be created and managed in OpenPanel Enterprise Edition.

📄️PHP Applications

Deploy a Composer-based PHP application into an existing domain. Unlike the containerized Node.js, Python, Ruby, and Java application installers, a PHP application never gets a dedicated container: it never creates a new container, edits docker-compose.yml, or configures a reverse proxy. The domain's existing vhost already routes to its PHP-FPM (or LiteSpeed) container, so installing a PHP application is really just deploying Composer-managed code into that domain's docroot and, optionally, running Composer against it.