Managed servers
Hostyrex engineers handle migrations, monitoring, updates, backups, security, and incident response.
Managed service packages
What we can handle
Migrations
We plan the move, test the environment, and switch services with minimal downtime.
Observability
We set up monitoring, alerts, baseline metrics, and clear incident response steps.
Security
Updates, hardening, firewall, backup policies, and access control.
Performance
We inspect bottlenecks across storage, network, databases, and service configuration.
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.
SLAManaged and long-term 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.