One model, two memory options, monthly billing
Our operations cover server delivery, hardware and networking, and support requests. Server specifications are confirmed before an order is placed. After delivery, server details, paid invoices and support tickets are available in the control panel.
Every server uses an AMD EPYC 7543P with 32 cores and 64 threads. The memory lineup has two options: 128GB or 256GB of DDR4-3200 ECC. The CPU, memory and drives are dedicated to one customer and are not shared with other customers.
Both options include 2×1TB NVMe drives connected directly to the system, 250 Mbps unmetered bandwidth and 1 dedicated IPv4 address. The data centre is in Tokyo, Japan. Memory cannot be upgraded on the same server after provisioning. Changing memory tiers requires a separate server; migration and data backups are arranged by the renter.
Available add-ons are additional drives, bandwidth, extra IPv4 addresses and Windows licensing. The configuration and amount due are shown item by item before an order is placed. Availability is based on the latest status returned in the control panel.
Orders are placed on the configuration page. Paid invoices, server details and support tickets are managed in the control panel.
This comparison looks at deployment models and does not represent performance testing of any specific provider. The key differences are whether resources are shared, what is delivered, and which equipment and rack responsibilities fall to the operator.
| Comparison | Shared VPS | Dedicated server | Self-managed rack |
|---|---|---|---|
| Dedicated resources | Delivered as a virtual instance; underlying physical resources are usually shared among multiple instances. | The entire server is dedicated to one customer, including its processor, memory and drives. | Equipment ownership and resource allocation are determined independently; hardware procurement and deployment are self-managed. |
| Compute consistency | Performance can be affected by resource allocation policies and shared load on the underlying hardware. | The server's compute resources are not shared with other customers; actual performance depends on its workload and system configuration. | Hardware capacity can be planned independently; performance tuning, expansion and equipment upgrades are self-managed. |
| Delivery | Usually delivered as a virtual instance, with workloads running on its operating system. | A complete server is delivered. Access credentials are available in the control panel, and the system is managed over SSH or RDP. | Requires arranging equipment procurement, rack installation, cabling and data centre connectivity. |
| Upfront cost | Typically starts with renting an instance, billed according to the selected resource specifications. | Rented monthly with no setup fee and no need to purchase the server hardware upfront. | Typically includes equipment, rack space, power and network costs. |
A dedicated server does not provide automatic system redundancy. Direct-attached drives, application deployment and backup policies should be assessed separately; data protection should not depend solely on whether a server is dedicated.
The service delivers a dedicated server. Data centre infrastructure and software running on the server fall under separate areas of responsibility. The following breakdown can help organise fault reports.
The processor, memory and drives listed in the order, along with server hardware faults.
Power and network infrastructure that supports server operation in the data centre.
The bandwidth tier and dedicated IPv4 address allocation specified in the order.
Hardware checks and replacements following a review of the reported issue through a support ticket.
For hardware or network issues, include the relevant server details in a control panel ticket.
System updates, firewall, application installation, performance tuning and software configuration.
Control panel account, server passwords and SSH keys, as well as system access permissions.
Drives are directly attached and do not use hardware RAID. Software RAID, ZFS mirroring or off-site backups must be planned independently, along with recovery procedures.
Software licences and business activities must comply with applicable requirements. Spam, network attacks and malware distribution are prohibited.
An image or array is not a substitute for an independent backup. Confirm that data can be restored before making system changes.
Support tickets should distinguish between network connectivity issues, system configuration errors and hardware faults. Clear details help identify the relevant area of responsibility. Passwords and private keys should never be sent in public email.
Requests related to a server are submitted through the account so they can be linked to the order, server ID and follow-up records. General enquiries reach the team by email.
After signing in to the control panel, open the support ticket page and provide the server ID, error details, checks already completed, and any system or network changes made before the issue began. Keep follow-up information in the same ticket to preserve context.
For connection issues, include the client error message. Remove passwords, keys and sensitive business information from logs before sharing them. Check the address and credentials in the server details before connecting. When multiple IPv4 addresses are assigned, connect using the first address.
For pre-sales questions, business enquiries, security reports or account access issues, contact the support team by email. Include the subject and relevant context; do not attach server passwords or private keys.
For email about an existing order, include the order number and account email address for verification. Server faults and service requests can be followed up through a control panel ticket once account access is available. Progress updates are provided in the reply.
The monthly total combines the server and selected add-ons. The amount due for the chosen billing period is calculated from that total. There is no setup fee, no contract and no discount between billing periods.
Amount due = monthly total × number of months
The monthly total includes the server's monthly price, plus any additional drives, bandwidth, extra IPv4 addresses and Windows licensing. Monthly, quarterly, semi-annual and annual billing cover 1, 3, 6 and 12 months respectively. The amount due is the monthly total multiplied by the number of months.
Before payment is confirmed, the configuration page shows the itemised configuration, the amount due for the current period and the available payment methods. All charges are in USD; payment methods are listed on the configuration page. Paid transactions appear in the control panel's billing section.
Service stops at the end of the term if it is not renewed. Renewal, system migration and data backups should be planned according to business needs; a billing period is not a data backup measure.
Check that the CPU, memory and directly connected drives suit the workload, then review the monthly prices for both options and any add-on charges. The specifications page describes what is delivered; the pricing page lists the charges.