4. VPS vs managed hosting vs object storage

You know what servers, storage, and databases are. Now it is time to choose: when you are ready to put your project on the internet, which type of cloud service should you actually use? In this lesson you will compare three practical options — a VPS, managed hosting, and object storage — and learn when each one is the right tool.

Imagine three ways Abebe could rent space to sell his traditional Ethiopian textiles online:

1. Rent an empty warehouse — He gets four walls and a floor. He decides where to put the shelves, how to organise the stock, who gets a key, and he hires his own security guard. Maximum freedom, maximum responsibility.

2. Rent a ready-made shop unit in a mall — The mall provides electricity, cleaning, security, and a shopfront. Abebe brings his products and sets up his display. He cannot knock down walls, but he does not have to worry about the building.

3. Rent a safe deposit box at a bank — He does not run a shop at all. He just stores his most valuable textiles in a secure box and retrieves them when needed. Simple, cheap, built for one purpose only.

In the cloud, these three options map to:

• Empty warehouse → VPS (Virtual Private Server)

• Ready-made shop → Managed hosting / PaaS platform

• Safe deposit box → Object storage

A Virtual Private Server (VPS) is a slice of a powerful physical machine running in a data centre. The cloud provider manages the hardware; everything above the hardware — the operating system, the web server software, the database, the firewall — is your responsibility.

What you get with a VPS:

• Root access — you can install any software you like.

• A fixed allocation of CPU, RAM, and disk space.

• A public IP address so the world can reach your server.

• Full control over security settings, scheduled tasks, and networking.

Why choose a VPS?

Choose a VPS when you need full control: you want to run a custom stack, host multiple apps on one machine, configure the server exactly the way you want, or keep costs low by managing things yourself.

Why not a VPS?

You are responsible for every security patch, every system update, and every backup. If you forget to update a library and attackers exploit it, that is on you. A VPS is not right for developers who want to focus purely on their code without worrying about system administration.

Popular VPS providers available in Ethiopia: AletCloud (ETB billing, local data sovereignty), DigitalOcean, Linode, and Hetzner.

AletCloud is Ethiopia's own cloud platform — you can rent VPS instances, managed databases, and object storage, all billed in Ethiopian Birr. This is especially useful for businesses that must keep their data inside Ethiopia for regulatory or data-sovereignty reasons.

Managed hosting (often called a PaaS platform) takes the system-administration burden away from you. You push your code; the platform handles the rest — installing dependencies, starting the web server, applying security patches, load balancing, and even automatic restarts if your app crashes.

Examples of managed hosting platforms:

• Vercel and Netlify — designed for front-end and full-stack JavaScript apps; deploy by just connecting your GitHub repository.

• Render and Railway — deploy Node.js, Python, Ruby, or Go apps with a few clicks.

• AletCloud App Hosting — a managed platform option on Ethiopia's sovereign cloud.

• Heroku — one of the oldest and most beginner-friendly managed platforms.

What you give up:

• Fine-grained control over the server configuration.

• The ability to install arbitrary system software (most platforms only support certain runtimes).

• Sometimes higher cost at scale compared to a VPS you manage yourself.

Who should use managed hosting?

Beginners, small teams, and startups who want to go live quickly without hiring a DevOps engineer. Also ideal for agencies building many small client websites who cannot afford to babysit multiple VPS instances.

Example: Sara has built a small web app for her injera delivery business using Node.js. She does not know how to configure Linux, install Nginx, or set up SSL certificates. She pushes her code to Render in ten minutes and the platform handles everything — her site is live with HTTPS at no extra effort.

Object storage is not a place to run code — it is purely a place to store and serve files. You upload a file; it gets a unique URL; anyone (or any app) with that URL can download the file.

Object storage works like a giant, globally accessible drawer. You put files in, you take files out. There is no operating system to manage, no server to patch, no RAM or CPU to worry about. You pay per gigabyte stored and per gigabyte transferred.

Common uses of object storage:

• Course videos and images for a learning platform like Ethio Telecom Learn.

• Profile photos and product images for an e-commerce site.

• Software update files that thousands of users download.

• Database backups — a nightly backup file copied to object storage is cheap and reliable.

• Static website files (HTML, CSS, JavaScript) — some object storage services can serve a static website directly, with no server needed at all.

Examples of object storage services:

• Amazon S3 (the original, most widely used).

• Google Cloud Storage.

• Cloudflare R2 (no data-transfer fees — popular for high-traffic sites).

• AletCloud Object Storage (ETB billing, data stored inside Ethiopia).

Object storage is not right when:

You need to run code on the stored data in real time, or when your files must be mounted as a traditional file system (use block storage for that).

Three overlapping circles of cloud options: VPS (full control, more responsibility), managed hosting (balanced — platform handles infrastructure), and object storage (cheap, scalable, file-only).

Here is a direct comparison of the three options:

VPS

• What it is: A virtual machine you control completely.

• You manage: OS, web server, database, security, backups.

• Cost model: Fixed monthly fee (pay even when idle).

• Best for: Advanced developers, custom stacks, multiple apps on one machine, cost optimisation at scale.

• Not ideal for: Beginners who do not want to learn system administration.

Managed Hosting (PaaS)

• What it is: A platform that runs your code for you.

• You manage: Your application code only.

• Cost model: Often pay-per-usage or tiered plans; may have a generous free tier.

• Best for: Developers who want to focus on code, teams without DevOps expertise, quick prototypes.

• Not ideal for: Projects needing unusual system-level customisation.

Object Storage

• What it is: A file store accessible via a URL.

• You manage: Which files to upload; access permissions.

• Cost model: Pay per GB stored + per GB downloaded. Very cheap for large files.

• Best for: Videos, images, backups, downloadable files, static websites.

• Not ideal for: Running code or serving dynamic data.

Scenario

Almaz is launching a portfolio website. It contains only HTML, CSS, and some JavaScript — no backend server or database is needed. She wants the cheapest and simplest option. What should she use?

Lesson recap: • VPS — a virtual machine you control fully. Best when you need fine-grained control or want to run many apps on one machine. You manage the OS, security, and updates yourself. • Managed hosting (PaaS) — a platform that runs your code. Best when you want to focus on building features without managing servers. Examples: Vercel, Render, AletCloud App Hosting. • Object storage — a file store, not a server. Best for videos, images, backups, and static websites. You pay per GB, not per server. • Most real-world apps combine all three — use each tool for what it does best.

Check your understanding

1/7 · 81 XP

Which cloud option gives you full control over the operating system, web server software, and security patches?