SOLUTIONS / VPS
A VPS provides a virtual server environment for running applications. When evaluating FibaCloud options, look beyond the package name: consider CPU sharing, memory, disk use and operating responsibilities together. Refine the initial configuration with measurements from the application you intend to run.
01 / Overview
vCPU, memory, storage and networking represent different constraints. Adding memory does not necessarily solve an inefficient query or a CPU-intensive loop. Understanding which resource the application needs is the first step toward a useful comparison.
A VPS does not mean that the entire physical machine is dedicated to you. Review shared and dedicated CPU conditions in the relevant product. Plan operating systems, applications, updates and backups alongside capacity.
Plan web applications, APIs and supporting services around a virtual server. Let operating system and software requirements guide selection.
Distinguish variable activity from sustained CPU use. Measure whether the constraint comes from application behaviour, memory or disk before adding resources.
Define setup, access, backups and updates from the beginning. A virtual server does not imply automatic application management.
02 / Architecture
Conceptual view: an application uses several resources together. A virtual server does not imply exclusive use of the entire physical machine.
Selection guide03 / Selection guide
| Consider | How to decide | Why it matters |
|---|---|---|
| CPU model | Assess shared or dedicated CPU against the workload. | A package name alone does not define processing capacity. |
| Memory | Measure the working set and peak usage. | Insufficient memory can cause errors or additional disk activity. |
| Storage and data | Separate capacity, I/O and persistence requirements. | A larger disk does not automatically make an application faster. |
| Operating scope | Assign system, application and backup maintenance. | Resource costs and operating work remain visible together. |
04 / Use cases
Measure requests, sessions and data access. Record application versions and dependencies clearly.
Test separately from production. Avoid unnecessary personal data and exposed management services in test environments.
Assess the resources and duration of background tasks. Observe interactions when several services share a server.
Plans & pricing
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
Shared 1
|
1 CPU
|
1 GB
|
25 GB
|
2TB
|
4.00$Hourly: 0,005
|
|
Shared 2
|
1 CPU
|
2 GB
|
50 GB
|
3TB
|
6.00$Hourly: 0,008
|
|
Shared 3
|
2 CPU
|
4 GB
|
80 GB
|
5TB
|
12.00$Hourly: 0,016
|
|
Shared 4
|
4 CPU
|
8 GB
|
160 GB
|
6TB
|
24.00$Hourly: 0,032
|
|
Shared 5
|
6 CPU
|
16 GB
|
320 GB
|
10TB
|
49.00$Hourly: 0,068
|
|
Shared 6
|
8 CPU
|
32 GB
|
640 GB
|
20TB
|
94.00$Hourly: 0,130
|
|
Shared 7
|
16 CPU
|
64 GB
|
1280 GB
|
22TB
|
180.00$Hourly: 0,250
|
|
Shared 8
|
32 CPU
|
128 GB
|
2560 GB
|
25TB
|
360.00$Hourly: 0,500
|
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
Dedicated 1
|
2 CPU
|
4 GB
|
80 GB
|
6TB
|
16.00$Hourly: 0,022
|
|
Dedicated 2
|
4 CPU
|
8 GB
|
160 GB
|
7TB
|
28.00$Hourly: 0,038
|
|
Dedicated 3
|
8 CPU
|
16 GB
|
320 GB
|
8TB
|
49.00$Hourly: 0,068
|
|
Dedicated 4
|
16 CPU
|
32 GB
|
640 GB
|
9TB
|
94.00$Hourly: 0,130
|
|
Dedicated 5
|
32 CPU
|
64 GB
|
1280 GB
|
12TB
|
180.00$Hourly: 0,250
|
|
Dedicated 6
|
48 CPU
|
96 GB
|
1920 GB
|
14TB
|
260.00$Hourly: 0,361
|
|
Dedicated 7
|
50 CPU
|
128 GB
|
2500 GB
|
16TB
|
340.00$Hourly: 0,472
|
|
Dedicated 8
|
56 CPU
|
256 GB
|
5000 GB
|
18TB
|
490.00$Hourly: 0,680
|
| Package | CPU | RAM | Storage | Bandwidth | Monthly price (USD) |
|---|---|---|---|---|---|
|
High Memory 1
|
2 CPU
|
24 GB
|
20 GB
|
6TB
|
28.00$Hourly: 0,038
|
|
High Memory 2
|
4 CPU
|
48 GB
|
40 GB
|
8TB
|
49.00$Hourly: 0,068
|
|
High Memory 3
|
6 CPU
|
90 GB
|
90 GB
|
10TB
|
74.00$Hourly: 0,102
|
|
High Memory 4
|
10 CPU
|
150 GB
|
200 GB
|
12TB
|
120.00$Hourly: 0,166
|
Review the current configuration, price and order terms before selecting a service.
05 / From planning to operation
List application versions, databases, storage and access needs. Use the list to choose initial resources.
Arrange management identities and network rules. Make updates and backup preparation part of readiness for production.
Observe CPU, memory, disk and response times with representative operations. Record a comparable baseline before changing resources.
Assess configuration options for the measured constraint. Verify resize conditions and data implications in the relevant product.
A VPS is a virtual server environment. If the workload requires an entire physical machine, assess Bare Metal separately.
VPS describes virtualization; Shared CPU describes how processing resources are shared. Review CPU and memory terms independently of package names.
It may be appropriate if the requirements fit. Allow resources for the system, application and data, then validate under representative load.
Do not assume so. Verify scope and pricing for the selected service, and test consistent recovery of application files and data.
Connect product decisions with installation, configuration and operating knowledge.
These references explain the technical concepts discussed on this page. Available configurations and service scope are defined by FibaCloud product and order information.
FIBACLOUD / VPS Servers
Tell us about your application, expected usage and operating requirements. Let’s bring the resource choices together.
