Virtual server options for development environments, web applications and custom services. Compare Istanbul and New York locations based on your resource and traffic needs.
Current order options open in the client panel. Compare Istanbul and New York configurations by location.
Monthly amounts are shown; the final total, including term, taxes, licenses and additional services, is determined on the order screen.
Plan names use the term VDS. vCPU count does not mean physical core allocation; verify before ordering if you need specific allocation or isolation.
Monthly prices are based on product information in the client panel. The final total, including term, taxes, licenses and additional services, appears on the order screen. Panel catalog checked: (Türkiye time).
| Plan | vCPU / RAM | Storage | Traffic / Port | Monthly price |
|---|---|---|---|---|
| Istanbul VDS 1For getting started and development environments. | 1 core1 GB DDR4 | 20 GB NVMe SSD | 2TB2x25 Gbit | ₺125.55/ month Order options |
| Istanbul VDS 2For getting started and development environments. | 1 core2 GB DDR4 | 40 GB NVMe SSD | 3TB2x25 Gbit | ₺188.55/ month Order options |
| Istanbul VDS 3For web applications and growing workloads.A balanced choice | 2 cores2 GB DDR4 | 50 GB NVMe SSD | 4TB2x25 Gbit | ₺251.55/ month Order options |
| Istanbul VDS 4For web applications and growing workloads. | 3 cores3 GB DDR4 | 70 GB NVMe SSD | 4TB2x25 Gbit | ₺377.55/ month Order options |
| Istanbul VDS 5For web applications and growing workloads. | 4 cores4 GB DDR4 | 80 GB NVMe SSD | 4TB2x25 Gbit | ₺440.55/ month Order options |
| Istanbul VDS 6For more memory and processing resources. | 6 cores8 GB DDR4 | 160 GB NVMe SSD | 5TB2x25 Gbit | ₺755.55/ month Order options |
| Istanbul VDS 7For more memory and processing resources. | 8 cores10 GB DDR4 | 200 GB NVMe SSD | 5TB2x25 Gbit | ₺881.55/ month Order options |
| Istanbul VDS 8For more memory and processing resources. | 10 cores12 GB DDR4 | 240 GB NVMe SSD | 6TB2x25 Gbit | ₺1,007.55/ month Order options |
| Plan | vCPU / RAM | Storage | Traffic / Port | Monthly price |
|---|---|---|---|---|
| New York VDS 1For getting started and development environments. | 1 core2 GB DDR4 | 40 GB NVMe SSD | Unlimited10 Gbit | ₺125.55/ month Order options |
| New York VDS 2For getting started and development environments. | 2 cores3 GB DDR4 | 50 GB NVMe SSD | Unlimited10 Gbit | ₺188.55/ month Order options |
| New York VDS 3For web applications and growing workloads.A balanced choice | 3 cores4 GB DDR4 | 60 GB NVMe SSD | Unlimited10 Gbit | ₺251.55/ month Order options |
| New York VDS 4For web applications and growing workloads. | 4 cores6 GB DDR4 | 70 GB NVMe SSD | Unlimited10 Gbit | ₺377.55/ month Order options |
| New York VDS 5For web applications and growing workloads. | 6 cores8 GB DDR4 | 80 GB NVMe SSD | Unlimited10 Gbit | ₺440.55/ month Order options |
| New York VDS 6For more memory and processing resources. | 12 cores16 GB DDR4 | 160 GB NVMe SSD | Unlimited10 Gbit | ₺755.55/ month Order options |
| New York VDS 7For more memory and processing resources. | 16 cores20 GB DDR4 | 200 GB NVMe SSD | Unlimited10 Gbit | ₺881.55/ month Order options |
| New York VDS 8For more memory and processing resources. | 20 cores24 GB DDR4 | 240 GB NVMe SSD | Unlimited10 Gbit | ₺1,007.55/ month Order options |
Traffic values represent plan allowances. Unlimited traffic in New York plans does not mean unlimited processing capacity or a fixed speed guarantee on every connection. Check port, overage and fair-use conditions before ordering.
Operating system and additional license options are determined during ordering.
Inside the platform
vCPU indicates the virtual processor count; RAM indicates the memory your application can use. Virtualization and physical core allocation are different concepts. Match specific isolation requirements to technical scope, not product names.
Applications, databases, system files and logs must all fit on the plan’s disk. Leave space for updates and temporary files; plan archive and backup locations separately.
Istanbul plans list traffic between 2 TB and 6 TB and 2 × 25 Gbit ports. Connection capacity is not a guaranteed end-to-end speed for every client or request.
New York plans list unlimited traffic and a 10 Gbit port. Assess fair-use conditions, latency and the locations of other services your application depends on together when choosing.
At initial setup, plan controlled access using SSH keys and required ports. Separate the administrator account from everyday application tasks, and run services with the permissions they need.
Monitor disk usage, memory and CPU consumption during peak hours. A single copy inside the server is not an independent backup; verify restore steps in a separate environment.
Even with sufficient resources, your application’s IP, network and runtime requirements determine the setup. Add the following areas to your technical requirements list; verify availability and fee scope for your selected product.
| Requirement | Information to define | Why does it matter? |
|---|---|---|
| IPv4 / IPv6 | Public or private addresses, IP count and use of both protocols together. | An IPv6-only environment cannot directly serve all IPv4-only clients. Plan DNS and firewall rules for each protocol. |
| Ports and external services | Incoming/outgoing connections, VPN or private network needs and API access lists. | The application port, administrator access and IP address allowed by the external service must work together. |
| Email sending | Outbound SMTP conditions, PTR record management and the email service to use. | A PTR is a reverse DNS record; it does not guarantee delivery alone. SPF, DKIM, DMARC and sender reputation are also assessed. |
| Container / virtual machine | Kernel, CPU architecture and nested virtualization support if required. | Running a Docker container and a virtual machine inside Proxmox/Hyper-V have different requirements; the standard VPS label does not guarantee compatibility. |
If operating business email is not your project’s core task, also consider the business hosting scope. You can add specific connection or application dependencies to the VPS requirements form.
The starting points below are not capacity limits. Match your application’s real tasks to system usage during the same interval.
| Workload | First measurement | Check together |
|---|---|---|
| Web application | Response time, concurrent processing, CPU and memory usage. | Distinguish cache status from waits for external API/payment services. |
| Job queue / data transfer | Pending jobs, completion time and resource usage of running processes. | Task frequency, retries and required runtime. |
| Database | Heavy query durations, active data size and disk wait. | Distinguish index/lock issues from memory or storage needs. |
If standard panel management is sufficient, narrow down the service type with the hosting–VPS comparison. If you have access issues, first distinguish DNS, TLS and application layers; not every error means insufficient resources.
A virtual server lets you control your application’s runtime environment. Assigning responsibility for operating system and application maintenance matters as much as choosing resources.
Create your security plan
When choosing between Istanbul and New York, consider connected services such as APIs, payment infrastructure and databases alongside your audience. Frequent data exchanges between distant regions can affect response times.
Measure the connection from your own network and test with real application tasks. Ping alone does not explain page performance; application code, databases and file sizes also affect the result.
Open the connection testServer management
Assign a team to operating system, application and backup tasks. If additional management service is needed, define its scope separately.
| Management area | Your technical team’s plan | Scope to clarify for additional service |
|---|---|---|
| Operating system | Post-installation accounts, firewall and updates. | Supported versions, maintenance schedule and reboot approval. |
| Web and database services | Service settings, application dependencies and error monitoring. | Which services will be managed and the scope covering application code. |
| Security | SSH keys, least privilege and opening required ports. | WAF, monitoring, security incidents and intervention boundaries. |
| Backups | File and database copies outside the server. | Backup frequency, retention, storage and restore tests. |
| Licenses | Tracking operating system and control panel licenses. | Product, user/core licensing criteria, renewal and total fee. |
Operating system and panel
Match Ubuntu, Debian, AlmaLinux, Rocky Linux and Windows options to your software requirements. Available versions and installation images are verified during ordering.
It suits developers and technical teams that want to install custom software, run services or control the operating system. If you only want to manage a website and email, hosting may be a simpler starting point.
Providers may use these terms differently. The key factors to assess are virtualization architecture, vCPU allocation, memory limits, disk and usage conditions. A product name alone should not be taken as a physical-core guarantee.
License scope depends on the selected operating system and product configuration. Check fees for Windows, cPanel, Plesk or other paid software separately on the order screen and in the written scope.
Server resources, system administration, application maintenance and backup services have separate scopes. The management level, backup frequency and restore responsibilities you need are defined before ordering.
Assess your users’ region, the services your application depends on and requirements for the country where data will be stored together. Since latency depends on the connection route, measuring from your own network is useful.
A snapshot captures a system’s state at a particular moment for rollback. A snapshot kept on the same infrastructure does not replace an independent backup; application/database consistency matters too. Verify separately whether snapshots are offered; define retention and restore methods for the off-server copy in your backup plan.
Resource increases are planned based on availability, virtualization architecture and disk layout. Do not assume every upgrade can be completed without downtime. Compatibility, backups, any reboot and the price difference are clarified first.
FROM SELECTION TO SETUP
Share your software, operating system and resource needs; let’s choose a suitable configuration together.
