
This article provides a guide demonstrating how to deploy Phanpy on AlmaLinux VPS.
What is Phanpy?
Phanpy is a modern alternative web frontend for Mastodon and compatible Fediverse platforms. It is designed as a minimalistic, ultra-fast, privacy-conscious social client that lets users browse, post, reply, boost, and manage Mastodon accounts through a cleaner interface than the default Mastodon web app.
In simple terms:
Think of Phanpy as a better-looking, faster, more responsive Mastodon dashboard that runs entirely in the browser.
🔍 What Does Phanpy Actually Do?
Phanpy connects to your existing Mastodon/Fediverse account and gives you:
- streamlined timeline browsing
- grouped notifications
- nested conversation threads
- multiple account switching
- pop-out composer window
- dark/light themes
- multi-column social dashboard mode
- hashtag timeline views
- unsent draft recovery
All while using Mastodon’s API behind the scenes.
SEE ALSO: How to Host Your Own Mastodon Server on a VPS
⚡ Why People Use Phanpy Instead of Default Mastodon UI
The official Mastodon frontend can feel:
- cluttered
- slower on heavy timelines
- less efficient for power users
- awkward on desktop workflows
Phanpy was built specifically to solve that.
Its developer describes it as an “opinionated” client—meaning it intentionally redesigns the social experience to be:
Cleaner
Less visual noise.
Faster
Built as a static SPA (single-page application) with aggressive frontend optimization.
More Productive
Ideal for people who manage multiple timelines or accounts.
Easier to Self Host
No backend daemon required—just static files served through NGINX/Apache/CDN.
🏗 Technical Architecture of Phanpy
This is important:
Phanpy is NOT a Mastodon server.
It does not federate, does not store posts, and does not run ActivityPub services.
Instead:
It is a frontend client layer.
Meaning:
User Browser → Phanpy UI → Mastodon API → Mastodon/Fediverse Instance
So it simply acts as the visual/social interface between your users and whatever Mastodon-compatible server they already use.
Because of this architecture:
- no database required
- no PostgreSQL required
- no Redis required
- no Sidekiq workers
- no Ruby stack
- no mail server
Just:
- Node.js to build
- NGINX to serve static output
This is why deployment is extremely lightweight.
🌐 Is Phanpy a Social Network?
No.
Phanpy is a client for a social network.
Just like:
- TweetDeck was a client for Twitter
- Ivory is a client for Mastodon
- Elk is another Fediverse frontend
Phanpy is simply one of the most polished browser-based clients available.
🎯 Best Use Cases for Phanpy
Phanpy is excellent for:
✔ Personal Mastodon power users
People wanting a better daily interface.
✔ Organizations running Mastodon communities
Custom branded frontend under:
social.yourdomain.com
✔ Hosting providers / SaaS companies
Offer white-labeled Fediverse portals.
✔ Privacy-first communities
No need to expose users to third-party frontends.
🔥 Why It’s Becoming Popular
Phanpy has gained traction because it offers something many Fediverse users want:
Mastodon functionality without Mastodon frontend frustration.
Users particularly like:
- instant feel
- smooth thread reading
- grouped boosts
- distraction-free design
It has become one of the most recommended alternative Mastodon web clients in the Fediverse community.
🖥 Can You Self-Host Phanpy?
Yes — very easily.
The official project specifically supports self-hosting as a pure static web app, meaning you can host it on:
- AlmaLinux VPS
- Ubuntu VPS
- Debian VPS
- NGINX web servers
- Apache
- Docker containers
- CDN object storage
with almost zero server resource usage.
💡 In One Sentence
Phanpy is a lightweight self-hostable premium frontend interface for Mastodon that dramatically improves usability, speed, and aesthetics without requiring you to run a full Mastodon server.
Running your own modern Mastodon client is easier than ever with Phanpy—a fast, lightweight, and privacy-friendly web interface designed for the Fediverse. In this guide, you’ll learn how to deploy Phanpy on an AlmaLinux VPS with production-grade performance, HTTPS, and optimization best practices.
🌐 Why Deploy Phanpy on AlmaLinux VPS?
Phanpy offers:
- ⚡ Blazing-fast performance (static build, no backend required)
- 🔒 Privacy-first Mastodon browsing
- 🎨 Clean, customizable UI
- 🌍 Works with any Mastodon instance
Deploying it on your own VPS ensures:
- Full control over performance and caching
- Custom domain branding (e.g.,
social.yourdomain.com) - Better uptime and SEO benefits
🧰 Prerequisites
- AlmaLinux 8/AlmaLinux 9 VPS
- Root or sudo access
- Domain or subdomain (recommended:
social.yourdomain.com) - Basic familiarity with Linux CLI
Compare AlmaLinux VPS Plans
🚀 How to Deploy Phanpy on AlmaLinux VPS (Production-Ready Guide)
To deploy Phanpy on AlmaLinux VPS, follow the steps below:
-
⚙️ Install Required Packages
dnf update -y dnf install -y git nginx nodejs npm
Ensure Node.js 18+:
node -v
If needed:
dnf module reset nodejs -y dnf module enable nodejs:18 -y dnf install nodejs -y
-
📦 Download Phanpy
cd /opt git clone https://github.com/cheeaun/phanpy.git cd phanpy
-
🔧 Install Dependencies
npm install
-
🛠 Configure Environment
cp .env.example .env nano .env
Set your default Mastodon instance:
VITE_DEFAULT_INSTANCE=https://mastodon.social
-
🏗 Build for Production
npm run build
Output directory:
/opt/phanpy/dist
-
🌍 Configure NGINX (Production Optimized)
Create config:
nano /etc/nginx/conf.d/phanpy.conf
✅ Optimized NGINX Config (Gzip + Brotli + SPA Routing)
server { listen 80; server_name social.yourdomain.com; root /opt/phanpy/dist; index index.html; # Enable Gzip gzip on; gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript; gzip_min_length 256; # Enable Brotli (if module installed) brotli on; brotli_types text/plain text/css application/javascript application/json image/svg+xml; brotli_comp_level 5; location / { try_files $uri /index.html; } location ~* \.(js|css|png|jpg|jpeg|gif|svg|ico)$ { expires 30d; access_log off; } }Reload:
nginx -t systemctl enable nginx systemctl restart nginx
-
🔥 Configure Firewall
firewall-cmd --permanent --add-service=http firewall-cmd --permanent --add-service=https firewall-cmd --reload
-
🔒 Enable HTTPS (Let’s Encrypt)
dnf install -y certbot python3-certbot-nginx certbot --nginx -d social.yourdomain.com systemctl enable certbot-renew.timer
⚡ Production Best Practices
✅ Use a Subdomain
Host Phanpy on:
social.yourdomain.com
✅ Enable CDN (Optional)
Use Cloudflare for:
- Global caching
- DDoS protection
- TLS optimization
✅ Auto-Update Script
nano /opt/phanpy/update.sh
#!/bin/bash cd /opt/phanpy git pull npm install npm run build systemctl reload nginx
chmod +x /opt/phanpy/update.sh
🎯 Final Result
You now have:
- ⚡ High-performance Phanpy deployment
- 🔒 HTTPS-secured instance
- 🌍 Custom branded subdomain
- 🚀 Optimized delivery via NGINX
💡 Use Case Ideas
- Branded Mastodon client for your business
- Internal social feed dashboard
- Privacy-focused alternative frontend for users
📣 Ready to Deploy Faster?
If you’d rather skip the manual setup, Rad Web Hosting offers:
🚀 AlmaLinux VPS Hosting
- Instant deployment
- Full root access
- Optimized for Node.js + NGINX
- DDoS-protected infrastructure
👉 Get Started Today: https://radwebhosting.com/almalinux-vps
Launch Your Own Branded Mastodon Frontend
Deploy Phanpy on a lightning-fast AlmaLinux VPS with full root access, DDoS protection, and optimized NGINX performance.
Best VPS Specifications for Hosting Phanpy (RAM/CPU/Bandwidth Sizing Guide)
One of the biggest advantages of deploying Phanpy is that it does not require the heavy backend resources associated with a full Mastodon server.
Because Phanpy is a static frontend application, your VPS is mainly responsible for:
- serving compressed HTML/CSS/JS assets
- handling SSL/TLS negotiation
- processing NGINX requests
- optionally acting as a reverse cache/CDN origin
This means the hardware requirements are surprisingly light — but there are still important production sizing decisions if you want fast global performance.
🧮 Minimum vs Recommended VPS Resources
| Deployment Size | vCPU | RAM | SSD Storage | Bandwidth | Recommended For | Best VPS Plan |
|---|---|---|---|---|---|---|
| Small Personal Use | 1 Core | 1 GB | 16 GB SSD | 1 TB | single user / hobby | KVM-SSD-1 |
| Small Community | 1 Core | 2 GB | 32 GB SSD | 1 TB | niche groups | KVM-SSD-2 |
| Branded Production Deployment | 1 Core | 4 GB | 64 GB SSD | 2 TB | organizations/business | KVM-SSD-4 |
| High Traffic Public Frontend | 2 Core | 8 GB | 128 GB SSD | 4 TB+ | large public audience | KVM-SSD-8 |
⚡ Why Resource Usage Is So Low
Phanpy does not run:
- PostgreSQL
- Redis
- Sidekiq
- Ruby workers
- media processing daemons
Unlike full Mastodon, there are no persistent backend services consuming RAM.
After build completion, Phanpy is essentially:
a folder of static files served by NGINX.
That means your VPS bottleneck becomes:
network throughput + TLS performance + concurrent NGINX workers
not database horsepower.
📦 Recommended Real-World Production Baseline
For a professional deployment under:
social.yourdomain.com
a sweet spot is:
1 vCPU / 4 GB RAM / SSD storage
Why?
Because this gives room for:
- NGINX
- Brotli compression threads
- gzip fallback
- Certbot renewals
- system updates
- optional local cache
- log rotation
- Fail2Ban / WAF tools
without resource contention.
This is the ideal commercial recommendation because:
users experience near-instant page delivery while the server remains inexpensive.
🌍 Bandwidth Matters More Than CPU
Since Phanpy serves frontend assets repeatedly to users, outgoing bandwidth can exceed CPU importance.
Each visitor may load:
- JS bundles
- CSS files
- fonts
- SVG/UI assets
Compression reduces this dramatically, but bandwidth still matters on public deployments.
Recommended:
minimum 2–3 TB monthly transfer
for publicly accessible instances.
If fronted by Cloudflare CDN caching, origin bandwidth drops substantially.
🔥 Why SSD Still Matters
Even static sites benefit from fast disk:
- faster file reads
- better NGINX cache performance
- snappier TLS session file operations
- improved update/build tasks
Avoid old spinning disk VPS plans.
Use:
SSD or NVMe VPS only.
🛡 Recommended Production Software Stack
Your VPS should ideally run:
- AlmaLinux 8 or 9
- NGINX
- Node.js 18+
- Certbot SSL
- Brotli module
- gzip enabled
- Fail2Ban
- logrotate
This gives:
- speed
- hardening
- long-term maintainability
📈 Scaling for Public Traffic
If Phanpy becomes publicly shared or indexed:
traffic patterns become bursty.
Especially from:
- Mastodon mentions
- Reddit threads
- tech blog referrals
- Fediverse directories
At that point:
2 vCPU / 8 GB RAM with CDN fronting
becomes ideal.
Not because Phanpy is “heavy”—
but because TLS handshakes + concurrent static requests + bot traffic accumulate.
Conclusion
You now know how to deploy Phanpy on AlmaLinux VPS and are also now familiar with the best VPS specifications for hosting Phanpy. You are now ready to deploy and run your own self-hosted Phanpy server.









