Hosting terms
Key terms to review before VPS, dedicated server, GPU, IP network, or managed support hosting.
Monthly hosting
| Topic | Term | Before payment |
|---|---|---|
| Payment period | monthly payment is available | the service can be paid month by month |
| Renewal | service renews by the selected monthly period | check renewal date and payment window |
| Prepayment | multiple months can be prepaid voluntarily | confirm discount or price lock by ticket |
| Cancellation | cancellation depends on the service and paid period | check terms before prepayment |
SLA and incidents
| Area | Covered | Exceptions |
|---|---|---|
| Network | location availability, routing, baseline L3/L4 DDoS | application-layer attacks and service misconfiguration |
| VPS | node, virtualization, network, and panel operation | OS, application, and customer actions |
| Baremetal | hardware, port, IPMI, diagnostics, and component replacement | data without ordered backup/RAID |
| Managed | plan response, monitoring, hardening, backup policy | application development and business logic |
Network, DDoS, and traffic
| Item | How it is confirmed | Why it matters |
|---|---|---|
| Port | 1/10/25/40/50/100 Gbit/s or Mbps in the plan card | this is not always guaranteed full-rate bandwidth for every workload |
| Traffic | unmetered or monthly limit in the card | long-term projects need a clear limit |
| DDoS | TCP/UDP profile, game ports, VPN/proxy, L3/L4 | filtering depends on traffic type |
| Network test | test IP, speedtest, and route by request | verify before payment |
Payment and documents
| Item | How it works | Who needs it |
|---|---|---|
| Invoice | invoice and payment due date are generated in the client area or through sales | B2B and recurring payments |
| Documents | terms, company details, and offer documents are requested before payment | companies and accounting workflows |
| Payment methods | available methods depend on account and service | customers with recurring payments |
| Taxes | tax details are confirmed by billing entity | legal entities |
Allowed use
| Scenario | Before ordering | Comment |
|---|---|---|
| VPN/proxy | allowed; describe purpose, geography, IP volume, and abuse process | IP-pool terms are agreed in advance |
| Torrents | allowed; specify traffic profile, port, and expected load | traffic limits, abuse handling, and location rules matter |
| Blockchain nodes | allowed; describe network, storage, CPU/RAM, and uptime needs | suitable for full/archive nodes and validators by agreement |
| confirm RDNS, limits, and reputation requirements | unsolicited bulk mail is not suitable without agreement | |
| BGP/IP | check LOA, ROA/RPKI, route objects, and contacts | especially for large leases and prefix announcements |
| GPU/AI | describe load duration, drivers, CUDA, and data storage | sustained load requires configuration confirmation |
Legal, billing, and support
Documents before payment
Request an invoice, company details, offer terms, and renewal rules before ordering if accounting needs them.
Billing termsPayments and invoices
Orders, invoices, tickets, and service history are managed through the client area; commercial questions go to sales.
ContactsAbuse and allowed use
For torrents, VPN/proxy, blockchain nodes, mail, BGP, and IP pools, abuse conditions and documents are agreed in advance.
Abuse policyEscalation
Critical incidents are handled through tickets with priority, service linkage, and clear response time.
SLATerms questions
Can the price be fixed for 6-12 months?
Yes. Monthly payment is available by default, and 6-12 month prepayment, discounts, and price-lock terms can be agreed in an invoice or ticket.
What happens if hardware fails?
A ticket is opened, IPMI/SMART/logs are checked, then disk, RAM, node replacement, or migration is coordinated. Critical projects should use RAID, backup, and managed support from the start.
Can resources be upgraded without migration?
VPS upgrades are usually available by moving to a larger plan. Baremetal upgrades depend on chassis, slots, drives, and available hardware, so growth should be discussed before ordering.
Who is responsible for backups?
By default, the customer is responsible for application data. Controlled backup/restore is available as a separate option or managed service.
Can the network be checked before payment?
Yes. Request a test IP, speedtest, and route check for the target location. DDoS-sensitive workloads should describe protocols and traffic profile in advance.