ChatGPT answers, unedited

For a hobbyist blog that mixes static pages (posts, images, CSS/JS) with dynamic content (comments, APIs, search, user accounts, etc.), I’d prioritize simple pricing and low operational overhead over raw cloud power.

My shortlist

1. DigitalOcean is probably the sweet spot.
A $6/month Basic Droplet gives you 1 vCPU, 1 GB RAM, 25 GB SSD and 1,000 GiB of transfer; DigitalOcean specifically describes Basic Droplets as suitable for low-traffic sites, blogs and CMSs. www.digitalocean.com

You could run something like:

Nginx
 ├── Static blog files
 ├── Node/Python/Ruby application
 └── PostgreSQL/SQLite

That makes it particularly good for learning how web applications actually work.

2. AWS Lightsail is the easiest AWS option.
The entry Linux plan is $5/month and bundles 0.5 GB RAM, 2 vCPUs, 20 GB SSD and 1 TB transfer, with a straightforward management console and one-click SSH. aws.amazon.com

I'd choose Lightsail over ordinary EC2 if your primary goal is "I want AWS without having to learn AWS infrastructure first."

3. DigitalOcean App Platform is attractive if you don't want server administration.
It's a managed application platform with a $0 starting tier, so you can deploy an application without maintaining the underlying VM yourself. www.digitalocean.com

What I'd personally do for a hobby blog

If you're comfortable learning a little Linux:

Cloudflare Pages → static frontend → DigitalOcean $6 Droplet → dynamic API/database

Or, for maximum simplicity:

DigitalOcean Droplet → everything

The second option is surprisingly capable for a small personal blog and gives you a very understandable architecture. You can later split the database, CDN, or application server out as the site grows.

One caveat: with a self-managed VPS, you become responsible for OS updates, backups, security, HTTPS, and monitoring. Managed platforms cost a little more in some cases but can be worth it if you want to spend your hobby time writing rather than administering servers.

DigitalOcean Droplet pricing · AWS Lightsail pricing

If you tell me whether your blog is WordPress, Hugo/Jekyll, Next.js, Python/Django, Node/Express, or something else, I can recommend the cheapest architecture for that particular stack.

For a hobbyist blog that mixes static pages (posts, images, CSS/JS) with some dynamic features (comments, contact forms, APIs, personalized content), I’d prioritize platforms that are cheap at low traffic and don't require much server administration.

My picks

1. Cloudflare Pages + Workers — best value

This is probably what I'd choose for your use case. Static assets can be hosted essentially for free, while Workers handles things such as an API endpoint, contact form, RSS generation, or dynamic page logic. The current Workers free tier includes 100,000 requests/day, and the paid plan starts at $5/month, with 10 million requests and 30 million CPU milliseconds included. developers.cloudflare.com

The tradeoff is that Cloudflare's ecosystem has a somewhat steeper learning curve than traditional hosting.

2. Render — easiest to understand

Render is particularly friendly if you already have a GitHub repository: connect the repo, choose static site or web service, and deploy. Its free tier covers static sites and small web services; free web services sleep after 15 minutes of inactivity, so the first request after a period of inactivity can be slow. render.com

It's a nice choice if your dynamic portion is a conventional Node, Python, Go, etc. API rather than a collection of serverless functions.

3. AWS Lightsail — best if you want a "real server"

Lightsail is a good middle ground between traditional VPS hosting and the complexity of the wider AWS ecosystem. AWS provides preconfigured stacks and a simple management console, and the cheapest Linux plans start around $5/month. aws.amazon.com

You could run something like Nginx + a blog CMS + your own Node/Python application on one small instance. The downside is that you're responsible for more server maintenance, security updates, backups, etc.

What I'd actually build

For a hobby blog, I'd start with:

GitHub → Cloudflare Pages → Cloudflare Workers → database/storage only if needed

Keep the blog itself static whenever possible. Put only genuinely dynamic operations behind Workers. That gives you very little infrastructure to maintain and should keep costs at $0 for quite a while, with a predictable $5/month upgrade path if you outgrow the free limits. developers.cloudflare.com

If you'd rather learn conventional server administration, choose Lightsail. If you'd rather have the simplest deployment workflow, choose Render.

For a hobbyist blog that mixes static content (articles, images, pages) with dynamic features (comments, search, newsletters, user accounts, APIs, admin dashboards), the best value usually comes from not putting everything on a traditional server. A hybrid approach is often cheaper and easier.

Here are beginner-friendly options:

aws.amazon.comwhatpeopleuse.com

My recommendations by blogging style

1. Mostly articles, photos, and occasional interactive features

Best stack:

• Static site generator (Astro, Hugo, Jekyll, etc.)
• Host on Cloudflare Pages
• Add dynamic pieces through:
  • serverless functions
  • hosted databases
  • third-party services (comments, newsletters, analytics)

Why:

• Almost no server maintenance
• Very cheap
• Fast globally
• Great fit for hobby blogs

toolchew.com

2. WordPress or Ghost-style blog

Best stack:

• A small VPS
• Managed database if you prefer less maintenance

Good beginner choices:

• DigitalOcean Droplet
• Amazon Lightsail

Advantages:

• One machine runs everything
• Easy backups
• Familiar software ecosystem

Trade-off:

• You handle updates, security, and monitoring.

aws.amazon.comwhatpeopleuse.com

3. A custom blog with code (Python, Node.js, Go, etc.)

Best stack:

• Frontend: static hosting
• Backend: app platform

Beginner-friendly choices:

• Render for deploying apps from Git repositories
• Fly.io for lightweight server deployments

This avoids learning Linux administration immediately.

bootstrap.build

A practical low-cost setup I’d suggest for a hobby blogger

Starter setup (~$0–$10/month):

• Blog pages → Cloudflare Pages
• Images → object storage or CDN
• Comments → hosted commenting service
• Newsletter → email provider
• Dynamic API → serverless functions or Render
• Database → free/low-cost managed database

This scales nicely without paying for an always-running server.

When a small VPS is worth it

Choose a VPS if you want:

• WordPress
• Ghost
• full database control
• self-hosted analytics
• custom background jobs
• learning Linux/cloud administration

A $5–$10/month VPS can comfortably run a personal blog with moderate traffic. DigitalOcean is popular among beginners because of its documentation, while cheaper VPS providers can offer more hardware for the money but may require more technical comfort. aws.amazon.comwhatpeopleuse.com

Simple decision guide

• I want to write posts and avoid maintenance → Cloudflare Pages
• I want WordPress/Ghost → DigitalOcean or Lightsail
• I want to learn cloud engineering → Oracle Cloud free tier or a small VPS
• I want custom dynamic features → Cloudflare Pages + Functions or Render
• I expect only a few hundred visitors/month → avoid overbuilding; free tiers are often enough

For most hobby bloggers in 2026, a static-first architecture with small dynamic add-ons gives the best combination of cost, speed, and simplicity.

For a hobbyist blog that mixes static pages with some dynamic functionality—comments, contact forms, APIs, personalized content, etc.—I’d prioritize platforms that let you start essentially free and add compute only when you need it.

My picks

1. Cloudflare Pages + Workers — best overall value

For a hobby blog, this is probably where I'd start. Pages gives you static hosting with a $0 tier, unlimited static requests and bandwidth, while Workers provides serverless compute for dynamic pieces. The current Workers free tier includes 100,000 requests/day; the paid plan starts at $5/month and includes substantially higher allowances. pages.cloudflare.com

It's particularly attractive if your blog is something like:

Markdown posts → static site generator → Cloudflare Pages
Contact form/API/search → Cloudflare Worker
Small bits of state → KV/Durable Objects/database

The downside is that Cloudflare's ecosystem can take a little more learning than a traditional hosting provider.

Cloudflare Pages

2. Render — easiest if you want a conventional backend

Render is a nice choice if you'd rather think in terms of "here's my Python/Node/Ruby app" than serverless functions. It supports Node.js, Python, Ruby, Go, Rust, Elixir, and Docker, and offers static sites, web services and managed Postgres. render.com

It also has free instances for static sites and web services. The catch is that free web services spin down after 15 minutes without inbound traffic, so the first request after inactivity can be slow. render.com

Render

3. AWS Lightsail — best if you want to learn servers

If part of the hobby is learning Linux, Nginx, Docker, databases, etc., Lightsail is compelling. Its smallest Linux VPS is currently $5/month, with 0.5 GB RAM, 2 vCPUs, 20 GB SSD and 1 TB transfer. render.comrender.comaws.amazon.com

It's more hands-on, though—you become responsible for considerably more of the server administration.

Amazon Lightsail

What I'd choose

For a personal hobby blog, I'd rank them:

Cloudflare Pages + Workers > Render > Vercel/Netlify > Lightsail

If you want the least maintenance, choose Cloudflare or Render.

If you want to learn cloud/server administration, choose Lightsail.

If your blog is built with Next.js, Vercel becomes much more attractive.

And if the site is 95% static, don't pay for an always-running VM at all—put the static content on a free static host and use serverless compute only for the handful of dynamic operations. That can keep a hobby blog at $0/month for quite a while. pages.cloudflare.com

For a hobbyist blog with a mix of static pages and some dynamic functionality—comments, contact forms, an API, a small database, etc.—I’d prioritize simple pricing and low operational overhead over raw compute power.

My picks

1. DigitalOcean App Platform — best overall for a hobbyist

You can host static sites for free, deploy directly from GitHub/GitLab, get HTTPS and CDN support, and move to a paid application starting at $5/month when you need server-side functionality. www.digitalocean.com

The big advantage is that you don't have to maintain a Linux server, install updates, configure Nginx, etc. That's particularly attractive if blogging is the hobby rather than server administration.

2. Amazon Lightsail — best if you want to learn traditional hosting

Lightsail is essentially a simplified VPS. The entry Linux instance is $5/month, with 0.5 GB RAM, 2 vCPUs, 20 GB SSD and 1 TB transfer. docs.aws.amazon.com

It also has ready-made blueprints for things such as WordPress, Ghost, Node.js, Django, Nginx and LAMP, making it considerably easier than starting with EC2. docs.aws.amazon.com

I'd choose this if you want the experience of actually managing your own web server.

3. Cloudflare Workers — best for a modern static + dynamic architecture

If your blog is mostly static, you can put the static content on Cloudflare and use Workers for small dynamic endpoints. The Workers free plan provides a useful amount of serverless compute, while the paid plan starts at $5/month and has no additional egress/bandwidth charge. developers.cloudflare.com

This is excellent for things like:

• /api/comments
• contact forms
• RSS generation
• authentication
• small database-backed features
• personalized responses

The tradeoff is that serverless concepts can be somewhat less intuitive to a beginner than "here's my Linux server."

One particularly cheap setup

For a hobby blog, I'd seriously consider:

Static frontend → Cloudflare Pages/Workers → small managed database

rather than paying for a permanently running VM.

If you want a more conventional setup:

DigitalOcean App Platform → application + database

is probably the least frustrating starting point.

And if learning Linux/server administration is part of the hobby, go with Lightsail. Its predictable $5/month entry point and preconfigured applications make it unusually approachable for a VPS. docs.aws.amazon.com

Bottom line:

• 🥇 Easiest: DigitalOcean App Platform
• 💰 Cheap + traditional: Amazon Lightsail
• ⚡ Best modern serverless option: Cloudflare Workers
• 🛠️ Most control per dollar: DigitalOcean Droplet

If you tell me what you're using for the blog (e.g. Hugo/Jekyll + Python/Node backend, WordPress, Astro/Next.js, etc.), I can narrow this down to a specific architecture and likely monthly cost.

For a hobbyist blog that mixes static pages with some dynamic functionality—comments, a small API, contact forms, RSS generation, analytics, etc.—I’d prioritize simplicity and predictable costs over raw cloud power.

My picks

1. DigitalOcean Droplet — best overall for a hobbyist

A $4/month Basic Droplet gives you a tiny VM; the $6/month option provides 1 GB RAM, 1 vCPU, 25 GB SSD and 1,000 GiB transfer. DigitalOcean explicitly describes its Basic Droplets as suitable for low-traffic websites, blogs, CMSs and small databases. www.digitalocean.com

You could run:

• Nginx/Caddy
• Hugo/Astro/Eleventy-generated static content
• WordPress or Ghost
• Node/Python/PHP backend
• SQLite or a small PostgreSQL database
• cron jobs

The downside is that you're responsible for server maintenance, security updates and backups.

2. Google Cloud Run — best if the dynamic part is small

Cloud Run is particularly attractive if your blog is mostly static but occasionally invokes a backend. It bills based on actual resource usage and automatically scales instances, including scaling down when there isn't traffic. Google currently provides a monthly free tier including 240,000 vCPU-seconds and 450,000 GiB-seconds of memory. cloud.google.com

For example:

Static site → CDN/hosting → Cloud Run API → database

That's potentially extremely cheap for a personal blog, although Google's ecosystem is more complicated than DigitalOcean's.

3. AWS Lightsail — best if you want AWS without AWS complexity

Lightsail is essentially AWS's beginner-oriented VPS offering. It bundles CPU, RAM and SSD into predictable plans and includes conveniences such as DNS management, a static IP and browser-based SSH. aws.amazon.com

I'd choose it over ordinary EC2 if your goal is "I want to learn AWS, but I don't want to learn 25 AWS services just to host my blog."

4. Azure Static Web Apps — excellent for static-first blogs

If the dynamic component can be handled through APIs/Azure Functions, this is worth considering. Azure's Free plan includes web hosting, GitHub integration, globally distributed static content, SSL and managed APIs via Azure Functions. learn.microsoft.com

What I'd actually build

For your use case, I'd probably start with:

Astro/Hugo/Eleventy → DigitalOcean $4–6/month Droplet → Caddy → small Node/Python API

That gives you a very understandable architecture and a predictable bill. DigitalOcean's current Droplet pricing is particularly hobby-friendly because of its monthly caps and straightforward VM model. www.digitalocean.com

If you expect the dynamic portion to be very intermittent, I'd instead go:

Static hosting → Cloud Run API

That can be cheaper because you're not paying for an always-running VM. cloud.google.com

Bottom line:

• 🥇 Easiest all-in-one: DigitalOcean Droplet
• 💰 Potentially cheapest for sporadic dynamic requests: Google Cloud Run
• ☁️ Best beginner route into AWS: Lightsail
• 🪶 Best static-first/serverless setup: Azure Static Web Apps

If you tell me whether you're thinking WordPress, a static-site generator, or a custom blog (Python/Node/etc.), I can narrow this down to the cheapest sensible architecture.

For a hobbyist blog that mixes static pages (posts, images, CSS/JS) with some dynamic content (comments, contact forms, APIs, personalized widgets), I’d favor platforms that minimize server administration.

My top pick: Cloudflare Pages + Workers

For your particular use case, this is probably the sweet spot. Cloudflare Pages' free tier provides unlimited static requests and bandwidth, while Workers gives you serverless compute for dynamic functionality. pages.cloudflare.comwww.cloudflare.com

You could structure it like:

Static

• Markdown blog posts → generated HTML
• Images/CSS/JavaScript → Pages
• GitHub → deployment source

Dynamic

• Contact form → Worker
• Comments → Worker + database
• RSS/API endpoints → Worker
• Small personalized features → Worker

The Workers free tier currently allows 100,000 requests/day, and the paid tier starts at $5/month, including 10 million requests/month and 30 million CPU milliseconds. www.cloudflare.com

That's particularly attractive for a hobby site because you aren't paying for an always-running server when nobody is visiting.

Best if you want to learn Linux: DigitalOcean

DigitalOcean Droplets are excellent if part of the hobby is learning how web servers actually work.

The smallest Basic Droplet is currently $4/month, with 512 MiB RAM, 1 vCPU, 10 GB SSD, and 500 GiB transfer. DigitalOcean explicitly lists low-traffic websites and blogs among the intended workloads. www.digitalocean.com

You could run:

Nginx + static site + Node/Python/PHP + SQLite/PostgreSQL

The tradeoff is that you become responsible for OS updates, security, backups, configuring the web server, etc.

A nice middle ground: DigitalOcean App Platform

If you want something more managed than a VPS but still want conventional application hosting, DigitalOcean's App Platform is worth considering. DigitalOcean currently lists it as starting at $0/month, with managed infrastructure and automatic scaling. www.digitalocean.com

What I'd choose

For a hobby blog, I'd rank them:

1. Cloudflare Pages + Workers — cheapest and least maintenance
2. DigitalOcean App Platform — good managed middle ground
3. DigitalOcean Droplet — best if learning server administration is part of the fun
4. AWS Lightsail — reasonable, but I'd choose DigitalOcean for a first VPS
5. Google Cloud — powerful, but more complexity than a small blog needs

If your goal is "I want to blog, not become a cloud administrator," use Cloudflare Pages + Workers. If your goal is "I want my blog to be an excuse to learn Linux, Docker, Nginx, databases, and deployment," get the $4 DigitalOcean Droplet.

If you tell me whether your blog is WordPress, Hugo/Jekyll/Astro, or a custom app, I can narrow this down to the cheapest sensible architecture.

For a hobbyist blog that mixes static pages (posts, images, CSS/JS) with dynamic content (comments, APIs, dashboards, a small database), I’d prioritize simplicity and predictable costs.

My recommendation

Start with DigitalOcean App Platform if you don't want to learn server administration. It can host static sites and applications without you managing the underlying infrastructure; DigitalOcean says its static-site hosting supports three free static sites, while its basic App Platform plan starts at $5/month. www.digitalocean.com

If you're happy to learn a little Linux, a $4–$6/month DigitalOcean Droplet gives you much more control. A small Droplet can run your blog, web server, application, and even a small database on one machine. DigitalOcean specifically positions its Basic Droplets for low-traffic websites, blogs, CMSs, and small databases. www.digitalocean.com

Cloud Run is attractive if your dynamic portion is intermittent. You pay for actual compute usage rather than keeping a VM running continuously, and Google currently provides a monthly free tier of 240,000 vCPU-seconds and 450,000 GiB-seconds of RAM usage for Cloud Run. cloud.google.com

A practical hobbyist setup

I'd probably use:

Static content → inexpensive static hosting/CDN
Dynamic API → Cloud Run or App Platform
Database → managed database only when you actually need one

That keeps the blog cheap while avoiding the operational burden of maintaining a database and server from day one.

If your main goal is learning cloud infrastructure, choose a Droplet. If your goal is writing/blogging with minimal maintenance, choose App Platform or a static/Jamstack platform with serverless functions.

For a hobbyist blog that mixes static pages (posts, images, CSS/JS) with some dynamic functionality (comments, contact forms, APIs, search, etc.), I’d prioritize low operational overhead and predictable costs over raw compute power.

My picks

1. Cloud Run — best overall for a modern hobby project

If your dynamic component can be packaged as a container (Node.js, Python, Go, etc.), Cloud Run is particularly attractive. It scales down when there's no traffic, and Google currently provides a substantial always-free allowance: 240,000 vCPU-seconds, 450,000 GiB-seconds, and 2 million requests per month under the applicable pricing model. cloud.google.com

That makes it a great match for a blog where traffic is sporadic. You can put your static content on a static host/CDN and use Cloud Run only for the dynamic pieces.

2. Lightsail — easiest if you want a conventional server

Lightsail is probably the least intimidating choice if you'd rather have a small Linux server and install your blogging software yourself. AWS describes it specifically as an easy way to get started with websites and web applications, with VPS, storage, DNS, backups, and related components packaged into a simpler interface. docs.aws.amazon.com

Current Linux plans start at $5/month for 0.5 GB RAM, with a $7/month 1-GB option and $12/month 2-GB option. docs.aws.amazon.com Lightsail even provides application templates for things like WordPress, Ghost, Django, Node.js, and LAMP. docs.aws.amazon.com

3. Cloudflare Workers — excellent for "static + tiny bits of dynamic"

If your blog is generated with something like Hugo, Astro, Eleventy, or Jekyll and your dynamic requirements are modest—contact forms, small APIs, personalization, counters, etc.—Workers can keep the architecture extremely lightweight.

What I'd actually build

For a hobby blog, I'd start with:

Static site generator → CDN/static hosting → Cloud Run for dynamic endpoints → managed database only if actually needed

That avoids paying for an always-running VM just so your blog can respond to the occasional visitor.

If you want to learn server administration, choose Lightsail instead. If you just want the blog to be cheap and require very little maintenance, choose Cloud Run + static hosting.

One caution: "free" cloud tiers aren't necessarily a zero-risk $0 bill—egress, databases, storage, and other ancillary services can still generate charges. Set billing alerts before experimenting.

For a hobbyist blog that mixes static pages with some dynamic features—comments, contact forms, search, small APIs, RSS processing, etc.—I'd prioritize platforms that don't require you to maintain a server.

My pick: Cloudflare

For your particular use case, Cloudflare Pages + Workers is probably the sweet spot. Static assets are free and unlimited, while dynamic Pages Functions are billed as Workers. The free Workers plan has a limited daily allowance, and the paid plan starts at $5/month. developers.cloudflare.com

It also gives you a natural progression:

Start:

• Static site generator → Pages
• Git repository → automatic deployments
• Contact form/search/API → Workers
• Small database → D1
• Images/files → R2

Later: move more of your application logic into Workers without having to administer a Linux server. Cloudflare specifically supports full-stack applications with static assets, APIs, and server-side rendering. developers.cloudflare.com

Cloudflare Workers pricing

If you want to learn "real servers": Lightsail

AWS Lightsail is a good alternative if part of the hobby is learning how a conventional web server works. The cheapest plan starts at $5/month, with predictable hourly billing up to the monthly maximum. docs.aws.amazon.com

You could run WordPress, Ghost, a Node/Python app, or your own Nginx + application stack. The downside is that you become responsible for OS updates, security, backups, and server configuration.

Amazon Lightsail pricing

Cloud Run is great if you like containers

Google Cloud Run is particularly attractive if your dynamic portion is a Dockerized application. It scales based on requests rather than requiring an always-running VM, and currently includes monthly free usage such as 240,000 vCPU-seconds and 450,000 GiB-seconds. cloud.google.com

The tradeoff is that Google Cloud has a steeper learning curve than Cloudflare.

Google Cloud Run

DigitalOcean if you want simplicity + a VPS

DigitalOcean Droplets are straightforward virtual machines and are excellent for learning Linux, Docker, Nginx, databases, and deployment. But unlike serverless platforms, you pay while the VM exists—even if you've powered it off. docs.digitalocean.com

DigitalOcean Droplets pricing

Bottom line: I'd choose Cloudflare Pages/Workers for a hobby blog where keeping the bill near $0 matters. Choose Lightsail or DigitalOcean if learning server administration is itself part of the hobby. Choose Cloud Run if you're already comfortable with Docker or want to learn container-based deployment.

For a hobbyist blog that mixes static pages with some dynamic functionality—comments, a small API, database-backed posts, RSS generation, etc.—I'd prioritize predictable pricing and simplicity over raw cloud power.

My picks

1. Amazon Lightsail — best overall beginner choice

Lightsail is specifically designed to make launching websites and web applications easier, with VPS instances, storage, DNS, backups, databases, and other pieces presented in a relatively simple interface. Its smallest Linux plan is currently $5/month, with 0.5 GB RAM, 2 vCPUs, 20 GB SSD and 1 TB transfer. docs.aws.amazon.com

For a blog, that's a very comfortable starting point. You could run something like:

Nginx → your blog/app → SQLite or PostgreSQL

and learn the fundamentals without diving immediately into the full AWS ecosystem.

2. DigitalOcean — best for learning

DigitalOcean's Droplets are straightforward Linux VMs, and its documentation is particularly approachable. Billing is granular, and you can destroy a VM when you're finished experimenting. docs.digitalocean.com

I'd choose this if part of the hobby is learning how servers actually work.

3. Google Cloud Run — best if you don't want server administration

If your dynamic portion can be packaged as a container, Cloud Run is particularly attractive. You deploy your application and Google handles the underlying servers. Google currently lists 2 million requests/month in its free tier. cloud.google.com

This is a great architecture for:

• Static blog hosted separately
• Small dynamic API on Cloud Run
• Managed database/storage only when needed

The downside is that cloud concepts and usage-based billing can be more complicated than a $5 VPS.

4. Google Compute Engine — best free/experimental option

Google currently offers an Always Free allowance for one e2-micro VM, subject to eligibility and the specified regions/quotas, plus 30 GB standard persistent disk and limited outbound traffic. cloud.google.com

That's potentially excellent for a tiny personal blog, but it's not my first recommendation for a beginner because Google Cloud's overall interface and billing model are considerably more complex than Lightsail/DigitalOcean.

5. Hetzner — best price/performance

If you're comfortable doing a little more Linux administration, Hetzner is worth considering. Its pricing is generally aggressive, although its June 2026 price adjustment means you should check the current plan pricing rather than rely on older blog posts. docs.hetzner.com

What I'd actually do

For your use case, I'd start with Lightsail at $5/month if you want one simple machine running everything.

If you want to learn modern deployment, I'd instead use:

Static frontend → CDN/static hosting
Dynamic features → Cloud Run
Database → SQLite initially, managed PostgreSQL only when necessary

That second approach can be extremely cheap at hobby scale because you're not paying for an always-running VM.

Bottom line:

• 🥇 Easiest: Lightsail
• 🥈 Best for learning servers: DigitalOcean
• 🥉 Best serverless/container approach: Cloud Run
• 💰 Cheapest experimentation: Google Cloud's free tier
• ⚡ Best raw value: Hetzner

For a hobbyist blog mixing static pages (posts, images, CSS/JS) with dynamic features (comments, contact forms, APIs, search, etc.), I’d prioritize simplicity and predictable costs over raw VM power.

1. Cloudflare Pages + Workers — my first choice

This is particularly attractive for your use case because static assets can be served essentially independently of your dynamic compute. Cloudflare says static asset requests are free and unlimited, while the Workers free plan includes limited dynamic execution; the paid plan starts at $5/month and includes 10 million requests and 30 million CPU milliseconds. developers.cloudflare.comdocs.aws.amazon.comcloud.google.comcloud.google.com

It's a good architecture for something like:

Static site generator → Cloudflare Pages/Workers → dynamic API → database

You don't have to maintain a Linux server, install security updates, configure Nginx, etc. Cloudflare also supports full-stack applications and server-side rendering through Workers. developers.cloudflare.com

Cloudflare Workers pricing

2. Amazon Lightsail — easiest traditional server

If you'd rather have the experience of running a conventional server—Ubuntu, Nginx, WordPress, Node.js, Python, etc.—Lightsail is arguably the friendliest entry point.

AWS explicitly positions Lightsail as an easy way to get started with websites and web applications, bundling VPS compute, storage, networking, DNS, backups, and other components into a relatively predictable package. docs.aws.amazon.com

The cheapest Linux/Unix instance is currently $5/month, with hourly billing up to the monthly maximum. docs.aws.amazon.com

Amazon Lightsail

I'd pick this if: you want to learn traditional server administration while keeping AWS complexity relatively low.

3. DigitalOcean Droplets — excellent DIY option

DigitalOcean is another good hobbyist choice if you want a small VPS and don't mind managing it yourself. Droplets are ordinary Linux VMs, billed by the second with a 60-second/$0.01 minimum. docs.digitalocean.com

It's especially nice for learning:

• Linux
• Docker
• Nginx/Caddy
• PostgreSQL
• Node/Python/PHP
• Git-based deployment

The downside is that you are responsible for more of the infrastructure than with Cloudflare or a managed platform.

DigitalOcean Droplets

4. Google Cloud Run — great if you like containers

If your dynamic portion is packaged as a Docker container, Cloud Run is compelling. Google currently lists 2 million requests/month in its free tier, and you pay based on actual usage beyond the free allocation. cloud.google.comcloud.google.com

It's less beginner-friendly initially than Lightsail because containers, IAM, projects, revisions, and Google Cloud's broader ecosystem introduce some concepts—but it's an excellent stepping stone toward more sophisticated deployments.

Google Cloud Run

5. Google Compute Engine — cheap, but more infrastructure than you need

Compute Engine gives you a conventional VM. Google currently offers a free tier covering one e2-micro instance, up to 30 GB of standard persistent disk and 1 GB/month outbound transfer, subject to the free-tier conditions. cloud.google.comcloud.google.com

It's a good learning environment, but for a hobby blog I'd generally choose Lightsail or DigitalOcean if I specifically wanted a VM.

What I'd choose

If you mostly want to blog:
Static-site generator + Cloudflare Pages/Workers. Very little server maintenance and excellent economics at hobbyist traffic levels.

If you want to learn Linux/server administration:
DigitalOcean Droplet or Lightsail.

If you want WordPress:
Lightsail is particularly appealing because you can run a conventional WordPress stack without assembling as much infrastructure yourself.

If you're building a custom app and already like Docker:
Cloud Run.

One useful rule: don't rent a continuously running VM just because you have a little dynamic content. If 95% of your blog is static, serverless functions/Workers can be substantially simpler and cheaper than maintaining an always-on server.

For a hobbyist blog mixing static pages with a little dynamic functionality—comments, a small API, contact forms, a CMS, etc.—I’d prioritize predictable pricing and simple deployment over the raw power of the cloud.

My picks

1. AWS Lightsail — best all-around beginner choice

Lightsail is specifically designed to make launching websites and web applications easier, bundling things like VPS instances, databases, DNS, storage, and backups into a relatively straightforward interface. Its cheapest plan is currently $5/month. docs.aws.amazon.com

It's particularly attractive if you want to run something like:

Nginx → WordPress/Astro/Next.js → small database

without learning the entire AWS ecosystem.

2. DigitalOcean Droplet — best if you want to learn Linux

A small Droplet gives you a conventional Linux server where you control practically everything. DigitalOcean bills CPU Droplets by the second, with a one-minute/$0.01 minimum, and includes a bandwidth allowance with each plan. docs.digitalocean.com

I'd choose this if you're comfortable following tutorials and want to learn Docker, Nginx, system administration, Git deployment, etc.

3. Google Compute Engine — best if minimizing compute cost is the priority

Google currently offers an Always Free e2-micro VM, subject to its eligibility, region, storage and networking limits. The free tier includes one e2-micro, up to 30 GB of standard persistent disk, and 1 GB/month of outbound transfer. cloud.google.com

The catch is that Google Cloud is substantially more complicated than Lightsail or DigitalOcean. It's a great learning platform, but probably not the most pleasant first cloud server.

4. Azure Container Apps — interesting if your dynamic content is containerized

Container Apps is serverless and can scale based on HTTP traffic/events, with consumption pricing based on resources used. azure.microsoft.com

It's more compelling when your blog is already Dockerized rather than when you're just starting out.

What I'd actually build

For a hobby blog, I'd probably avoid putting everything on a VM unless you want the server-management experience.

A cost-efficient architecture is:

Static frontend → static hosting/CDN
Dynamic features → serverless functions/container service
Database → small managed database or serverless database
Images → object storage

That lets the static portion handle most page views cheaply while you pay for compute only when dynamic functionality is actually used.

If you specifically want one simple server running the whole thing, though, Lightsail or DigitalOcean is the sweet spot. If your goal is learning cloud infrastructure, I'd pick DigitalOcean; if your goal is spending as little time as possible managing infrastructure, I'd pick Lightsail.

For a hobbyist blog that mixes static pages with some dynamic functionality—comments, a small API, contact forms, authentication, etc.—I'd prioritize predictable pricing and low operational overhead.

My picks

1. Lightsail — easiest all-around choice

If you want something that feels like "rent a small server and put my blog on it," Lightsail is probably the best starting point. AWS specifically positions it as an easy way to launch websites and web applications, with instances, storage, DNS, backups, and other components simplified into predictable pricing. The cheapest Linux plan is currently $5/month. docs.aws.amazon.com

You could run something like:

Nginx → WordPress/Hugo/Next.js → SQLite/PostgreSQL

It's also a nice stepping stone if you eventually want to learn more AWS.

2. Cloud Run — best if your "dynamic" part is small

For a modern blog, this is arguably the most economical architecture. Put the static frontend on a CDN/static host and run your dynamic component as a container on Cloud Run.

Cloud Run scales to zero, meaning you aren't charged for idle instances under request-based billing, and Google currently provides a substantial monthly free tier. cloud.google.com

This is particularly attractive for a hobby project that gets 100 visitors one day and 10 the next.

3. Azure Static Web Apps — excellent for mostly-static blogs

The Free plan is specifically intended for personal projects and includes globally distributed static hosting, SSL, GitHub integration, custom domains, and managed APIs through Azure Functions. learn.microsoft.com

For example:

GitHub → Static Web Apps → static blog

↘ Azure Function → database

That's a very low-maintenance setup.

4. DigitalOcean — best for learning traditional server administration

A Droplet gives you a conventional Linux VM, so you have complete control over the OS, web server, database, Docker, etc. DigitalOcean bills Droplets by the second with a 60-second minimum, and you continue paying while a Droplet is merely powered off—you need to destroy it to stop billing. cloud.google.comdocs.digitalocean.com

I'd choose this if learning Linux/server administration is part of the hobby, rather than simply wanting the blog online.

What I'd do for your use case

If your blog is 90% static and 10% dynamic, I'd start with:

Static site generator → Azure Static Web Apps → serverless function for dynamic features

or

Static site → CDN/static host + Cloud Run → small database

If you want one machine and minimal architectural complexity, choose Lightsail.

If you want to learn how servers actually work, choose DigitalOcean.

The key is not to rent a large VM just because you might eventually need one. For a hobby blog, scale-to-zero/serverless or a tiny $5-ish VPS is usually plenty.