Turkey (Türkçe) 
VDS Operating System Selection Guide
Lets you install FreeBSD, Proxmox, pfSense or hardened images that are not in the standard template list, using your own ISO.
Full control: your own ISO, your own installation process.
At the order step, choose the Custom ISO template.
| Version | User-defined |
|---|---|
| Base | Depends on the ISO |
| Package manager | Depends on the distribution |
| Kernel | Depends on the ISO |
| Architecture | x86_64 |
| Init | Depends on the distribution |
| LTS / support | Depends on the distribution |
| Container | Depends on the ISO |
The recommendations below are for general guidance; actual needs vary with traffic and application architecture.
| Use | Resources | Note |
|---|---|---|
| Firewall (pfSense) | 1–2 vCPU · 1–2 GB RAM | Low traffic |
| Proxmox VE | 4+ vCPU · 8 GB+ RAM | High resources for nested VMs |
| cPanel | ✕ Not supported |
| Plesk | ✕ Not supported |
| DirectAdmin | ✕ Not supported |
| Docker | ◐ Partial / after installation |
| Nginx | ◐ Partial / after installation |
| Apache | ◐ Partial / after installation |
| LiteSpeed | ✕ Not supported |
| CloudLinux | ✕ Not supported |
Custom ISO is the option of installing an operating system from an image you supply yourself. Kernel/base: depends on the ISO. Default components: the SistemDC HTML5 KVM console + ISO mount. In a VDS environment, a Custom ISO server is delivered as a virtual machine with root/Administrator access and IPv4/IPv6 support, installed through the KVM console. The support window depends on the distribution you install. At the KVM hypervisor layer, dedicated vCPUs and NVMe I/O deliver consistent performance without noisy neighbours. On a Custom ISO VDS, the hostname, SSH key and package updates can be automated with cloud-init (if your image supports it) or your own post-install script. For disk I/O, keep the NVMe queue depth high; for PostgreSQL/MySQL the vm.swappiness=10 sysctl setting is recommended. Logrotate and journald prevent the disk from filling up. Monitoring: a lightweight setup with node_exporter + Prometheus or Netdata. If you use containers, after installing Docker/Podman with your distribution's package manager, run containers as non-root and define cgroup v2 limits. SistemDC's Istanbul POP delivers low jitter for traffic within Turkey, without carrier-grade NAT.
Choose Custom ISO if…
Typical use cases for a Custom ISO VDS: FreeBSD, Proxmox VE, pfSense, OPNsense, ClearLinux, custom hardened images. Thanks to the Turkey location, local users get a fast TTFB with 5–15 ms ping domestically. On Ryzen VDS plans, high single-core GHz is preferred for game servers and Discord bot workloads. With SistemDC NVMe disks, random-I/O-heavy database queries see 5–10x lower latency than on an HDD VDS. Under heavy traffic the Stormwall DDoS filter kicks in automatically at the network layer. For CDN origin, reverse proxy caching and static asset delivery, optimise the Nginx/Apache configuration on your image with HTTP/2 and Brotli compression; for users in Turkey, the origin location directly improves the SEO Core Web Vitals LCP score.
When ordering a SistemDC VDS, choose Custom ISO as the template. After the first login, run (your distribution's package update command) to update the packages. Hostname: hostnamectl set-hostname server.yourdomain.com. Time zone: timedatectl set-timezone Europe/Istanbul. Create a new user with sudo privileges and disable root SSH login. Verify the network configuration (netplan/NetworkManager/ifcfg). On low-RAM plans you can add a 1–2 GB swapfile. Installing Fail2ban is recommended.
SSH hardening: /etc/ssh/sshd_config — set PermitRootLogin no, PasswordAuthentication no (use an ED25519 key), with an optional port change. firewalld: firewall-cmd --permanent --add-service=ssh, --add-service=http, --add-service=https, firewall-cmd --reload. Leave SELinux in enforcing mode; use semanage when opening custom ports. Updates: (your distribution's package update command) — automate with a weekly cron. KernelCare (optional) applies kernel patches without a reboot. SistemDC Stormwall network-layer DDoS protection is standard. SSH guide: Linux SSH Security.
A Linux VDS environment has no physical sleep/hibernate mode; the virtual machine is kept running continuously by the hypervisor (N/A). Power management is provided on the server side with 24/7 active uptime; systemd sleep targets are disabled in the server templates.
In the VDS order flow in the SistemDC client area, open the Operating System step and choose the Custom ISO template. For general web/API, choose the Intel Xeon TR-VDS plans; for gaming, bots and high GHz, choose Ryzen VDS. For control panel installation, see our application setup guides for details. Category: VDS plans.
How do I order a Custom ISO VDS?
Choose Custom ISO when ordering a VDS; send the ISO link to the support team.
Installation time?
It depends on the ISO size; it can take 15–60 minutes over the KVM console.
Which ISO formats are supported?
Standard x86_64 bootable ISOs; verify EFI/BIOS compatibility.
How long does installation take?
It depends on the ISO size; a manual installation over the KVM console can take 15–60 minutes.
Is there automatic provisioning with a Custom ISO?
No; cloud-init or an unattended answer file is your responsibility.
Turkey location · Stormwall DDoS · NVMe disk · 99.98% uptime SLA
Rent a Turkey VDSSetup Guides
