High-traffic servers for services that are not light

What is a high-traffic server?

Every virtual server comes with a monthly traffic allowance: the amount of data in and out it may use each period. For a small website or a bot this number rarely matters. Some services move tens or hundreds of gigabytes, sometimes terabytes, every month: file delivery, busy APIs, popular shops, backups of large data and media services. For those you need a plan with a big allowance.

The recommended plans on this page are picked from the catalogue's plans with the largest traffic allowances; a plan with unlimited traffic, if one is listed, comes first. What you see on each plan's card is that plan's real allowance.

The allowance is not the only number

Besides volume, a few things matter. Port speed decides how fast data leaves; with a slow port a big allowance is useless. Location decides how quickly your users reach the data. And how traffic is counted, whether only outbound or inbound too, may differ between plans.

So read each plan's specification fully before buying, and ask support if you have a question.

Know your usage

Estimate traffic from the number of users and the size of each response. If each user downloads a few megabytes a month and you have a thousand users, you need a few dozen gigabytes. This simple sum prevents surprises.

If the allowance runs out

Even with careful planning, traffic sometimes exceeds the forecast; a viral link or a successful campaign is enough. You do not have to change plans then. You can buy an extra traffic package and the service carries on without a pause. You see live usage in the Telegram bot and the web panel and get warnings before you reach the limit, so you do not find out late.

Server and traffic package are both billed from the same wallet, which keeps management simple.

Which services is it for?

Any service that sends more than it receives benefits from high traffic.

File delivery and downloads

If you publish large files, look at the download server, which focuses on disk space.

Busy APIs and web apps

APIs that answer millions of requests a day, even with small responses, add up to serious traffic over a month.

Backups and sync

Regularly moving backups from several servers to one place also produces a lot of traffic.

Growing without rework

A service that grows needs more resources too: CPU, RAM and disk. On many plans you can upgrade without rebuilding the server, so the service stays up. To protect a popular service, CloudSnap DDoS protection is on its way. For tests and development use the developer server.

To begin, see the full list of plans or build a server straight from the Telegram bot. You can also start small on a cloud server and grow.

Choosing the right plan

First write down your real or estimated monthly usage. Then pick a plan whose allowance is at least one and a half times that, so peaks have room. Look at location next: the server should sit near most of your users. Finally compare prices, but compare the price per gigabyte of traffic rather than only the plan's total; sometimes a bigger plan costs less per gigabyte. After launch, watch usage for two weeks. If the allowance stays half empty, go smaller; if it nears the ceiling, go bigger or add a package.