1. Service scope
CloudDDR provides dedicated server rentals, priced monthly and billed for the selected term. Each server is powered by an AMD EPYC 7543P processor with 32 cores and 64 threads. The processor, memory and included drives are reserved for the relevant account and are not shared computing resources. Servers are provisioned in Tokyo, Japan.
These terms apply to rental-related processes on the public website, configuration page and account portal. The selected server, add-ons, operating system, billing term and amount due are based on the details displayed before payment is confirmed and the corresponding order record. Availability is based on the status returned by the portal in real time.
CloudDDR is responsible for the supplied hardware and network. Account holders are responsible for the operating system, applications, business content and data. A dedicated server rental does not include system administration or automatic data redundancy or business backups. Further details are set out in Sections 5, 6 and 9.
2. Accounts
The registered email address and account details provided must be accurate and kept up to date so they can receive verification codes, service notices and support ticket updates. Account holders must access the portal through the standard sign-in process and must not register for or use the service under another party's identity.
Account holders are responsible for safeguarding their passwords, email access, server login credentials and any keys they configure. Valid passwords, verification codes, private keys and other sensitive information must not be disclosed on public webpages, public code repositories or in support ticket messages. If credentials are exposed or unexpected activity is detected, the relevant credentials must be changed and the incident reported through a support ticket.
Information associated with account details, orders and support tickets is handled as described in the Privacy Notice. Requests to correct account details or report access issues can be submitted through a support ticket after signing in. If sign-in is not possible, the issue can be reported by email to support@cloudddr.com.
3. Orders & payment
On the configuration page, orders can include a memory tier, additional drives, bandwidth, extra IPv4 addresses, an operating system and a billing term. Before confirming payment, the full configuration, itemised charges and amount due for the current period should be checked. In particular, the Windows licence type and system language should meet the requirements of the intended workload.
All orders are billed in US dollars. Available payment methods are those listed on the configuration page before payment is confirmed. Examples in public materials or methods used for previous payments do not determine the options for a new payment. Payment results, order details and delivery status should be checked in the portal; a redirect page alone does not confirm that the server is ready for connection.
Prices for both server configurations and optional extras are listed on the pricing page. The monthly total shown on the configuration page is used to calculate the amount due for the current period. Charges for extra IPv4 addresses do not include the one address supplied with the server.
4. Billing
The monthly total consists of the server's monthly price, additional drives, bandwidth surcharges, extra IPv4 addresses and any Windows licence. Monthly, quarterly, six-month and annual billing terms cover 1, 3, 6 and 12 months respectively, with no discount. Amount due = monthly total × number of months. There is no setup fee or contract, and longer billing terms are not presented as discounted plans.
Subscriptions renew automatically at the end of the selected term. The renewal amount is calculated by multiplying the current monthly total by the number of months in the billing term. Account holders should check subscription, invoice and expiry details in the portal. If optional services change, billing is based on the invoice shown in the portal.
To stop renting a server, the subscription can be cancelled in the portal. After cancellation, the subscription will not renew when the currently paid term ends. Stopping server use, shutting down business processes or disconnecting a remote session does not cancel a subscription. The cancellation action and subscription status should be checked in the portal.
For billing cycle calculations and cancellation instructions, see the billing guide. Questions about charges, configuration details or subscription status should be submitted in a support ticket with the order information. Account or payment details must not be shared on public pages.
5. Hardware
The available configurations are AMD EPYC 7543P · 128GB and AMD EPYC 7543P · 256GB, both with DDR4-3200 ECC memory. The memory tier cannot be upgraded on an existing server after provisioning. Changing tiers requires ordering another server. Account holders are responsible for data synchronisation, service cutover and backup arrangements when migrating workloads.
Both configurations include 2×1TB NVMe drives, 250 Mbps unmetered bandwidth and 1 dedicated IPv4 address. Each included NVMe drive is directly attached; there is no hardware RAID, and the drives are not supplied as a preconfigured RAID-1 mirror. Optional drives are 2TB NVMe each, with up to two additional drives available. These are also attached independently.
Account holders are responsible for setting up and verifying software RAID, ZFS mirrors, filesystems, snapshots and off-site backups to suit their workloads. A mirror is not a backup. Deletion, overwriting, application errors and system operations can still affect data. Before reinstalling the operating system, initialising a disk or changing the storage layout, account holders should confirm that backups can be restored.
CloudDDR handles hardware and network issues. Account holders are responsible for the operating system and data, including backup integrity and restore testing. If disk detection, memory information or network settings do not match the order, the relevant output should be retained and submitted in a support ticket. Destructive disk operations should be avoided until the issue has been investigated.
6. Software & licences
There are 14 operating systems available at no additional charge: AlmaLinux 8, 9, 10; CentOS Stream 9, 10; Debian 11, 12, 13; Ubuntu Server 22.04, 24.04, 26.04 LTS; FreeBSD 13; and Proxmox VE 8, 9. These operating systems have no additional licensing fee. The selection is confirmed on the configuration page.
Windows Server is available with Standard or Datacenter licensing for versions 2019, 2022 and 2025. Licences are billed monthly, apply for the corresponding subscription term, and are included in the monthly total and the amount due for the selected term. Available system languages are English, Traditional Chinese and Simplified Chinese. The selection made when ordering applies.
Account holders are responsible for operating system updates, access policies, application configuration and data protection after installation. Software, virtualised guests and business components installed by account holders must be properly licensed for their intended use. A preinstalled operating system or server rental does not replace licences for other commercial software.
7. Access
After payment and delivery, sign in to the portal and find the connection address and credentials in the server details. Linux, FreeBSD and Proxmox VE are accessed over SSH; Windows is accessed over RDP. The username, credentials and address shown in the details for the relevant server apply.
If a server has multiple IPv4 addresses, SSH and RDP connections use the first address in the list. Additional addresses are for workload planning and do not change the management address used for the initial connection. Details from another server must not be used to infer the username, password or connection settings for this server.
After the first connection, check the server against the order, change the password or configure keys as required, and set appropriate access controls. Connection steps are provided in the connection guide. If a connection fails, retain the exact error message and report the address and connection method in a support ticket through the portal.
8. Support
Technical, billing, subscription and complaint enquiries must be submitted as support tickets through the signed-in portal. Tickets should be linked to the relevant server or order and describe the issue, the conditions under which it occurred, actions already taken and what needs to be checked. Separate issues affecting different servers should not be combined in one description.
For connection issues, specify whether SSH or RDP was used, the address and the error shown by the client. For hardware or storage issues, include information that can be used to identify the component. For billing questions, include the order and the item in question. Remove passwords, verification codes, private keys and unrelated personal business information from logs and screenshots before sharing them.
Replies and additional information for support tickets are handled in the portal. For account access issues that prevent sign-in, email support@cloudddr.com. Email does not replace verification of account identity, order ownership or permissions for requested actions.
9. Acceptable use
The service must not be used to send spam, conduct network attacks, distribute malicious software, host infringing content or engage in other unlawful or abusive activity. Account holders are responsible for managing applications, virtualised guests and downstream access on their servers. If an intrusion, unusual outbound traffic or attack traffic is detected, appropriate isolation and remediation measures should be taken.
If an abuse complaint is received or such activity is detected, CloudDDR may suspend the affected server or address and notify the account holder through a support ticket. Account holders must assist with identifying the affected workload, retain necessary logs, and provide details of isolation measures, remediation and outcomes. Any action taken will be based on the facts reviewed and the support ticket record.
CloudDDR is responsible for hardware and network issues; account holders are responsible for systems and data. Issues arising from events beyond reasonable control or actions taken by account holders will be addressed in light of their actual impact and the parties' respective responsibilities. Account holders must maintain independent backups and verify recovery plans before making system or data changes.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. Disputes arising from the service should first be raised through a support ticket to discuss the facts and requested resolution. If no agreement can be reached, the dispute will be submitted to a court of competent jurisdiction in that jurisdiction.