LINUX DISTRIBUTIONS & COMPATIBILITY
Different Linux.
One clear standard.
Choose the Linux system you want to prepare. We'll show you the work SysLauncher performs, in plain language first—with the technical details close at hand.
Explore compatibility01FIND YOUR SYSTEM
Start with the Linux you know.
Every release has its own package tools and settings. Select yours to view the matching preparation path.
We prepare a fresh Linux installation. Existing production systems and migrations are a different kind of work.
Compare all ten Linux releasesSee pipeline coverage and role-dependent differences at a glance.
All four families support core preparation, backups and the final review. Optional server roles depend on the exact Linux release.
Ubuntu
- 22.04 LTS
- 24.04 LTS
- 26.04 LTS
Debian
- 12
- 13
AlmaLinux
- 9
- 10
Rocky Linux
- 8
- 9
- 10
P1 and P2 form the required Baseline, P5 is always included, while P4 and P3 depend on your selections.
02FROM INSTALL TO HANDOFF
What happens to your server.
Five carefully ordered stages. The essential setup and final review are always included. Server roles and backup are added when requested.
- P1Prepare
- P2Harden
- P4Server roleOPTIONAL
- P3BackupOPTIONAL
- P5Verify
01P1First, know the system.We check the new installation before changing anything, so the configuration matches the actual server.INCLUDED
Check the starting point
Confirm the Linux version, processor type, disk space and remote access before work begins.
Technical details
OS fingerprint, CPU architecture, storage probes, SSH reachability and read-only readiness checks.
Choose the correct preparation method
Use settings and packages appropriate to this exact Linux release—not a generic script.
Technical details
Version-specific OS module, apt or dnf package management, validated execution plan.
02P2Make the foundation dependable.Prepare access, updates and essential protection with checks that confirm the changes really took effect.INCLUDED
Bring the system up to date
Install appropriate system updates and configure the server's essential services.
Technical details
Package updates, time zone and host identity, unattended security updates and verified service state.
Protect administrative access
Create a safer way to connect and confirm it works before closing the original access path.
Technical details
SSH keys, named sudo administrator, custom SSH port, staged reconnection, root SSH restrictions.
Reduce unnecessary exposure
Allow only the required network access and add protection against repeated login attempts.
Technical details
UFW or firewalld rules, Fail2ban and security-oriented service configuration.
03P4Give the server a purpose.When ordered, configure the software for the work the server will actually do.OPTIONAL
Available roles depend on the selected Linux release.
Host websites and applications
Set up the web services required to publish a website or application.
Technical details
Nginx, release-compatible PHP, TLS certificates and selected application components.
Run a database service
Prepare a dedicated place for application data, with appropriate access restrictions.
Technical details
Native PostgreSQL role, configuration, service checks and limited network exposure.
Distribute incoming traffic
Direct requests across application servers when the infrastructure needs a load balancer.
Technical details
HAProxy, compatible deployment mode and TLS termination where configured.
Keep a clean, general-purpose server
Prepare the server without installing a web stack or unnecessary application services.
Technical details
Plain Server native profile with verified baseline and explicit ownership of installed components.
Configure a compatible server role
The selected Linux release determines which server functions and software combinations can be prepared.
Technical details
Per-release role catalog, dependencies and validated configuration plan.
Keep administration private
When requested, access the local management panel through a protected private connection—not the public website.
Technical details
Private interface, SSH tunnel and TOTP authentication via compatible authenticator applications.
04P3Prepare for the unexpected.When ordered, configure backups and check that the saved data can actually be recovered.OPTIONAL
Save what matters
Create protected backups in a compatible storage location, with an appropriate schedule.
Technical details
Restic, Borg or Kopia, encrypted repositories, retention and scheduled jobs.
Verify that recovery works
Test restoring the backup instead of relying only on a successful backup message.
Technical details
Isolated restore of the exact snapshot, content checks and recovery evidence.
05P5Finish with proof, not promises.Check the final configuration and deliver a clear record of what was completed.INCLUDED
Review the security settings
Check the protections that apply to this server and report the actual findings.
Technical details
CIS-aligned applicable checks, Lynis findings and role-dependent OWASP review.
Hand over a verifiable result
Receive the connection information and reports needed to take control of your server.
Technical details
Final state verification, reports, SSH handoff artifacts and execution evidence.
03THE IMPORTANT DETAILS
A clear fit. No guesswork.
Compatibility is more than an operating-system name. These are the conditions that make the result dependable.
A fresh start
SysLauncher prepares newly installed Linux servers, not existing production systems or migrations.
Fresh-install requirementThe right combination
Server software and optional roles must match the selected Linux version and architecture.
Role-specific compatibilityA checked finish
The setup is verified before it is handed over. A command completing is not enough.
Observed final state04EXPLORE FURTHER
Your system. Your next step.
Now that you know what can be prepared, explore service details or see the cost of your chosen setup.