Cloud Hosting Service Terms

PART I – ARCHITECTURE AND CHARACTERISTICS

Article 1. Cloud Hosting infrastructure

1.1. HiTechCloud Cloud Hosting is built on distributed cloud computing, with an architecture entirely different from traditional shared hosting:

(a) Multi-node architecture: resources are distributed across multiple physical hosts, with no single point of failure;

(b) Auto-scaling: resources scale up automatically when traffic spikes, with no manual intervention required;

(c) Load balancing: intelligent traffic distribution across nodes;

(d) Storage: distributed across an NVMe SAN (Storage Area Network); IOPS are not shared in the traditional way;

(e) Automatic failover: when a node fails, traffic moves to another node in under 10 seconds;

(f) Global CDN: 25+ points of presence worldwide, included.

1.2. This service suits high-traffic web applications, large e-commerce sites (more than 10,000 orders per day), SaaS applications, web games and payment gateways.

Article 2. Cloud Hosting plans and pricing model

SpecificationsCloud BasicCloud StandardCloud AdvancedCloud Enterprise
vCPU (burst)2 (burst 4)4 (burst 8)8 (burst 16)16 (burst 32)
RAM4 GB8 GB16 GB32 GB
SSD NVMe50 GB150 GB400 GB1 TB
Bandwidth1 TB/month3 TB/month10 TB/monthUnlimited
Auto-scalingRAM/CPURAM/CPU/DiskFullFull + custom
CDN PoP5 (VN)15 (ASEAN)25 (Global)50+ (Global)
DDoS Protection10 Gbps20 Gbps50 Gbps100 Gbps+
Dedicated IP1248
SLA Uptime99,9%99,9%99,95%99,95%
SupportChat 24/7Phone + Chat 24/7Dedicated 24/7Enterprise 24/7

Article 3. Auto-scaling and flexible resource charging

3.1. Cloud Hosting uses a flexible pricing model (Flex Pricing):

(a) Base resources: a fixed monthly fee per plan;

(b) Burst/overage resources: charged hourly when basic resource limits are exceeded, at the rates set out in the price list;

(c) Overage bandwidth: charged at 0.05 USD per GB over the allowance (or the VND equivalent);

(d) Spending Cap: the Customer can set a maximum monthly spending limit to keep the budget under control.

3.2. HiTechCloud sends an email alert when resource use reaches 80% and 95% of the plan limit.

Article 4. Containers and deployment

4.1. Cloud Hosting supports several deployment methods:

(a) Git-based deployment (integrated with GitHub, GitLab and Bitbucket);

(b) Docker container support (Standard plan and above);

(c) One-click installer for 150+ popular applications;

(d) SSH/SFTP access with key-based authentication;

(e) Unlimited cron jobs with flexible scheduling;

(f) CI/CD pipeline integration (GitHub Actions, Jenkins).

Article 5. Data and continuity terms

5.1. Commitment to data integrity and durability:

(a) Data is replicated three times across three different nodes;

(b) Automatic daily snapshots, the most recent 30 days retained;

(c) Point-in-time recovery (PITR) for databases (Advanced+ plans);

(d) Cross-datacenter replication on Enterprise plans (RPO ≤ 5 minutes, RTO ≤ 1 hour).

5.2. Definitions of RPO and RTO:

– RPO (Recovery Point Objective): the maximum period of data that may be lost in an incident;

– RTO (Recovery Time Objective): the maximum time to restore service after an incident.

Revision history

Current versionby HiTechCloud
Updatedby HiTechCloud
Updatedby HiTechCloud
Follow category: Cloud HostingGet notified when new documents are added to this category.

If this article did not answer your question, please contact HiTechCloud for help.

Contact