INFRASTRUCTURE WITHOUT LOCK-IN

Your provider.
Your choice.

SysLauncher prepares your fresh Linux server wherever you choose to host it. You stay with the infrastructure provider you trust — and choose where your backups live.

Explore providers
HOSTING IS YOUR DECISIONTHE HANDOFF IS INDEPENDENT

01SERVER INFRASTRUCTURE

Your server can live
where you want.

Choose a provider for your virtual machine or dedicated server. SysLauncher works with the server through SSH, not through an exclusive hosting partnership.

The provider is not the limitation.

What matters is a supported fresh Linux installation, SSH access, enough resources and permission to make the requested system changes.

Infrastructure directory

Examples of providers and platforms suitable for consideration.

Cloud & virtual machines

VPS & dedicated

These names are examples, not a list of official partners or a promise that every product, region or image is compatible. Eligibility depends on the actual server configuration.

Your own servers belong here, too.

Dedicated hardware in a private datacenter or a self-managed environment can qualify under the same fresh-Linux and SSH requirements.

02BACKUP DESTINATIONS

Your backups.
Your destination.

Backups are most useful when a copy lives away from the server. Choose a destination that suits your data and the way you want to recover it.

  1. 01Server data
  2. 02Backup engine
  3. 03Remote storage
  4. 04Restore check

Storage providers & services

Each provider below is paired with a corresponding backup engine and connection method.

Kopia · S3 API

Hetzner Object Storage

Object storage reached through an S3-compatible connection.

Provider documentation

A BACKUP THAT CAN BE RESTORED

Storage alone is not protection.

SysLauncher verifies a restoration from the selected backup. Protection against deletion or ransomware additionally depends on destination permissions, retention rules and features such as append-only storage or Object Lock.

Backup capabilities

03BEFORE YOU BEGIN

A few things matter.
The rest is flexible.

A familiar provider name is less important than meeting the conditions of the setup you choose.

01

Start with a fresh Linux installation

SysLauncher prepares new servers. It does not take over a server already configured by another control panel.

Technical: supported distribution, version and CPU architecture.
02

Allow secure initial access

The setup needs administrator access to prepare the system and verify the finished result.

Technical: SSH, initial root access, privileges and network reachability.
03

Choose a suitable backup destination

If you request backups, their destination must support the selected engine and the desired protection.

Technical: SFTP/SSH or compatible S3 API; credentials and retention policy.
04

Keep control after handoff

The configured server continues on your infrastructure. You manage the hosting and backup service accounts.

Technical: no permanent SysLauncher management agent or provider account ownership.

YOUR INFRASTRUCTURE. YOUR CHOICE.

Ready to choose your setup?

Explore the Linux versions and service options before you decide.

Explore pricing Service capabilities