1. Service scope
CloudSFP rents AMD EPYC 7543P dedicated physical servers on a monthly basis. Each processor has 32 cores and 64 threads. DDR4-3200 ECC memory is available in two capacities: 128GB and 256GB. Each server is assigned to one customer; its CPU, memory and drives are not shared with other customers. The data center is in Tokyo, Japan.
These terms apply to orders placed through the site, account management, server delivery and ongoing service. The memory configuration, drives, bandwidth, IPv4 addresses, operating system and billing period for each order are those confirmed on the configuration page and recorded in the order. Current availability is determined by the status shown in the console.
CloudSFP is responsible for server hardware, data center power and network, upstream bandwidth, IPv4 allocation and replacement of faulty hardware. Customers are responsible for the operating system, applications, account and key management, data redundancy and backups. Hardware service does not include managed operations or data backup services.
2. Accounts
When registering and using an account, customers must provide accurate, valid email addresses and account details, and keep their contact information current. Delivery, billing and support-ticket notifications rely on the contact details on the account. When those details change, they must be updated in the console or corrected by submitting a support ticket.
Customers are responsible for keeping account passwords, email verification codes, server login passwords and keys secure. Verification codes and passwords must not be shared with unauthorized individuals. Sessions on shared computers should be logged out of when use is complete. When access is granted to team members, credential security and access removal when roles change must also be managed.
If an account is accessed unexpectedly, an email account is compromised or credentials are exposed, the affected credentials should be changed promptly and the incident reported through a console support ticket. If account access is unavailable, contact support@cloudsfp.com with the account email address and relevant order details. Passwords, verification codes and private keys must not be included in emails or support tickets.
3. Orders & payment
On the configuration page, customers select a server, additional drives, bandwidth, extra IPv4 addresses, an operating system and a billing period. When selecting Windows Server, the licensed edition and system language must also be confirmed. Before payment, review each part of the configuration summary, all charges and the amount due for the current period.
All orders are billed in US dollars (USD). Payment methods are those listed on the configuration page. Available options, as returned by the payment interface, are shown before payment is confirmed. Payment completion and the corresponding order status are verified against the order record and payment result; a payment screenshot alone is not sufficient.
After payment, retain the order number and check the account email and console for delivery information. If there are questions about payment status, configuration details or delivery, include the order number and a description of the issue in a support ticket. Avoid submitting duplicate information that cannot be matched to the original order.
4. Billing
Service is billed monthly and can be paid monthly, quarterly, semi-annually or annually, covering 1, 3, 6 or 12 months respectively. All billing periods have no discounts, no setup fee and no contract. Choosing a longer period only changes the number of months covered by the current payment; monthly prices remain the same.
The monthly total consists of the server's monthly price, additional drive charges, bandwidth upgrades, extra IPv4 addresses and any Windows license. Amount due = monthly total × number of months. Free operating systems incur no license charges, and included items are not charged again as optional add-ons. Review the itemized charges before payment.
Service stops if it is not renewed by the end of the term. Customers should keep track of the service period for each order and arrange renewal or migration before it expires. No contract means there is no obligation to order a subsequent billing period; the service term for a paid period is the one shown in the order record. Before stopping service, export any required data and verify that backups can be restored.
5. Server specs
Both server configurations include 2×1TB NVMe drives, each directly attached, with no hardware RAID. The two included drives have a combined raw capacity of 2TB; they are not delivered as a RAID-1 array. Formatting, file systems and redundancy choices affect usable capacity. Up to 2 additional 2TB NVMe drives can be added, and each is also directly attached.
The memory configuration cannot be upgraded on the same server after deployment. To switch from 128GB to 256GB, or from 256GB to 128GB, a new order for the other configuration is required. Customers must arrange their own system and data migration; a new order does not change the existing server in place.
Each server includes unmetered 250 Mbps bandwidth and 1 dedicated IPv4 address. 1 Gbps or 2 Gbps bandwidth is available as an option; all three bandwidth tiers are unmetered. Up to 255 additional IPv4 addresses can be added, for a maximum of 256 per server. Charges for additional drives, bandwidth and addresses are included in the monthly total according to the confirmed options.
Customers are responsible for data redundancy and backups. Depending on the workload, software RAID, a ZFS mirror and off-site backups may be used, but drive mirroring does not replace independent backups. Back up data before reinstalling the system, changing partitions, deleting files or changing software configuration. Replacing faulty hardware does not include data recovery.
6. Operating systems
There are 14 free operating systems: AlmaLinux 8, 9 and 10; CentOS Stream 9 and 10; Debian 11, 12 and 13; Ubuntu Server 22.04 LTS, 24.04 LTS and 26.04 LTS; FreeBSD 13; and Proxmox VE 8 and 9. Select an operating system at checkout based on application compatibility and administration requirements.
Windows Server is available with Standard or Datacenter licensing, in versions 2019, 2022 and 2025. The license is included in the server's monthly total and billed for the selected payment period. System languages available are English, Traditional Chinese and Simplified Chinese. The order selection determines the language provided.
Use of Windows licenses is subject to Microsoft's license terms. Customers are responsible for installing and licensing other software, applying updates and configuring their systems. Before reinstalling or changing the operating system, check application dependencies and create backups. Operating system delivery does not replace application or data management.
7. Access
After payment and delivery, sign in to the console and find server addresses and credentials in the server details. Connect to Linux, FreeBSD and Proxmox VE over SSH, and to Windows Server over RDP. Use the connection details shown in the console; do not assume default usernames or ports without verification.
If a server has multiple IPv4 addresses, use the first address listed in the console for SSH and RDP. Customers are responsible for configuring any other addresses in the operating system as needed. An additional address is not automatically a configured management endpoint.
Customers are responsible for server credentials, password changes, key distribution and firewall configuration. Check administrative access after the first connection. Before changing network or access-control rules, confirm a recovery path to avoid losing connectivity because of a local configuration change.
8. Support tickets
Submit service requests and fault reports through a support ticket in the console. To help investigate, include the server or order number, what happened, the conditions under which it occurred and any troubleshooting already performed. For connection issues, a redacted error message and relevant screenshots may be attached.
Do not include account passwords, email verification codes, private keys or unrelated business data in support tickets. If additional diagnostic information is needed, provide only what is relevant to the issue and redact credentials and other sensitive details. Email does not replace the order references and handling history recorded in a support ticket.
CloudSFP handles hardware, network and address allocation issues. Customers manage operating systems, applications, account permissions and data recovery. If responsibility for an issue is unclear, provide the symptoms and troubleshooting results in a support ticket so the parties can confirm the next steps based on the available information.
9. Acceptable use
The service must not be used to send spam, launch network attacks, distribute malware or engage in other unlawful activity. Customers must ensure that the software installed, content published and services operated have a lawful basis for use, and are responsible for the accounts, software and business activities they manage.
If abuse is detected, CloudSFP may suspend the affected server or IPv4 address and notify the customer through a support ticket. Customers must cooperate with the investigation and remediation and provide relevant information as needed. Changing an address or redeploying the same prohibited activity does not remedy the abuse.
Responsibility for service issues depends on their actual cause and the respective responsibilities of the parties. CloudSFP is responsible for hardware and network; customers are responsible for operating systems, applications and data, including backups. If service is affected by circumstances beyond reasonable control or by a customer's own actions, the parties should verify the situation through a support ticket and address matters within their respective areas of responsibility.
These terms are governed by the laws of the jurisdiction in which the platform operator is based. Service-related disputes should first be discussed through a support ticket. Any dispute that cannot be resolved by agreement will be submitted to a court of competent jurisdiction in that jurisdiction.