Leave cPanel this afternoon.

One command installs KLYRN on a fresh Ubuntu server. It brings your sites over from cPanel or DirectAdmin and lets you check each one before you touch DNS.

curl -fsSL https://get.klyrn.com | sudo bash

Install Free Watch the tour 1:26

The KLYRN panel's overview of one server: what needs attention first, then resources, sites and recent activity. — The real panel, with demo data.

53s: From a fresh server to a working panel
11: Install stages, each one checked
22: Health checks from one command
0: Root processes facing the internet

From an empty server to paying customers.

Install it in a minute.

The installer sets up nginx, PHP, MariaDB and the firewall, then checks its own work. If a stage fails, run the command again and it picks up where it stopped.

How the install works

root@ubuntu-24.04: klyrn install 11 of 11 stages verified in 53 s

$ curl -fsSL https://get.klyrn.com | sudo bash

  ✔ Checking this server
  ✔ Profiling hardware and deriving tuning
  ✔ Preparing the operating system
  ✔ Creating KLYRN user, directories and keys
  ✔ Installing and configuring nginx
  ✔ Installing PHP 8.3 (FPM)
  ✔ Installing and securing MariaDB
  ✔ Configuring the firewall (ufw)
  ✔ Applying kernel network and filesystem limits
  ✔ Starting KLYRN services
  ✔ Verifying the complete installation

  KLYRN is installed and verified.

  Panel:        https://51.75.165.38:7443
  Setup token:  (printed once, on the console)

Bring your sites with you.

KLYRN reads a cPanel or DirectAdmin backup, or connects to the old server over SSH. The old server keeps serving until you change DNS.

AnalyseA plan you read before anything is copied.
CopyFiles, databases, mailboxes and cron jobs.
VerifyA preview of every site on the new server.
Cut overThe exact DNS records to change.

Proven on a production DirectAdmin server with 48 domains and 48 mailboxes.

How migration works

A migration in the panel: three sites coming across, one copying, with the routes to start another.

Run every kind of site.

PHP, WordPress, Node.js, containers and mail, with the same backups, certificates and limits for all of them.

PHP: Any version, chosen per site. PHP
WordPress: Staging, an update policy and a health check. WordPress
Node.js: Deploy from Git and roll back with one command. Node.js
Containers: Any image, locked down by default. Applications
Mail: Mailboxes, DKIM, spam filtering and webmail. Mail

The sites list, grouped by stage, with one status line per site.

Leave it running.

The part of KLYRN that faces the internet has no root access. Every backup is read back before it counts. An update that fails its checks rolls itself back.

How KLYRN is secured