It varies mainly based on the following: 

・Scope of work (rack/cabling/power/UPS/lines/removal, etc.)

・Downtime conditions (no downtime/short downtime/night/weekend)

・On-site constraints (equipment transport/protection/building access, rack congestion, work space)

・Required materials (cable length, labels, panels, PDUs, etc.)

After an on-site survey, we will provide an estimate that clarifies the schedule, personnel, and materials. 

We work with minimum privilege and minimum necessary information in accordance with DC regulations and your company policies.

We also accommodate NDAs, worker rosters, work reports, and photo handling rules (photography prohibited/masking required, etc.) as needed. 

 Yes. We support coordination considering on-site constraints, such as work application, entry procedures, and cross-connect/line installation arrangements.

(If there are contractual constraints, we will clarify which procedures need to be handled on your end.) 

We deliver in a reusable format (we will accommodate your preferred format as much as possible). 

Examples: Rack diagrams/U charts, wiring diagrams, wiring tables, port tables, power system diagrams, asset ledgers, work procedures, test results, photographic records. 

We will conduct tests according to the scope. Examples: 

・Power-on verification, link-up/connectivity, redundant path failover verification

・Preparation of monitoring perspectives (SNMP/alerts) and LED/log verification procedures

・Load testing (simple/full-scale) as needed

※We will clearly define in advance “what constitutes passing criteria.” 

Yes. We include “traceable afterward” deliverables. 

・Label design (naming conventions)

・Creation of wiring diagrams/port tables

・Bundling and route separation (power/communication, A/B separation, etc.)

・Post-completion photographic records (as needed) 

We can accommodate this. We will organize the work schedule and team structure in accordance with DC entry restrictions and work application requirements (advance application and on-site supervision requirements). 

Yes, it is possible. However, to “do it without stopping,” we design the **stop conditions, switchover sequence, and recovery (rollback)** in advance and operate with checklists on-site.

For power/UPS replacement as well, we organize the procedures according to redundant configurations and load conditions (e.g., N+1 configuration replacement, etc.). 

First, we eliminate “constraints” that are prone to causing accidents and rework, primarily checking the following:

・Rack available U space/depth/weight, mounting method, front/rear door interference

・Power capacity (A/B systems, PDU, breakers, redundancy), cable routing

・Cooling (hot/cold aisles, airflow, intake/exhaust, air conditioning constraints)

・Delivery route, protective coverings, tools/work space

・Traceability of existing wiring (label presence, organization status)

If possible, please prepare the following (if unavailable, we can conduct an on-site inventory): 

・Existing rack diagrams/U charts, wiring diagrams, power system diagrams (or distribution board information)

・Available work hours (evenings/weekends possible) and shutdown conditions (no shutdown allowed, short-term shutdown, etc.)

・Delivery route/facility access rules (DC regulations), escort availability

・Model numbers and quantities of additional equipment (estimates acceptable if not yet finalized) 

Starting from on-site surveys, we provide end-to-end support from planning → construction → testing → handover.

Examples: Rack mounting/U design, LAN/fiber/power cabling, labels and wiring diagrams, circuit/cross-connect arrangement support, power/distribution/UPS, acceptance testing, as-built drawings, equipment ledgers, and procedure documentation. 

The SLA applies only to services explicitly labeled as “SLA-eligible” on sales pages and other materials, guarantees a monthly uptime of 99.9%, and provides compensation in the form of **account credits (service credits)** when conditions are met. 

Standard support is best-effort and provided 24/7/365 (JST) in principle. However, support coverage is limited to the infrastructure layer; OS/middleware/applications are the customer’s responsibility. 

 As a countermeasure against unauthorized use (Abuse), by default permitted communications are limited using a whitelist approach, and outbound communications not explicitly permitted are blocked in principle. Standard permissions include DNS (TCP/UDP 53), NTP (UDP 123), HTTP (TCP 80), HTTPS (TCP/UDP 443), ICMP, and others. Additional ports/protocols required must be requested through an application process. 

We assume optional snapshots.

• $2.01/generation/month (charged according to number of generations)

  ※Since snapshots are not a backup alternative, we recommend backup for long-term storage and disaster recovery. 

 As an option, we offer PBS backup.

• Backup capacity: $0.01/GB per month (HDD storage)
• Backup generation: $13.40 per generation per month (charged according to number of retained generations)

  Example: 500GB×3 generations = ($6.70 for capacity + $40.20 for generations) = $46.90/month (excluding tax) 

Yes. We provide a **10Gbps private network (included free)** for connections between GPU-VPS instances and non-GPU cloud instances. It can also be used for multi-node inference and distributed processing. 

1 free by default, additional ones cost $2.01/each・month (example limit: maximum 5). 

 Any amount exceeding the free tier is assumed to be handled as **additional purchase (e.g.,$0.01/GB·month)** (please follow the portal display for the actual purchase method). 

 6TB (6,000GB) per month/VM is the guideline for the free allowance. An automatic email notification is expected to be sent when 80% of the free allowance is reached. 

**Prepaid (advance balance)** is designed for billing operations where hourly charges and optional fees are deducted. Monthly statements and invoices are issued. 

Hourly billing is based on “Uptime,” so usage charges are reduced while the instance is stopped.

However, monthly options (snapshots/backups/additional IPs/additional bandwidth, etc.) are billed monthly, so separate charges apply while in use. 

Here is a guideline based on the estimated formula:

• Lite: approximately $0.67/hour (approximately $491.30/month *730h calculation)
• Standard: approximately $0.81/hour (approximately $593.28/month)
• Pro: approximately $1.03/hour (approximately $748.32/month)
• Max: approximately $1.24/hour (approximately $904.84/month) 

**Pay-as-you-go (hourly billing)**.

You are automatically billed based on “uptime” + “allocated resources while running (vCPU / RAM / NVMe)”.

Estimated formula: 60 + (vCPU×2.5) + (RAMGB×0.3) + (NVMeGB×0.005) (yen/hour) 

 Virtual Machine (VM) GPU-VPS with dedicated GPU allocation per VM. ※If hypervisor type disclosure is required, let’s standardize the public-facing expression separately. 

First, we assume a configuration that allows you to start using Ubuntu 24.04 LTS (with GPU drivers pre-installed) immediately (please follow the portal display for availability of other templates). 

 No. You can launch immediately from a template with CUDA/drivers pre-installed. If necessary, please change versions or perform additional installations on your end according to your use case. 

 Yes. You can Rebuild (reinstall) from the portal (note that reinstallation will initialize the OS area, so please back up any necessary data in advance). 

Yes. You can freely change it later (using the portal’s resource modification feature). The reflection method (such as requiring a restart) varies depending on the content of the change. 

Yes. The storage for plans is NVMe SSD (250/500/1000/2000GB, etc.). 

The main differences are in vCPU, RAM, and NVMe capacity (as a guide)

• Lite: 8 vCPU / 64GB / 250GB
• Standard: 12 vCPU / 96GB / 500GB
• Pro: 16 vCPU / 160GB / 1000GB
• Max: 16 vCPU / 250GB / 2000GB 

Both have equivalent plan configurations. If you prioritize redundancy, we recommend distributing your order by selecting one unit from NODE-A and one from NODE-B. Each node is provided in stock (GPU slot) units, and multiple units can be ordered. 

Not shared. V100 (32GB) is exclusively allocated to 1 VM (1 instance = 1 GPU assumed) 

It depends on the scope (number of flows, integration destinations, authority/approval/audit trail requirements, and depth of testing).

First, through a free consultation (automation assessment), we will clarify “where to start appropriately” and “a rough estimate,” and define a scope that is neither excessive nor insufficient. 

It’s okay if the details are incomplete, but having the following information will help facilitate a smooth process:

• Current operational workflow (who does what)
• List of monitoring alerts (priority, frequency, problematic ones)
• Ticketing destination (Jira, etc.) and notification channels (email/chat)
• Constraints (prohibited downtime periods, approval requirements, audit requirements, etc.) 

We proceed with the minimum necessary information and permissions. (Need-to-Know principle)

• Access tailored to operations such as VPN/bastion hosts/time-limited accounts
• Recording of operation logs and change history
• Confidentiality handling rules (NDA, etc.)

  We design and operate in accordance with your organization’s rules. 

For introducing a single flow first, depending on the clarity of requirements, it’s easy to adopt a quick start → verify results approach.

As you expand across multiple systems (monitoring, ticketing, permissions, logs), coordination increases, so phased implementation (start small → horizontal expansion) is more practical. 

The specific deliverables depend on your project requirements, but generally include the following:

• Design documentation (architecture diagrams, workflows, permission/approval design, operations rules)
• Procedure manuals (Runbooks, cutover/recovery, operations procedures)
• Test results (test scenarios, results, points to note)
• Implementation deliverables (configurations, scripts, integration procedures, etc.)

  To avoid single-person dependency, we prioritize documentation as a key deliverable. 

Typically, this includes the following:

1. Current state inventory (As-Is) and issue analysis
2. Target selection and prioritization (roadmap)
3. Initial implementation of one flow (notifications/ticketing/runbooks, etc.)
4. Testing and operations rule establishment (approvals/audit trails/permissions)
5. Horizontal rollout and operations handoff (docs/procedures/training) 

Yes. Automation is used not only for “convenience” but also to improve recoverability.

For snapshots, backups, and DR, not only execution but also “recovery procedures and testing (restoration verification)” are important, so we design them including procedures and validation. 

are eligible. AD/OU design and baseline application via GPO (audit policies, security settings, update policies, etc.) can also be handled as part of operations governance.

On the Linux side, standardization of initial configuration is often achieved using cloud-init and similar tools. 

Design collection, classification, retention periods, and searchability according to your purpose (troubleshooting/auditing/security).

To avoid “collected a lot but can’t use it,” start by narrowing your scope and ensure you can reliably track only the logs you need. 

We can accommodate this.

• Approval flow (review and approval before execution)
• Separation of privileges (execution account/operations staff/approver)
• Audit trail (execution logs, change history, configuration differences)

  We will organize these in a form that can withstand audits. 

For critical changes (stop, switch, firewall changes, etc.), the basic design includes approval gates and manual confirmation steps.

Additionally, execution logs (who/when/what) are retained, and rollback procedures are prepared together.

To avoid “convenient but dangerous automation,” we build with control measures as a prerequisite. 

Starting with “one fixed flow” is the most failure-proof approach.

Example:

• Monitoring alert → notification (email/chat) → automatic ticket creation
• Standardize routine tasks (restart/switchover/log collection) into runbooks up to initial response
• Once effectiveness is confirmed, apply the same pattern horizontally to other alerts. 

. Typically, this includes monitoring events → notifications → ticket creation, first response (Runbook), standardized provisioning (templates/initial configuration), change management (approvals/audit trails), and log aggregation and compliance.

We separate “decisions that require human judgment” from “standardized tasks that can be systematized,” and implement them in phases in a structured order that maintains consistency. 

In many environments, the most effective order is “Entry Point (MFA/Administrator Privileges),” “Log Aggregation,” and “Protection of Critical Assets.” Prioritize according to your current situation. 

To avoid complexity, we make phased implementation + documentation + rollback procedures mandatory. We start with high-impact areas such as “entry points” and “logs.” 

Yes, this is possible. First, we reduce false positives and organize priorities, then design automatic ticket creation and initial response at a granularity that makes operations manageable. 

It’s covered. We integrate IAM, logs (CloudTrail, etc.), network, auditing, and alert coordination into an “operational” format. 

Yes. We can establish policies including GPO baseline, local administrator privileges, patch policies, audit logs, and more. 

We can assist you. We will design from the foundational stages of SIEM implementation: “collection, storage, permissions, and retention periods.” 

We prepare a basic set comprising configuration diagrams, configuration policies, policy/rule lists, operations manuals (Runbooks), rollback procedures, and ledgers (accounts, equipment, certificates, etc.). 

For small-scale deployments (entry + logs), it typically takes a few weeks, while full integration (ID/FW/EDR/SIEM) often requires several months. We mitigate risks through phased implementation. 

As a rule, we integrate with the premise of “utilizing existing systems.” Replacing products is a last resort; we start by organizing settings, operations, and log integration. 

We proceed on the basis of least-privilege work, separation of work accounts, and audit trails (work logs). Depending on your needs, methods such as VPN, bastion host, or screen-sharing only are also available. 

A network diagram (optional), a list of products in use (FW/EDR, etc.), log retention status, and specific issues (excessive alerts, audit compliance, etc.) will help facilitate the process. 

We will provide a quote based on your current scale (number of locations, endpoints, log volume), target scope (ID/FW/EDR/SIEM, etc.), and migration method (phased/bulk). You can start small with inventory and roadmap creation. 

 Applications with false information, impersonation, violation of laws and regulations, infringement of rights, spam transmission, phishing, malware distribution, etc. are prohibited. If a violation is suspected, we may take measures such as suspension. 

 Your name, address, contact information, etc. must be accurate and up-to-date. Any discrepancies may prevent registration/issuance or lead to suspension/revocation. Additionally, we may request additional verification or documentation to comply with third-party rules.

As a guideline, we respond on weekdays (JST). Please refer to the portal/announcement for specific business hours (best-effort support; response time is not guaranteed). 

We accept support requests through support tickets in the client portal (phone calls, verbal requests, personal emails, and social media/DMs are not accepted).

Standard support primarily covers “administrative procedures such as issuance/renewal/reissue/revocation” for certificates we sell. Technical tasks such as CSR creation, server installation, chain configuration, HSTS/redirects, etc., are generally the customer’s responsibility (we may offer paid support options as needed). 

 Example: Incomplete or false application information, private key leakage, suspected unauthorized use such as phishing, or when deemed necessary under the certificate authority’s policy. Refunds may not be available even in cases of revocation.

The timing for renewal varies by product and certificate authority. Please complete the procedure and payment by the renewal deadline. 

Depending on the Certificate Authority’s rules, reissuance may be possible. The procedure and number of reissuances allowed vary by product and Certificate Authority. 

In principle, you generate and manage them on your server/environment. Please manage private keys strictly to prevent leakage. 

 DV certificates tend to be issued relatively quickly, but OV/EV certificates may take additional time due to required documents and verification. We cannot guarantee issuance or processing time, as these depend on the certificate authority’s review process. 

 The verification process conducted by the Certificate Authority (CA) differs. Generally, DV focuses on domain ownership verification, while OV/EV includes additional verification such as organizational validation. The verification process and required duration follow the CA’s rules. 

Choose according to your purpose.
・Personal site / Small-scale site: Domain Validation (DV)
・Corporate site: Organization Validation (OV)
・When you want to strongly demonstrate external credibility: EV (*Varies depending on availability)
Also, a wildcard is suitable when you want to consolidate multiple subdomains.

 May be provided as an additional service. Availability, conditions, and restrictions are subject to our guidance (screen displays, etc.). 

This may be possible. You will need to complete the transfer procedure at the destination, as well as unlock the domain and obtain the EPP code. There may be a transfer restriction period due to third-party rules. 

It may be possible. Typically, “unlock,” “obtain EPP code,” and “verify administrator email receipt” are required. Transfer rules differ by TLD, so please follow the instructions on the application screen and guidance. 

 It may be possible to verify/issue in the portal’s domain management screen. Depending on the TLD, the acquisition procedures and restrictions may differ. 

This is a lock feature to prevent unauthorized domain transfers. You may need to temporarily disable it when performing a transfer (availability varies by TLD). 

Propagation time varies depending on TTL settings, cache status, and internet-side factors. Immediate propagation is not guaranteed. 

If the portal provides DNS management functionality, you can add and modify records. If you are using an external DNS, please manage it on the external side. 

The change procedure itself may be possible in some cases, but restrictions or additional verification may be required due to third-party rules. Please always keep your registration information accurate and up to date. 

 Depending on the TLD, registration type, and third-party rules, some registration information may be publicly disclosed or shared with third parties. The scope of disclosure varies by TLD and other factors. 

 If the renewal procedure and payment are not completed by the deadline, the domain will expire. In some cases, recovery (redemption, etc.) may be possible after expiration, but the availability, period, and costs vary depending on the TLD and other factors, and recovery is not guaranteed. 

 We may send notifications, but you are responsible for managing deadlines regardless of whether the notification is received. Please also check your spam folder. 

 If automatic renewal is supported, you can configure it in the portal (terms of provision follow the on-screen instructions). However, the final responsibility for managing renewal deadlines rests with the customer. 

You can check domain expiration dates, renewal status, and status in the client portal (management console). 

 The number of years you can select varies by TLD. The periods available for selection on the application screen will apply. 

In most cases, it will be reflected within a few minutes to several hours, but it may take longer depending on the TLD type, registry-side processing, and whether additional verification is required. Due to the first-come, first-served principle, there is a possibility that the domain may be acquired by another party during the application process. 

After domain “registration completion” or SSL “issuance completion,” due to third-party rules, cancellations/refunds based on customer circumstances are not possible in principle. Even before completion, if actual costs have already been paid to third parties, they may not be eligible for refund. 

Please pay within the specified deadline from the date of application (e.g., within 3 days). For renewal invoices, payment must be made by the renewal deadline. If payment confirmation is not received within the deadline, your application may be canceled. 

You can use the payment methods displayed on the order screen (e.g., credit card, PayPal/Stripe, bank transfer, etc.). Available options vary by service. 

As a general rule, we will begin procedures such as domain registration/renewal/transfer or SSL issuance/renewal after payment confirmation. 

Renewal fees are based on the amount displayed on the order screen at the time of renewal. Fees may vary due to changes in registry/certificate authority terms or currency exchange rates. 

 The prices shown in search results may be estimates (reference display). The final billing amount will be the amount displayed on the order screen (cart/order confirmation screen). 

We proceed based on the principles of least-privilege work accounts, securing operation logs, and configuration file storage rules (encryption and storage location).

We will comply with your policies as needed, including NDA execution and data export restrictions.

We define test items from necessary perspectives such as connectivity, routing, redundancy switchover, VPN connection, firewall policies, and monitoring alerts.

Even when production-equivalent testing is difficult, we mitigate risks through phased switchover design.

The basics include As-Is/To-Be configuration diagrams, IP/VLAN ledgers, configuration backups, switchover/recovery procedures, test items and results, and operations runbooks (monitoring/incident response).

These are selected based on the scope of the project.

We can design monitoring targets, thresholds, and notification rules (including false positive suppression).

We also handle log aggregation (Syslog, etc.) and preparation of initial troubleshooting flows (Runbooks) for incidents.

Yes, it is possible. We organize policies in the following order: inventory of current policies (usage status, duplicates, exceptions, responsibility boundaries) → consolidation → principle of least privilege.

When making changes, we clearly define the scope of impact and rollback procedures, and migrate safely in stages.

We minimize impact through phased transitions wherever possible.

When downtime is required, we prepare transition procedures, recovery (rollback) procedures, and communication flows in advance to ensure implementation can be completed quickly.

For small-scale projects (1 site, a few servers), several weeks to a few months; for medium-scale projects, 1 to 3 months is typical.

 The timeline varies depending on the depth of preliminary investigation, availability of a testing environment, and the number of switchovers.

We can accommodate both upgrades/consolidations that leverage existing equipment and new deployments.

Taking into account current constraints (support deadlines, performance, operational structure), we propose the optimal configuration and migration procedure.

 LAN (VLAN/ACL), WAN (circuits/routing), VPN (site-to-site/remote), firewall, redundancy, monitoring/logging, and operations handover (documentation/procedures) are all within scope.

We can also provide support for specific areas as needed on a spot basis.

Having a configuration diagram, IP/VLAN list, network information (ISP/bandwidth/redundancy), device models/OS, current issues, and desired schedule will make the process smoother.

If documentation is not available, we can start with an inventory assessment (As-Is).

Individual quotes are provided based on scope (number of locations/devices/lines), requirements (downtime acceptability, redundancy level, security requirements), and work schedule (weekdays/nights/holidays).

We will first conduct a current situation assessment and provide an estimate.

Yes, we can. We handle everything from rack installation, cabling, and labeling in the data center/server room to connection verification (if there are entry procedures or work time restrictions, we will coordinate in advance). 

Configuration diagrams, volume tables, connection tables (ports/zoning, etc.), switchover procedures, rollback procedures, checklists, test items and test results (evidence), operations procedures (monitoring and initial troubleshooting), etc. 

Yes, we can. We create a “recoverable state” that includes generation management, recovery procedures, and DR (replication, etc.). Our scope can also include **restore verification (drills)** after the switchover. 

Yes, it is possible. In addition to organizing I/O requirements in advance, we conduct load testing (e.g., FIO) and acceptance testing (performance, redundancy, recovery) as needed, and keep them as evidence. 

The optimal approach varies depending on the target (VM/DB/files) and requirements (downtime tolerance, consistency, speed). After assessing the current situation, we design a practical procedure from options such as online/offline/staged migration. 

We define switch conditions, decision points, and recovery procedures (rollback) in advance without ambiguity about “possible/impossible.” We also prepare decision criteria for the day of the switch (check items, logs, test results). 

It depends on the system dependencies and migration method. To minimize downtime, we organize and propose options and risks, such as phased migration / pre-synchronization / rehearsal of cutover procedures. 

Yes. Based on EOL/EOSL, capacity increase, performance (IOPS/latency), redundancy, backup/DR, and operations structure, we will implement a configuration that meets your requirements. 

We support design, setup, and migration tailored to your existing methods such as FC (SAN), iSCSI, NFS, and CIFS (SMB). Configurations including HCI (Ceph/vSAN, etc.) are also available for consultation. 

From current state assessment (capacity, I/O, dependencies) → sizing → configuration design → setup → data migration → acceptance testing → operations handover (document delivery), we handle everything end-to-end. 

Vendor-free.

We can handle everything from surveying your existing environment. Details will be confirmed through a hearing.

In principle, we do not provide refunds. Exceptionally, we may approve a final settlement, but the eligible credit types, conditions, fees, etc. are specified. 

No. In principle, compensation will be provided as account credit, and cash refunds will not be issued. 

A monetary equivalent amount recorded in your customer account that can be applied to service fees within the scope we define. 

Cancellations can be requested from the client portal. In principle, requests submitted by the day before the next renewal date will be processed as “do not renew (renewal suspension).” Fees already paid will not be refunded in principle, unless the reason is attributable to us. 

If payment is not confirmed within the deadline after application, your application may be canceled. The deadline follows the display on the application screen and invoice. 

After payment confirmation, the service will be provided ready for use within a few minutes to 1 business day in principle (excluding cases requiring review, congestion, etc.). 

You can use the payment methods displayed on the order screen (e.g., credit card, PayPal/Stripe, bank transfer, etc.). 

Standard support primarily covers troubleshooting and workaround suggestions for the infrastructure layer (platform, control panel, etc.). Configuration and operations of guest OS/middleware/applications, as well as DNS/certificate implementation tasks, are the customer’s responsibility. 

As a general rule, we accept inquiries through support tickets in the client portal (we do not provide technical support by phone except for individual contracts). 

Please submit a support ticket within 30 days from the incident occurrence (or our announcement), including the affected service ID, time of occurrence, and impact details. If no application is submitted, credit may not be automatically granted. 

This is a system that guarantees 99.9% uptime per calendar month (JST). If the conditions are met and the SLA falls below the guaranteed value, we will compensate with account credit (service credit) (no cash refund will be provided). 

Email sending may require application and strict review due to high risk of abuse. We recommend using an external authenticated SMTP relay. 

To prevent unauthorized use, we define standard permitted outbound traffic (e.g., DNS/NTP/HTTP/HTTPS, etc.), and other traffic may be blocked. If you require non-standard ports/protocols, please submit a request including the purpose, destination, and duration. 

Assigned IPs are number resources managed by us and are provided according to the terms of service. Even when fixed IPs are provided, they may be changed for operational or security reasons. 

For critical data, we recommend regular backups (including offsite storage) and verification of restoration procedures. Maintenance and operations of the OS, middleware, and applications (updates, configuration, backup design, etc.) are the customer’s responsibility.

It may be offered as a plan/option. Retention generations, restoration methods, and pricing follow the display on the application screen.

We may be able to provide guidance for publicly available official ISOs. We cannot provide ISOs without distribution rights (such as commercial OSes). Whether customer-provided ISOs can be used depends on size, format, security review, and other factors. 

A custom ISO mount feature may be provided. Please follow the portal’s instructions for availability, procedures, and limitations.

You may be able to reinstall from the client portal. When executed, existing disk contents are normally initialized, so we recommend taking a backup/snapshot in advance. 

We provide CentOS, Rocky Linux, Ubuntu, Debian, AlmaLinux, Fedora, and more. Templates may be added or updated. 

A method where virtualization technology isolates multiple virtual servers on a single physical server (infrastructure), utilizing resources within the allocated vCPU/memory/storage range for each VPS. You can freely build and operate the OS and middleware on your end.

Each plan has a guideline (upper limit) for monthly data transfer. Handling of overages (restrictions/additional purchases, etc.) follows the information displayed on the application screen.
 

Yes. VPS hosting uses NVMe storage (as indicated on the sales page). 

Changes may be possible through a plan change (upgrade/downgrade). The timing of reflection and whether a shutdown is required vary depending on the content.

Select based on your use case (Web/DB/development/testing, etc.) and the required vCPU, memory, storage capacity, and estimated monthly transfer volume. If you are unsure, please contact us with your expected usage (concurrent connections/expected access volume/current server utilization, etc.).
 

To prevent abuse, we define a standard range of allowed outbound traffic (e.g., DNS/NTP/HTTP/HTTPS, etc.). If access outside the standard range is required, it must be requested and will be reviewed and approved through an application process. High-risk use cases such as email transmission are subject to strict review. 

 Even when assuming fixed operation, changes or suspension of assigned IPs may occur when security measures, upstream requirements, equipment upgrades, etc. are necessary. Please manage IP-dependent configurations on your end and prepare for changes. 

Support requests are primarily handled through support tickets in the client portal. We do not provide phone support except for individual contracts. 

You can apply for cancellation from the client portal. As a general rule, it will be treated as “do not renew next time (renewal stopped)”. Returns after service commencement are not possible, and unless there are reasons attributable to us, refunds of paid fees will not be issued in principle. 

After payment confirmation, service will be provided in a ready-to-use state typically within a few minutes to 1 business day (may vary depending on review, congestion, or configuration details). 

You can select from the plan options at the top of the page (High Memory / High CPU / High Storage / High Network, etc.) or compare and choose from the pricing and plan list. If you are unsure, please contact us with your use case (CPU-focused / memory-focused / IO-focused / bandwidth-focused).

Yes, you can install an OS yourself using an ISO (via console, etc.).
※ Please prepare the installation media/license on your end. The OS installation procedure itself may be outside the scope of standard support.

 Yes, you can perform reinstallation and snapshots (create/restore) from the client portal.
※Snapshots are a mechanism to simplify restoration and are not a substitute for backups. We recommend backing up important data separately.
 

You can select from standard OS templates (e.g., CentOS / Rocky / Ubuntu / Debian / AlmaLinux / Fedora, etc.).
※ Since the provided templates are updated, please check the client portal for the latest list. 

Provided as a virtual machine (VM). You can freely configure the OS and software on your end within the resource limits of your contracted vCPU/memory/storage, etc.
※Configuration/operations/security of OS, middleware, and applications are your responsibility. 

 In principle, yes. You can add storage capacity by changing (upgrading) your plan from the client portal.
※After expansion, you may need to extend the partition/file system on the OS side. For reduction (downgrade), data migration may be required.

The feasibility and procedure for migration vary depending on your current operations (customer management, billing, integration backends).
Please organize your requirements and consult with us via a support ticket (individual support/quotation may be required as needed). 

Typically, the flow is: (1) Application → (2) Payment/Confirmation → (3) Initial setup in the admin panel (brand/payment/products) → (4) Start of sales.
If review or additional confirmation is required, it may take time before you can start.

Personal information collected and processed by us is handled in accordance with our Privacy Policy and related regulations.
For domain/SSL procedures, it may be necessary to provide registration information to registrars/registries/certificate authorities, etc. 

There are prohibited uses. Violations of laws and regulations, infringement of rights, spam, phishing, malware distribution, etc. are strictly prohibited.
If a violation occurs or is suspected, we may take measures such as communication restrictions or suspension. 

To prevent unauthorized use and ensure safe operations, we may request additional verification (identity/corporate verification, contact verification, usage purpose verification, etc.) at the time of application or during use.
If you do not cooperate with the verification process, your application may be held, restricted, or suspended.

Due to the nature of digital services, once provision has started, refunds will not be issued in principle unless the cause is attributable to us.
Additionally, due to the nature of third-party rules for domains/SSL, refunds may not be possible after registration/issuance is completed. 

In principle, you can process this from the client portal.
The timing at which it is treated as “do not renew next time (renewal suspension)” may vary depending on the application time and relationship with the renewal date.

Billing is generally subscription-based (recurring). Renewal dates and billing timing follow what is displayed in the management console and invoices.

This refers to operations that adjust the priority of ticket responses (for example, increasing priority under certain conditions, etc.).
However, this does not guarantee response times or resolution deadlines. Applicable conditions vary depending on the plan and operational rules. 

This refers to operations aiming for 24-hour reception and response capabilities, but does not imply time guarantees (SLA) such as response time or resolution time.
Support is provided on a best-effort basis, and depending on the situation, investigation and response may be delayed. 

In principle, support is provided through support tickets in the client portal (for record-keeping and quality assurance).
Unless there is a separate contract, we do not provide technical support by phone. 

This is possible, but custom development or integration work may be required. Please organize your requirements (API specifications, authentication methods, creation/deletion flows, etc.) and contact us. 

If the backend supports API or similar functionality, configurations can be created automatically after application.
However, if review, identity verification, external factors, or exceptional conditions are involved, manual handling or holds may occur. 

The supported backends shown in the management console and information pages are the latest.
(Example: various integrations such as payment/cloud/registrar. Support status may be changed or added) 

Refers to the partners (cloud infrastructure, payment, registrar, etc.) that actually create and provide the services.
Reseller Hosting serves as the bridge between the front end (sales/billing/customer management) and the backend (provisioning/issuance/creation). 

Email operations tend to have complex requirements from the perspective of deliverability and spam prevention, so we recommend choosing an appropriate configuration (e.g., external SMTP relay) depending on your use case.
Email deliverability and DNS configuration (SPF/DKIM/DMARC, etc.) are in principle the responsibility of the customer’s operations. 

This indicates that DNS-related services (e.g., DNS hosting, etc.) can be provided as a product.
The scope of services varies depending on the backend and our service offerings. 

In principle, due to third-party rules and specifications, cancellations/refunds may not be possible after registration completion or issuance completion.
Even before the procedure begins, if actual costs have already been paid to third parties, they may be excluded from refunds. 

You can offer domain registration/renewal/transfer, SSL certificate issuance/renewal, and other services as products.
However, domains/SSL are subject to third-party rules from registrars/registries/certificate authorities (CAs), and third-party rules may take precedence. 

Register VPS/cloud and similar products to provide a complete flow from order through billing to automatic provisioning (if supported).
Available sales options vary depending on backend support and product design. 

Availability and format (electronic delivery, etc.) follow the features provided in the control panel and operational policies.
For details, please check the reporting function in the control panel or contact support. 

A feature that automates, to the extent possible, a series of operations including quote/invoice issuance, payment deadline management, payment confirmation, renewal, and notifications.
There are cases where manual operations are required (review, exception handling, external factors, etc.). 

This is a system that integrates with credit cards and payment services (e.g., Stripe/PayPal, etc.) to automate recurring billing and invoicing.
The available payment methods are prioritized by what is displayed on the application and management screens. 

Multi-language display is supported. The supported languages and translation scope vary depending on the portal’s availability.
If specific wording needs to be tailored for your company, we will adjust it in accordance with your operational policies.

We support basic white-label settings such as logo and color scheme (scope complies with the control panel features).
For more advanced design adjustments or custom modifications, separate arrangements (individual quotation) may be required. 

Yes. You can operate the client portal on your company domain (e.g., portal.example.com).
For DNS records and SSL certificate preparation required for setup, please follow the instructions in the control panel or procedure. 

The presence or absence of an initial setup fee may vary depending on the product, campaign, etc. The display on the application screen takes precedence. 

Yes, you can (the procedure and timing follow our operations policies).
Please contact support if you want to “upgrade to a higher plan starting next month” or “upgrade only during peak seasons.” 

The basic fee (plan pricing) differs. Depending on the plan, terms such as operational scale, required support scope, and priority may vary.
For specific differences (limits, scope, conditions, etc.), please refer to the details page of each plan and the information on the application screen. 

Bronze: $112.56/month, Silver: $166.16/month, Gold: $333.66/month, Platinum: $656.60/month (example pricing).
The latest pricing and billing units displayed on the application screen take precedence.

For example, you can sell products such as VPS/cloud, domain/SSL, DNS, and email-related services.<br>
The products you can actually sell and the scope of services depend on the plan details and the support status of the integration partner (backend). 

Ideal for web development companies, system integrators/operations firms, and sole proprietors who want to offer servers/domains to their clients “as their own service.”
You can start small and adjust your plan as your operations scale. 

A “sales platform (portal + automation)” that allows you to sell and operate hosting-related services under your own brand (white label).
Centrally manage custom domains, payments, billing, client portals, product registration, notifications, and more. 

Yes, we can. We provide support that includes preparing operational procedures, operational training, incident response workflows, establishing monitoring and backup operations, and improvement proposals. 

It varies depending on the scale and downtime constraints. Generally, we proceed in the order of “current state assessment → design → PoC/verification → setup → phased migration → cutover → handover,” and we first present a roadmap (schedule proposal) based on the results of the current state assessment. 

We operate based on a fundamental policy of least-privilege work accounts, recording of work logs/change history, and restriction of access routes (VPN/bastion hosts, etc.), adapted to your company’s rules. We can also design with security requirements (audit compliance, etc.) as a prerequisite. 

Example: Configuration diagrams, parameter sheets, design documents, migration plans, cutover/rollback procedures, test case documents, verification results, operations manuals (Runbooks), monitoring design documents, etc. The required level of detail is adjusted to match your operations structure. 

Yes, we can support this. We will organize and establish monitoring (Zabbix, etc.), notification flows, log collection and storage, and backup methods (generations and recovery testing) as part of operations design. 

Yes, we can. We will formulate a hypothesis based on current load trends and target performance, define PoC configuration, verification items, and evaluation criteria, and execute the test (the results will be reflected in the production design). 

Yes, it is possible. Since optimizing only virtualization tends to lead to operational failures, we address this with comprehensive design that includes network, security, and storage. 

Yes, it is possible. We will document and provide rollback procedures in case of switchover failure, organize RTO/RPO, and include DR configuration (remote sites, replication, etc.) along with testing procedures.  

Yes. We design parallel operation, phased migration, and switchover procedures tailored to the characteristics of your target system to minimize downtime (any necessary downtime will be clearly identified in advance). 

Yes, we can. We will organize design considerations such as performance, redundancy, failure domains, and network isolation, and establish procedures that include post-deployment operations (monitoring, backup, expansion procedures). 

Yes, we can support that. We will design an operational configuration that includes connectivity between your site and the cloud (VPN, etc.), name resolution, ID integration, operations monitoring, and backup policies. 

We primarily support VMware vSphere/ESXi, Hyper-V, and Proxmox (including HCI). We assist with design, setup, migration, and operations planning tailored to your current environment and destination requirements.  

If possible, please prepare a server/VM list (CPU/memory/storage), virtual infrastructure version, network diagram (VLAN/routing/firewall), storage configuration, backup method, maintenance deadlines, and available downtime windows. If unavailable, we can conduct inventory assessment through interviews. 

Pricing varies based on scope (number of hosts/VMs/sites, tolerable downtime, inclusion of design/migration/operations planning). We first align assumptions through current-state assessment (As-is), then proceed to estimates → phased implementation quotations. 

Purpose and Use Cases (Web publishing, business systems, AI training, test environments, etc.)

Preferred Configuration (cloud/VPS/GPU/dedicated setup, with or without operations support)

Scale Guidelines (number of users, traffic volume, required CPU/memory/storage capacity, GPU requirements)

Migration Needs and Timeline (existence of current environment, desired start date)

Firewall control functionality is provided as standard.

For outbound traffic, we do not allow all connections; instead, we use a whitelist-based approach based on these regulations.

VPN is possible by setting up a virtual router on your end.

We clearly define our support scope to ensure that our customers can use our services comfortably without misunderstanding.

Please refer to our Standard Support Terms.

Yes, it is available.

Please see the service page for details.

Cloud
VPS  

GPU VPS 

TETS2

TEST

It is required. For backups, not only “taking” them but also “being able to restore” them is important, so we design them including recovery procedures and recovery testing.

Yes, it’s possible. Our basic approach is to integrate while leveraging your existing assets. We can also propose additions or enhancements only for the areas that are lacking.

Basically, the flow is: current state inventory → ideal state/prioritization → implementation for one target → incorporation into operations → horizontal rollout.

Configuration diagrams, monitoring design documents, backup design documents, notification/ticketing design, runbooks, recovery procedures, recovery test results, operations handover materials, etc.

Other deliverables depend on individual requirements.

Start small (1 target), create a success pattern, then scale horizontally. Since it varies by scale and requirements, we present a roadmap after As-is inventory.

Designed with the principles of least privilege, bastion/temporary credentials, operation logs, and procedure-based operations. Secret masking and environment isolation are also implemented as needed. 

Monitoring tools/notification destinations, backup methods/generations/storage locations, critical systems list, incident history, recovery challenges, network overview diagram (if available), etc. 

Custom quotes based on current scale (sites/units/monitored targets/backup capacity), existing tools, RPO/RTO requirements, and documentation scope. We also support spot, quasi-mandate, and ongoing operations support.