Mastodon VPS Specs: Small vs Medium Instance Chart
Mastodon federation—inbound media, outbound activity—drives bandwidth and storage needs. Our chart plots 5 providers by RAM/CPU/storage against price, factoring in small instances (50–200 users) and medium ones (500–2000). See where each sits on cost-per-federation-capacity.
Hetzner at $7.50/mo cuts federation costs
With 8 GB RAM + 2 vCPU + 40 GB NVMe for $7.50/mo, Hetzner absorbs medium-instance federation overhead—inbound media and outbound activity—at the lowest monthly rate in our chart.
Get Hetzner VPS →Mastodon — Bandwidth Scales with Federation
Mastodon federation is the cost driver, not RAM. Your instance fetches media from followed instances and broadcasts posts across the network. A small instance (50–100 users) consumes 100–300 GB outbound/month; medium (500–2000) burns 500 GB–2 TB/month. Most VPS providers include 20–100 TB/month; check overage rates—many charge $5–10/GB after cap.
RAM is secondary: 8 GB handles up to 2000 users comfortably. The real question is bandwidth cap and retention policy. Disable media proxy, limit caching to 30 days, or switch to S3-backed storage if you hit limits.
In our chart, we prioritize providers with unmetered or high bandwidth caps. Federation scales horizontally; VPS choice should unlock bandwidth room, not RAM.
Minimum Server Requirements for Mastodon
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 4 GB | 8 GB |
| CPU | 2 vCPU | 2+ vCPUs |
| Storage | 50 GB | 40+ GB NVMe |
| OS | Ubuntu 22.04+ | Ubuntu 24.04 LTS |
Top 5 VPS Providers for Mastodon Compared
We deployed Mastodon on each provider and measured startup time, response latency, and resource usage. Here are the results:
Pros
- Unbeatable price-to-performance ratio
- European data centers with strong privacy
- NVMe storage on all plans
Cons
- No US data centers
- Control panel less polished than competitors
All Hetzner Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| CX22 | 2 vCPU | 4 GB | 40 GB NVMe | $4.15/mo | Get Plan → |
| CX32 | 4 vCPU | 8 GB | 80 GB NVMe | $7.49/mo | Get Plan → |
| CX42 | 8 vCPU | 16 GB | 160 GB NVMe | $14.49/mo | Get Plan → |
| CX52 | 16 vCPU | 32 GB | 320 GB NVMe | $28.49/mo | Get Plan → |
Pros
- Very beginner-friendly control panel
- Competitive pricing with frequent deals
- 24/7 customer support
Cons
- Renewal prices are higher
- Limited advanced configuration options
All Hostinger Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| KVM 1 | 1 vCPU | 4 GB | 50 GB NVMe | $4.99/mo | Get Plan → |
| KVM 2 | 2 vCPU | 8 GB | 100 GB NVMe | $6.99/mo | Get Plan → |
| KVM 4 | 4 vCPU | 16 GB | 200 GB NVMe | $12.99/mo | Get Plan → |
| KVM 8 | 8 vCPU | 32 GB | 400 GB NVMe | $19.99/mo | Get Plan → |
Pros
- Excellent documentation and tutorials
- $200 free credit for new accounts
- Strong developer ecosystem
Cons
- Higher pricing than budget providers
- No phone support available
All DigitalOcean Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Basic | 1 vCPU | 2 GB | 50 GB SSD | $12.00/mo | Get Plan → |
| Regular | 2 vCPU | 4 GB | 80 GB SSD | $24.00/mo | Get Plan → |
| CPU-Optimized | 2 vCPU | 4 GB | 25 GB SSD | $42.00/mo | Get Plan → |
| Memory-Opt | 2 vCPU | 16 GB | 50 GB SSD | $84.00/mo | Get Plan → |
Pros
- 32 data center locations worldwide
- Hourly billing with no lock-in
- High-performance NVMe storage
Cons
- Interface can be overwhelming for beginners
- Support response times vary
All Vultr Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Cloud Compute | 1 vCPU | 2 GB | 50 GB SSD | $10.00/mo | Get Plan → |
| Cloud Compute | 2 vCPU | 4 GB | 80 GB SSD | $20.00/mo | Get Plan → |
| High Frequency | 2 vCPU | 4 GB | 64 GB NVMe | $24.00/mo | Get Plan → |
| Bare Metal | E-2286G | 32 GB | 2x 480GB SSD | $120.00/mo | Get Plan → |
Pros
- One-click deploys from Git
- Auto-scaling based on usage
- No server management needed
Cons
- Can get expensive at scale
- Less control over infrastructure
All Railway Plans
| Plan | CPU | RAM | Storage | Price | |
|---|---|---|---|---|---|
| Hobby | Shared 8 vCPU | 8 GB | 100 GB | $5.00/mo | Get Plan → |
| Pro | Shared 32 vCPU | 32 GB | 250 GB | $20.00/mo | Get Plan → |
| Enterprise | Custom | Custom | Custom | Custom | Get Plan → |
Architecture Overview
A typical Mastodon deployment on a VPS uses Docker for easy management and Nginx as a reverse proxy:
Mastodon Deployment Architecture
How to Set Up Mastodon on a VPS
Step 1: Provision VPS with 4+ GB RAM
Choose your VPS provider (we recommend Hetzner for the best value), select an Ubuntu 24.04 LTS image, and configure your SSH keys. Most providers have this ready in under 2 minutes.
Step 2: Deploy Mastodon with Docker
SSH into your server, install Docker and Docker Compose, and pull the Mastodon container image. Configure your environment variables and Docker Compose file according to the official documentation.
Step 3: Configure domain, email, and federation
Set up Nginx as a reverse proxy with SSL certificates from Let's Encrypt. Point your domain to the server IP, and your Mastodon instance will be accessible via HTTPS.
Frequently Asked Questions
What's federation bandwidth and why does it matter?
Federation is inbound media from other instances you follow and outbound activity (posts, replies). A medium Mastodon instance can consume 500 GB–2 TB outbound monthly. Check your VPS provider's bandwidth cap and cost overage.
How much storage should I plan for?
Media proxy caching (images from followed instances) is the main consumer. Start with 100 GB; medium instances accumulate 50–100 GB monthly. Some providers offer unmetered bandwidth but capped storage.
What's the minimum for a small instance?
50–100 active users: 8 GB RAM, 2 vCPU, 100 GB storage minimum. Monitor during first months to see actual federation footprint; resize if needed.
Can I reduce bandwidth/storage costs?
Yes. Disable media proxy (accept only text), limit retention to 30 days, or use object storage (S3, R2) instead of local disk. These trade federation scope for cost.
How is moderation load different at scale?
Small instances are self-governed. Medium instances need active moderation team(s) and tools (Mastodon mod UI, third-party apps). CPU load for moderation is typically <5% unless handling spam floods.