Dedicated servers
Baremetal for projects that need guaranteed resources, fast storage, stable networking, and hardware-level access.
Servers by workload
What is confirmed before payment
| Item | What we confirm | Why it matters |
|---|---|---|
| Availability and delivery | configuration and delivery date | GPU and rare configurations are checked for availability first |
| Network | port, traffic, included IP, DDoS profile | traffic limits and abuse rules are clear before launch |
| Hardware | IPMI/KVM, RAID, drives, component replacement | long-term hosting needs a clear recovery process |
| Billing | monthly payment | the project can renew month by month |
What matters for multi-month hosting
Monthly billing
Monthly payment is available. Multi-month prepayment is optional, not required.
Migration plan
Before moving, we check the stack, DNS TTL, database, backup, cutover window, and rollback path.
Hardware replacement
For baremetal, disk replacement, RAM/CPU diagnostics, IPMI access, and remote-hands flow are agreed in advance.
Clear responsibility
Infrastructure, OS, application, backups, and managed work are separated clearly so incidents have no hidden scope.
What to verify before ordering
Test IP and speedtest
For a location, request a test IP, speedtest file, and route check to your region before payment.
Request testDDoS and filtering
Before ordering, clarify the traffic profile: TCP/UDP, game ports, VPN/proxy, L3/L4, and application needs.
Network termsASN, BGP, ROA
For IPv4/BGP tasks, we verify origin ASN, ROA/RPKI, route objects, LOA, and abuse contacts.
IPv4 subnetsTraffic and port
Plans show port and traffic terms clearly: unmetered VPS traffic or a stated server traffic package.
View serversWhen baremetal fits
Sustained high load
Projects with predictable traffic, CPU-bound tasks, and strict performance requirements.
PostgreSQL, MySQL, ClickHouse
NVMe, RAM, RAID, and dedicated networking help keep latency under control.
Game servers and voice
Low latency, stable CPU, and network attack protection for game services.
AI, render, media
GPU servers for CUDA, inference, rendering, video processing, and batch workloads.
What to check for GPU servers
VRAM and model
Exact GPU model, VRAM, number of cards, and configuration availability are confirmed before payment.
CPU and PCIe
Multi-GPU workloads depend on CPU, PCIe generation, memory, scratch disk, and network port.
Drivers and CUDA
Driver, CUDA, OS, and image versions are agreed before launch, especially for ML and rendering.
Load and cooling
Long-running GPU jobs require checking power, cooling, and sustained-load constraints.
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.
SLAServer questions
When do I need a dedicated server instead of VPS?
Choose dedicated hardware when you need guaranteed CPU, stable I/O, large RAM, RAID/IPMI, GPU, or sustained load without neighbors. If a VPS hits disk or CPU limits, baremetal is often more predictable and cost-effective.
How should I choose CPU for databases, games, or high-load?
Databases need cores, RAM, and NVMe; game servers often need higher single-core frequency; high-load sizing depends on whether the workload is CPU-bound, I/O-bound, or network-heavy.
What should I confirm before ordering a GPU server?
GPU model, VRAM, CUDA/drivers, CPU, RAM, NVMe scratch storage, network port, traffic, and load duration. Multi-GPU servers also require checking power, cooling, and configuration availability.
Can I add IPs, disks, or a faster port?
IPs, disks, and network ports depend on the location and chassis. Specify requirements before ordering: IPv4 count, RAID/ZFS, NVMe/SATA, 1/10/25/40/50/100 Gbit/s, and monthly traffic.
How does migration to a dedicated server work?
We first document the current stack, data volume, and switching window. Then the server is provisioned, data is copied, services are tested, changes are synced, and DNS or IP routing is switched.
Long-term server hosting
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.