Terms of Service

Registering an account or paying an invoice accepts the account, billing and use limits below.

  1. Scope

    These terms govern the dedicated server rental that OVN Cloud provides at ovncloud.com. Registering an account, placing an order or completing a payment accepts the specifications and prices shown on the pages at that moment, together with these terms.

    What is delivered is one physical machine with the chosen system installed, plus the orders, invoices and tickets held in the console. Cities, billing terms, systems and add-ons that the pages do not list fall outside this agreement.

    Support is reached at support@ovncloud.com. Tickets handle power, system and address matters on existing orders; they do not extend commitments beyond what is written here.

  2. Account

    An account is identified by its email address, one address to one account. A password set at registration is at least 6 characters. Sign-in codes and password resets are sent to that same address, and the code email carries nothing but the code.

    A signed-in account can view paid orders, file and answer tickets, and read paid invoices. While signed out, the console, tickets and invoices do not open. The public configuration page can still reach checkout without signing in.

    Keeping the password safe rests with the account holder, as does responsibility for the orders, tickets and payments made under that account. Changing the email address restarts from the sign-in step and has no separate entrance inside the console.

  3. Ordering and payment

    Orders are completed on the configuration page: memory tier first, then added disks, bandwidth, extra IPv4, system and billing term. Before payment is confirmed, the payment method is picked from the gateways listed at that moment.

    Checkout produces an invoice, and the chosen gateway handles the payment. Once payment completes, the order enters the console. Unpaid orders stay out of the machine list, and unpaid invoices stay out of the invoice list.

    The console offers no payment methods and starts no payment from the invoice page.

  4. Billing

    Monthly rent is the rent of the memory tier plus added disks, the bandwidth step, extra IPv4 and any system surcharge. The amount due is that rent times the months in the term: 1 for monthly, 3 for quarterly, 6 for semiannual, 12 for annual. No term carries a discount.

    Add-ons are prepaid on the same term as the machine. There is no setup fee. The currency is USD, written with $. 128GB and 256GB are two memory tiers at different rents. Each amount follows the figure shown on the configuration page at the time, and no flat price is fixed here instead.

    Console invoices list paid records only, with short title, number, term, amount and payment date. An invoice leads back to its machine. Within a prepaid term, machine details show status and expiry date.

  5. Machine and specification

    One tenant holds one machine. The processor is an AMD EPYC 7543P with 32 cores and 64 threads. The two tiers differ only in memory, which is DDR4-3200 ECC RDIMM and cannot be added after the order. A 256GB machine has to be chosen as that tier at checkout.

    Default storage is 2×1TB NVMe, each disk direct-attached, with no hardware RAID. Usable capacity is the sum of the two, so 2TB. Added 2TB NVMe disks, up to two, are direct-attached in the same way; they never join a hardware array and never merge into the default pair.

    One IPv4 is included. Further addresses are counted one at a time, up to 255 more and 256 in total. Bandwidth defaults to 250 Mbps, with 1 Gbps or 2 Gbps available, all unmetered. Machines are deployed in Tokyo, Japan.

  6. System

    One system is selected at checkout. Free images cover the AlmaLinux, CentOS Stream, Debian, Ubuntu, FreeBSD and Proxmox VE versions listed on the pages, with Ubuntu 24.04 as the default. Distributions absent from the configuration page are not provided.

    Windows Server Standard and Datacenter carry a monthly surcharge, and the language is fixed at checkout as English, 繁體中文 or 简体中文. The system choice fixes the access method with it, and the console does not convert that into a different form of delivery.

  7. Access

    Linux is reached over SSH. Windows Server is reached over RDP. Until the order status becomes connectable, the console shows status, order number, facility and expiry date only, without address or password.

    Once connectable, addresses are split out of the delivery record, de-duplicated and placed in a scrollable list with the total stated. The list filters, copies one line at a time, and copies every line when there is more than one. SSH and RDP use the first address in that list.

    The password sits beside the first address, masked with dots by default, revealable and copyable. Public pages do not present the in-browser graphical session as an access method.

  8. Tickets

    Power, system and address matters are filed in the console with a subject and a description. Replies and later notes stay on the same ticket, which can also be closed. Filing requires a signed-in account.

    Tickets do not change the memory tier, disk count, bandwidth, address count, system or billing term of a paid order. Changing any of those calls for a new order at the new configuration.

  9. Use limits

    A machine may not be used for unlawful purposes, may not disturb other equipment in the facility, and may not be used to reach addresses, disks or accounts outside its own order.

    Direct-attached disks are partitioned and mounted by the tenant. The service provides no hardware RAID and builds no array across disks in advance. Striping, mirroring and backup at the software layer are arranged by the tenant.

    Provisioning times, availability ratios and refund formulas that the pages do not state form no part of these terms. Add-ons absent from the configuration page cannot be appended to paid content through a ticket.