Back to Blog
team@tinypod.app

Understanding Cloud Computing: IaaS vs PaaS vs SaaS

Break down the cloud computing models. When to use IaaS, PaaS, or SaaS — and how self-hosting fits into the picture.

cloudiaaspaassaaseducation

Cloud Computing Models


IaaS (Infrastructure as a Service)

You get virtual machines, storage, and networking. You manage everything on top.


Examples: AWS EC2, DigitalOcean Droplets, Hetzner Cloud, Vultr.


PaaS (Platform as a Service)

You get a platform to deploy applications. The provider manages the infrastructure.


Examples: Heroku, Railway, Fly.io, Render, TinyPod.


SaaS (Software as a Service)

You get a complete application. No deployment, no management.


Examples: Gmail, Slack, Notion, GitHub.


The Spectrum


  • IaaS: Most control, most responsibility
  • PaaS: Balance of control and convenience
  • SaaS: Least control, least responsibility

    • How Self-Hosting Fits


    Traditional self-hosting is DIY IaaS: rent a VPS, install everything yourself.


    TinyPod is PaaS for self-hosted software: you pick the app, we handle the infrastructure.


    When to Use What


    Use SaaS When

  • You need it to work immediately
  • You don't have custom requirements
  • Data privacy isn't a concern

    • Use PaaS When

  • You want to deploy apps without managing servers
  • You want the benefits of self-hosting without the ops work

    • Use IaaS When

  • You need full control over the stack
  • You have custom infrastructure requirements
  • You have the skills and time to manage everything

    • Cost Comparison


    For a single service like Gitea:

  • IaaS: $5/mo VPS + your time to set up and maintain
  • PaaS: $5-10/mo, no maintenance
  • SaaS (GitHub): Free for small teams, scales with usage

    • The hidden cost of IaaS is your time. The hidden cost of SaaS is vendor lock-in.