Shared hosting or VPS?
Move for a specific reason.
A virtual private server gives an application its own operating system environment and an agreed allocation of resources. It also brings server maintenance responsibilities. A bigger server will not, by itself, fix slow database queries or an inefficient website.
Compare shared hosting first
Business websites and WordPress
A brochure website may work well on shared hosting. Consider a VPS when measured CPU or memory limits, concurrent visitors or required software are restricting the site. Check caching and application performance before paying for more capacity.
Applications, APIs and background jobs
Describe your PHP, Node.js or other runtime, database, scheduled tasks and workers. A Laravel application with a queue or a custom API may need a server configuration that a standard shared account cannot provide. Software compatibility must be checked in the proposal.
Several client websites
An agency may need separate hosting accounts, access permissions and control-panel licences. Include the number of sites and accounts in the brief. A single VPS remains a shared point of failure for the sites on it.
Size from evidence
What determines your VPS specification?
These are planning examples, not packages for sale. Send recent usage figures if you have them; if you do not, describe your busiest business activities and expected growth.
CPU and memory
Share peak CPU usage, memory usage and the number of simultaneous users or background jobs. A virtual CPU count alone does not guarantee an application response time. Leave room for the database, operating system, backups and traffic peaks.
Storage and data transfer
Count the website files, database, uploads, logs and retained backups. Include monthly traffic in GB or TB and expected growth. Confirm usable disk space, storage type and any transfer allowance or overage charge.
Location and access
Tell us where your users are, whether you need root or SSH access, and any data-location requirement. Hosting for a Ugandan business does not necessarily mean a server in Uganda. The proposed data centre, access level and operating system are confirmed before purchase.
Agree who does what
Managed VPS needs a defined scope.
“Managed” should describe actual work. Ask for the responsibilities below in writing so your team knows which tasks are included, which remain yours and which are charged separately.
Server and application maintenance
Identify who patches the operating system and control panel, configures the firewall, monitors services and responds to alerts. Separately agree responsibility for your application code, plugins, database tuning and software upgrades.
Backups and restoration
Agree what is backed up, how often, where copies are stored, how long they are retained and who tests restores. Ask about restore charges and recovery times. Disk redundancy or a server snapshot alone does not establish a complete recovery plan.
Licences and the renewal bill
Confirm cPanel or another control panel, account limits, software licences, IP addresses, setup, migration and support charges. Compare the renewal total as well as the first term, and check the currency and validity period of your quote.
Prepare your enquiry
Bring a brief we can price.
Send your application type, software versions, current usage, main user locations, budget and launch date. Include your preferred maintenance window and any backup or recovery requirements. Do not send passwords in an enquiry.
Request a VPS hosting proposal
Test before changing DNS
A migration plan should cover a staging check of the website or application, database, SSL, scheduled jobs and outgoing email. Agree how new data is synchronised, when traffic changes and how to return to the old service if validation fails.
Keep the right services separate
Moving a website does not require moving every service at once. Identify your domain registrar, DNS provider and email host first. Preserve the email routing records when only the website is moving.
Compare business email options
Read the planning guides
Compare shared hosting, VPS and cloud, work through the hosting selection checklist, and prepare with our website migration guide.
Review before committing
Your written proposal should name the configuration, management scope, location, migration work, billing term and renewal basis. Availability and suitability are confirmed before an order; this page does not reserve infrastructure.
Made for your next step
Power is only part of the decision.
The right server depends on your application, traffic and the team looking after it. Agree the operational details before moving a live service.
Application requirements
Bring your software versions, database needs and expected traffic.
Management responsibilities
Agree who handles updates, security, monitoring and incident response.
Recovery planning
Confirm backup schedules, retention and the steps to restore a service.
Connect your services
Your domain, website and email can work together. Compare the services you need before placing an order.
Check domain availability and annual registration prices for your business name.
Use your domain for your team's email and discuss mailbox requirements before moving.
Review storage, included features and annual prices for a standard business website.
Explore the architecture and billing model for an application with changing capacity needs.