Where your server sits, how your resources are allocated and what you can verify yourself. We publish no figure we cannot back in writing — and we say plainly what is not yet confirmed.
Every item states its basis. Where something is not yet confirmed we publish no figure — we give you the command to measure it on your own server instead.
Services are hosted in Istanbul, Türkiye. Site and panel traffic is routed through Cloudflare, where TLS terminates.
Being close to your users keeps latency low and your data stays in the country. Assigned IPs and ports are visible in the panel.
Basis: The data centre location comes from the same source used in our contracts and contact page; the Cloudflare integration is managed from the panel.
Site and panel traffic passes through Cloudflare, where requests are filtered and TLS terminates.
Malicious request floods aimed at the web interface and panel are filtered before they reach you, with no configuration on your side.
Basis: Whether the provider applies L3/L4 filtering to game ports has not yet been confirmed in writing. Until it is, no capacity (Tbps) or layer claim is published here.
The disk figure on your plan is applied to the container verbatim. The quota is defined at container level, not handed out from a shared pool.
No neighbouring service can consume your space. You watch usage live in the panel and upgrade from the same screen when you approach the limit.
Basis: We do not publish a disk type or IOPS figure here because the fleet-wide storage technology has not been verified. Only the top database plan states NVMe in the catalogue.
Every service runs in its own container with its own CPU and memory limits. If a service exceeds its quota, the audit routine reapplies the limit.
Load from another server on the same machine does not spill into your performance. The figure on the order screen is the figure your server runs with.
Basis: Each node's capacity is tracked separately and plans are defined against it; we do not sell beyond capacity. We do not publish a CPU model here because node hardware is not readable from the panel.
Plans define no separate monthly traffic quota; the only limits on the price list are CPU, RAM and disk.
You will not face an unexpected traffic bill at the end of the month. Your cost is the amount shown at checkout.
Basis: No plan in the catalogue defines a traffic quota field. We publish no throughput figure here because node uplink capacity has not been confirmed by the provider.
Provisioning starts on its own once payment completes; there is no admin approval queue. Environment templates are kept ready, so setup does not re-download packages each time.
Your server arrives ready in the panel: open the console and start uploading files right away.
Basis: The provisioning flow is invoked directly when an order completes; there is no manual step.
Guarantee: If provisioning fails, the charge is refunded. This is not a marketing line: failed records are closed with a refund marker and the accounting trail is preserved.
