SERVICE CAPABILITIES & LIMITS
Know exactly
what you get.
From the first secure login to the final verification, see what SysLauncher prepares, what you can add and what stays in your hands.
Explore the capabilities01FROM FRESH LINUX TO A VERIFIED SERVER
Five stages.
One coherent result.
Every server starts with the essential setup and finishes with a security review. You decide whether it also needs specialist services or backups.
-
P1
Prepare the system
Start with a clean Linux installation, the right packages and settings for the server.
Technical details
OS profile checks, package metadata, updates, hostname, time zone, prerequisites and reboot handling.
-
P2
Protect access and essential settings
Control who can connect, close unnecessary entry points and check that administration still works.
Technical details
SSH key authentication, controlled port migration, sudo/admin access, firewall, root-login restrictions, automatic security updates and final connectivity proof.
-
P4
Put your server to work
Add the web, database or traffic-handling services your project actually needs, with private administration where appropriate.
Technical details
OD Prepare: explicit server role; native or supported container deployment; Nginx, PHP, PostgreSQL and HAProxy profiles; private management endpoint and checked handoff manifests.
-
P3
Make recovery possible
Create scheduled backups of the selected data and prove that a copy can be restored.
Technical details
Backup / Restore: Restic, Borg or Kopia with compatible destinations, snapshots, retention, systemd schedules, isolated restore tests and recorded evidence.
-
P5
Check and document the result
Finish by checking the server's security posture and documenting what was actually achieved.
Technical details
Security Pipeline: applicable CIS controls, Lynis, role-dependent OWASP checks, evidence files and a final report. Always executed last; reports distinguish checks from formal certification.
When you choose both extra services, OD Prepare runs before Backup / Restore so the newly configured services can be included in the backup.
02CHOICES WITHOUT THE GUESSWORK
Just the work
you actually need.
The essentials are never left out. Add an application role, backups, or both. The final checks are part of every combination.
ESSENTIAL
A clean, protected base
For a fresh server that needs a reliable starting configuration.
WITH SERVER ROLE
Ready for an application
For a server that should also run selected web, database or traffic services.
WITH RECOVERY
Prepared and backed up
For a server whose chosen data needs a backup and verified restoration path.
COMPLETE CONFIGURATION
Configured. Backed up. Verified.
For a new server that needs both its working services and a tested backup route.
The pipeline labels show execution order, not separate subscriptions. P1 + P2 and P5 are included in every setup.
03THE JOB YOUR SERVER WILL PERFORM
Different purposes.
The right setup.
A server that hosts a website is not the same as a database or a traffic director. With OD Prepare, the configuration follows the role you choose.
Plain Server
A clean Linux server without an application stack added for you.
Native OS preparation; no automatic web services or local management panel for this role.
Web Server
Host websites and application services on a deliberately configured web stack.
Nginx, version-matched PHP, declared database placement, TLS; native or qualified container-based profiles.
Database Server
Give application data its own dedicated service and controlled connections.
Dedicated native PostgreSQL role, with local or explicitly permitted private-network exposure.
Load Balancer
Distribute incoming traffic among services and check where it can safely go.
HAProxy, health-checked backends, Nginx TLS edge and scoped administration, using supported deployment profiles.
The exact software, deployment method and available role depend on your selected Linux release. Check the compatibility reference for detailed combinations.
04NOT JUST A COPY — A WAY BACK
Backups should
be restorable.
A backup is useful only when you can recover what you need. SysLauncher prepares compatible storage, runs a backup and tests restoration before calling the work complete.
-
01
Choose what matters
Protect the data and settings relevant to your server's role.
-
02
Store a recoverable copy
Use a compatible repository, retention policy and schedule.
-
03
Test the return path
Restore a real snapshot into an isolated location and check the result.
FOR THE TECHNICALLY CURIOUS
Compatible tools and storage
The backup engine and destination are selected as a compatible pair—not mixed at random.
Encryption and versioning are not the same as protection against deletion. Strong anti-ransomware claims require destination-specific access restrictions and verified retention behavior.
05THE DIFFERENCE BETWEEN DONE AND VERIFIED
A command ran.
Did it work?
SysLauncher does not treat a successful command as proof of a correct server. It checks the resulting state, records findings and hands over evidence of the work.
What matters is the server you receive, not the number of commands that ran.
Configuration checked
Verify the intended services, access and settings against the actual server.
Postconditions · State evidence · IdempotencySecurity reviewed
Review applicable security measures and identify what still deserves attention.
CIS-aligned controls · Lynis · Role-specific OWASPResults documented
Receive a verifiable outcome instead of an unexplained success message.
Reports · Execution records · Delivery artifacts06THE BOUNDARIES ARE PART OF THE PROMISE
Clear conditions.
No surprises.
Knowing where the service starts and ends helps you plan confidently—whether you are preparing your own server or delivering servers for customers.
A fresh start is required
SysLauncher prepares newly installed Linux systems. It does not take over an already configured production server or migrate its applications.
Fresh-install contract · Supported OS profile · SSH readinessChoose a supported system
The service targets selected Ubuntu, Debian, AlmaLinux and Rocky Linux releases. Your chosen architecture and role must be compatible.
Ubuntu 22.04 / 24.04 / 26.04 · Debian 12 / 13 · AlmaLinux 9 / 10 · Rocky Linux 8 / 9 / 10 · AMD64 / ARM64One order can cover many servers
Prepare several servers together, with a declared job and settings for each one. Capacity is checked when the order is accepted.
Per-target jobs · Readiness gates · Resource-based admission limitsYour access is handed over
Receive the keys and delivery information needed to administer your server. SysLauncher does not remain as a required management service.
SSH key handoff · Host-key pinning · Client key rotation · No persistent SysLauncher agent↗READY TO TAKE THE NEXT STEP?
Build it once.
Make it yours.
Start with the essential configuration and choose only the services your infrastructure needs.