Legal

Dedicated Server Terms: Monthly Billing

These terms cover dedicated server rentals, order billing and each party’s responsibilities. Check the server configuration before ordering and plan for system security, data redundancy and backups.

Terms of Service — effective October 14, 2026

On this page

  1. 1. Service Scope
  2. 2. Accounts
  3. 3. Orders & Payment
  4. 4. Billing
  5. 5. Server Specs & Responsibilities
  6. 6. Operating Systems
  7. 7. Access
  8. 8. Support Tickets
  9. 9. Acceptable Use
Console

1. Service Scope

CloudUDP provides monthly rentals of dedicated servers powered by AMD EPYC 7543P processors. Each server is reserved for one customer, with no processor, memory or local storage shared with others. Servers are located in Tokyo, Japan.

Service is based on the server configuration and billing period confirmed in the order. Published pricing explains server models and optional add-ons; current availability is shown in the console. Check the selected model, add-ons and amount due on the configuration page before paying.

The rental includes the server hardware and network resources listed in the order. Customers manage the operating system, application deployment, access controls and business data. See Section 5 for the division of responsibilities.

2. Accounts

The registered email address and account details must be accurate, current and usable for account verification and service-related communications. Update account details promptly when they change. Submit questions about order ownership, invoices or account access through a console support ticket.

Customers are responsible for safeguarding account passwords, verification codes and server login credentials. Do not disclose credentials to unrelated parties or include usable passwords or keys on public pages, in code repositories or in support ticket attachments.

If account or server credentials may have been exposed, update them promptly and use a support ticket to identify the affected server and describe the unusual activity. See thePrivacy Policy for details about how account information is handled.

3. Orders & Payment

Choose a memory tier, number of additional drives, bandwidth tier, extra IPv4 addresses, operating system and billing period on the configuration page, then check out. Before paying, verify the configuration, monthly total, number of months and amount due. There is no setup fee.

All charges are in US dollars (USD). Available payment methods are those listed on the configuration page before payment is confirmed. Payment status is determined by the order and billing records.

Once payment is confirmed, the server enters the provisioning process. When provisioning is complete, the console shows the updated server status and corresponding login credentials. No fixed provisioning time is specified in these terms; seeFrom Order to First Login: Provisioning Guide.

Configure a Dedicated Server

4. Billing

There is no contract, and the minimum billing period is one month. Billing periods are monthly, quarterly, semiannual or annual, covering 1, 3, 6 or 12 months. None includes a discount, and longer periods do not reduce the monthly total.

The monthly total is the sum of the server’s monthly price, additional drives, bandwidth upgrades, extra IPv4 addresses and Windows licenses. Amount due = monthly total × number of months. Unselected paid options are not included. SeeFull Monthly Pricing & Add-on Fees.

Renewals made before expiry use the same billing period and calculation. Expiry, non-renewal and refund requests are handled individually through console support tickets. No fixed refund percentage or calculation formula not listed on this page applies.

5. Server Specs & Responsibilities

Servers use AMD EPYC 7543P processors with 32 cores and 64 threads, and 128GB or 256GB DDR4-3200 ECC memory. The server is provisioned with the memory tier, additional drives, bandwidth tier and number of IPv4 addresses selected in the order. Memory cannot be upgraded on an existing server; changing tiers requires ordering another server.

Standard storage is 2×1TB NVMe drives, each directly attached and operating independently, with no hardware RAID. The combined 2TB capacity does not mean the drives are configured as a RAID-1 mirror. Add 0 to 2 additional 2TB NVMe drives; these are also directly attached and are not part of a hardware array.

Standard networking includes 250 Mbps unmetered bandwidth and 1 dedicated IPv4 address. Choose 1 Gbps or 2 Gbps bandwidth; all three tiers are unmetered. Add up to 255 IPv4 addresses, for a maximum of 256 total, billed individually per month.

CloudUDP is responsible for

  • Server hardware.
  • Data center power and network.
  • Providing the bandwidth tier listed in the order.
  • Allocating the IPv4 addresses listed in the order.

Customers are responsible for

  • Operating system configuration and updates.
  • Application deployment, account security and access controls.
  • Data redundancy, such as software RAID or ZFS mirroring.
  • Off-site backups and recovery plans.

Disk redundancy and off-site backups must be arranged separately; mirroring is not a substitute for backups. Before reinstalling the operating system, changing storage or taking any other action that could overwrite data, customers must make their own backups and verify that the information needed for recovery is available.

6. Operating Systems

14 operating systems are available at no extra charge: AlmaLinux 8, 9 and 10; CentOS Stream 9 and 10; Debian 11, 12 and 13; Ubuntu Server 22.04, 24.04 and 26.04 LTS; FreeBSD 13; and Proxmox VE 8 and 9. The system selected in the order is installed.

Windows Server Standard and Datacenter are available in versions 2019, 2022 and 2025, with English, Traditional Chinese or Simplified Chinese system languages. Standard licensing costs +$25/month and Datacenter licensing costs +$32/month. The monthly license fee is added to the monthly total and included in the amount due for the server’s billing period.

Submit operating system reinstalls and related changes through a console support ticket. When switching to Windows Server, include the monthly license fee in the monthly total. Customers are responsible for backing up data before reinstallation. SeeWindows Server System Information.

7. Access

After delivery, find login credentials in the server details in the console. Connect to Linux, FreeBSD and Proxmox VE using SSH, and to Windows using RDP (Remote Desktop Protocol). Use the login name and initial password shown in the console.

If a server has multiple IPv4 addresses, use the first address for SSH and RDP. Customers can configure the remaining addresses in the operating system or virtualization host. Change the initial password after first login and configure access controls as needed.

Use SSH or RDP for routine server management. See theServer Access Guide for connection steps and first-login checks. For connection issues, submit a support ticket as described in Section 8.

8. Support Tickets

Submit technical and billing requests through a support ticket in the console, including questions about provisioning status, hardware or network issues, additional drives, bandwidth, IPv4 addresses, operating systems, billing and refunds.

Include the server or order ID, a description of the issue, the conditions under which it occurred, troubleshooting already performed and the exact error message. For billing questions, identify the relevant order and payment status. Remove passwords, verification codes, private keys and unrelated personal information from screenshots and logs before submitting them.

If account access is unavailable or contact by email is needed, write tosupport@cloududp.com. Further handling is based on account and order records and support ticket communications. No fixed response time is promised in these terms.

Submit a Support Ticket

9. Acceptable Use

The service must not be used for abuse, including sending spam, launching network attacks, distributing malware or sharing infringing content. Customers are responsible for managing applications, accounts and public-facing services on their servers, and for preventing abuse caused by exposed credentials or insecure configurations.

If abuse is detected, CloudUDP may restrict network access or suspend a server and notify the customer by support ticket. Customers must help investigate affected applications, access logs and configurations, then report the actions taken through a support ticket.

CloudUDP is responsible for hardware and network; customers are responsible for operating systems and data, including backups. For service impacts caused by force majeure or customer actions, the parties will assess the impact and response based on the circumstances, order records and support ticket information.

These terms are governed by the laws of the jurisdiction where the platform operator is based. Service disputes should first be discussed through a support ticket. If they cannot be resolved by agreement, they will be submitted to a court with jurisdiction in that jurisdiction. Updates to these terms will be published on this page with their effective date.