Get a VPS.Your project, your rules.

A VPS is a virtual private server with its own operating system. It lets you host websites, applications, databases and processes. The physical hardware may be shared with other virtual machines; the type of resources and their availability depend on the plan.

The best VPS is the one that fits your workload, budget and ability to administer it. Compare CPU type, RAM, disk, location, backups, support and total cost. CubePath is worth considering if you want root access, NVMe and hourly billing. Test your application before you decide.

Define what you will run, where your users are and who will maintain the server. Then compare equivalent plans, including IP, transfer, backups, licences and taxes. A plan with more vCPU will not necessarily be faster for every application.

When you need to install your own services, run processes continuously, control versions or go beyond the limits of your current hosting. If you only have a simple website and prefer to hand off the server, managed hosting may be enough.

VPS describes a virtual machine. Cloud describes a way of delivering infrastructure and can include VPS, networking and other services. A dedicated server is a whole physical machine. A VPS plan with dedicated CPU is still virtual; it is not the same as renting the whole physical server.

Start from the real need. An affordable VPS can be enough for testing or lightweight services. For production, also weigh stability under load, recovery and administration time. The lowest price stops paying off if the plan limits your application or lacks services you need.

There is no universal figure. Measure concurrent processes, your database's memory, containers and traffic peaks. Leave headroom for the operating system, updates and backup jobs. A small application and a store with dynamic search can need very different resources.

Shared CPU usually fits variable workloads and tight budgets. Dedicated CPU reserves CPU capacity for sustained workloads. A high frequency CPU can help tasks limited by single-thread performance. Check the available instance families before you choose.

NVMe gives access to flash storage with low latency. It helps workloads with many reads and writes, but final performance also depends on the application, memory, database and the load on the environment. NVMe alone does not guarantee a fast website.

It cannot be worked out from RAM alone. Caching, dynamic requests, response size, queries and concurrent users all play a part. Run a representative load test and monitor response times, memory and CPU.

CubePath lets you upgrade to available plans in the same family and location from the panel. The upgrade restarts the machine and may take a few minutes of downtime. To move to a smaller plan, the documentation says to contact support to handle the migration. See how resizing works.

It can help if your current hosting runs out of resources. It does not automatically fix slow plugins, heavy images, missing caching or expensive queries. Find the bottleneck first and check the result after migrating.

CubePath deploys virtual machines in Barcelona, as well as Houston and Miami. Check plan availability in the panel. If your users are in Spain, Barcelona is a location worth evaluating with latency tests.

Measure latency from where your users are and from the services your application connects to. Geographic proximity is a guide, but network routes matter too. No single location is the fastest for every country in Latin America.

Yes. On Linux machines you can log in as root over SSH with the authentication you configure. CubePath also documents a browser console. Protect access and limit the permissions of the accounts you use for everyday work.

CubePath's Linux range includes distributions such as Ubuntu, Debian, AlmaLinux, Rocky Linux and Fedora. Check the versions available when deploying and pick one compatible with your software. Windows and ISO installs are available on dedicated servers, so confirm support and licences before buying if you need them.

Yes, on a compatible system and plan you can install your services with administrator access. Review requirements, data persistence, ports and updates. Keep public and internal access separate; publishing an API does not require exposing its database too.

Size by concurrent executions, data processed, automated browsers and additional services. If the model runs through an external API, inference happens at the provider and normally needs no GPU on the VPS. Running the model inside the server has different requirements. Keep processes under a service manager or containers and configure them to restart.

It depends on the plan, the IP and the extras. The selection on this page shows monthly reference prices in USD; check the current price and applicable taxes in the panel before deploying. The server cost does not automatically include licences or external APIs for the applications you install.

The deployment documentation offers IPv6 at no cost and IPv4 as an extra-cost option. The reference prices for the three plans shown here include one IPv4. If you change the configuration or add addresses, check the total before buying.

CubePath uses prepaid balance and hourly charges. A stopped VPS keeps billing for as long as it exists. To stop paying for the machine you have to destroy it, first keeping the data you need and checking any IPs or other resources that remain active. Read about billing.

The balance documentation states that hourly VPS has no minimum commitment. Destroying the machine stops its charge, but deletes its data. Floating IPs and other resources you keep may continue to bill. Also review automatic top-ups and the terms of additional services.

Every plan has a monthly transfer allowance. The deployment documentation states a charge of 2 USD per additional TB. Check the current conditions and your usage in the panel; the plan should not be read as unlimited traffic.

A verified account, available balance and a choice of region, plan, system and access. Check the payment methods enabled on your account. The documentation states a minimum top-up of 10 USD. Deploying the server and getting your application ready are separate steps.

Root access lets you or your team manage the system and applications. Do not assume that infrastructure support includes updates, optimisation or fixing errors in your software. If you need to hand off those tasks, agree the scope with CubePath before buying.

Automatic backups are optional. CubePath documents a 20% surcharge and configurable retention from 1 to 7 days. Review the settings and the total when enabling them. Also keep an external copy of critical data and test that you can restore it. See backups and restores.

No. DDoS protection helps against attacks that try to saturate the service. You also need to manage patches, access, firewall rules, secrets and the security of your applications. Backups help you recover data, but they do not replace those measures either.

Yes. Prepare a backup, set up a compatible environment, transfer the data and test the application before switching DNS. Plan a final sync if there are purchases or writes. If you need help with the migration, check its scope and cost with the team first.

You can set up several sites and services depending on resources and the software installed. For email, CubePath blocks outbound SMTP on ports 25 and 465 by default and documents port 587 for sending through an external provider. Check the unblock conditions and configure DNS and authentication correctly. See network conditions.

Review the contractual SLA, support channels, committed response times and the recovery procedure. Infrastructure availability alone does not guarantee your application's availability. If downtime has a big impact, design monitoring, backups and redundancy to match your project.