JK JKSolutions
Home › Documentation › JKPanel Pro › System Requirements
Deployment preparation

System Requirements

Plan the host, network, database and runtime environment before installing JKPanel Pro.

Reference deployment stack

JKPanel Pro is deployed on a standard Linux web application stack. The current JKSolutions reference environment uses Ubuntu Server, Nginx, PHP-FPM, MariaDB and Redis.

The exact sizing required for a production installation depends on customer count, order activity, integrations, background jobs and retained operational data.

  • Operating system: a maintained 64-bit Linux server environment.
  • Web server: Nginx with HTTPS enabled for production.
  • Application runtime: PHP-FPM and the PHP extensions required by the installed release.
  • Database: MariaDB/MySQL-compatible database.
  • Cache/runtime services: Redis where enabled by the deployment.
  • TLS: a valid certificate for the production hostname.
  • Time: correct system timezone and clock synchronisation.
The production release package and installer should remain the authoritative source for version-specific package requirements.

Network and DNS

  • Create the final production hostname before customer traffic is enabled.
  • Point public DNS to the deployment server or intended reverse proxy.
  • Permit only the inbound ports required for the deployment.
  • Ensure outbound access required by configured registrars, gateways, server APIs and notification services is available.
  • Use HTTPS for administration and customer-facing access.

Database planning

Use a dedicated application database and a scoped database account. Avoid using the MariaDB root account as the normal JKPanel Pro application credential.

  • Back up the database before upgrades or high-impact maintenance.
  • Restrict remote database exposure unless the architecture explicitly requires it.
  • Protect database credentials as deployment secrets.
  • Monitor storage consumption and database growth.

Before production

  1. DNS and TLS

    Verify the production hostname and certificate.

  2. Application health

    Confirm the dashboard and authenticated routes load correctly.

  3. Database

    Confirm database connectivity and migration state.

  4. Integrations

    Test each configured provider before assigning it to customer services.

  5. Backup

    Create and validate a recoverable backup before launch.

  6. Updates

    Verify updater status and rollback readiness.