High-Traffic Online Stores
Phoenix VPS & Dedicated Servers Plan & Pricing
Express Linux VPS
- 4GB RAM
- 2 CPU Cores
- 60GB SSD Disk Space
- 100Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Express Plus Linux VPS
- 6GB RAM
- 3 CPU Cores
- 100GB SSD Disk Space
- 100Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Basic Linux VPS
- 8GB RAM
- 4 CPU Cores
- 140GB SSD Disk Space
- 200Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Basic Plus Linux VPS
- 12GB RAM
- 6 CPU Cores
- 180GB SSD Disk Space
- 200Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Professional Linux VPS
- 18GB RAM
- 8 CPU Cores
- 240GB SSD Disk Space
- 300Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Professional Plus Linux VPS
- 24GB RAM
- 8 CPU Cores
- 280GB SSD Disk Space
- 300Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Advanced Linux VPS
- 28GB RAM
- 10 CPU Cores
- 320GB SSD Disk Space
- 500Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Advanced Plus Linux VPS
- 32GB RAM
- 16 CPU Cores
- 400GB SSD Disk Space
- 500Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Getting Started with Phoenix Server: Requirements & Plan Guide
Minimum Server Requirements for Phoenix (Production)
Operating System: Linux (Ubuntu 22.04/24.04 LTS, Debian 12, AlmaLinux 9 recommended)
Elixir: Elixir 1.15+ (latest stable release recommended for production)
Erlang/OTP: Erlang/OTP 26+ (required for Elixir runtime)
Process Manager: systemd or Distillery/Release (for process monitoring and auto-restart)
Reverse Proxy: Nginx (recommended for HTTP/HTTPS handling and load balancing)
Database (Optional): PostgreSQL 15+ / MySQL 8+ (separate database server recommended for high traffic)
Caching (Recommended): Redis (for caching, sessions, PubSub, and real-time performance optimization)
Recommended RAM: ≥2 GB
Recommended CPU: ≥2 vCPU cores
Storage: ≥20 GB SSD
Recommended Phoenix Hosting Plans
| Recommended Plan | Estimated Concurrent Users | Estimated Daily Visits | Use Case | Notes |
|---|---|---|---|---|
| Express Linux VPS | 10–50 | 100–500 | Simple blog, landing page, or marketing site | Minimal real-time features, mainly static or lightly dynamic pages |
| Express Plus Linux VPS | 30–100 | 500–2,000 | Small dynamic site with login or basic APIs | Supports basic Channels/WebSocket and small API usage |
| Basic Linux VPS | 50–150 | 2,000–6,000 | Small SaaS app, admin dashboard, or MVP eCommerce | Handles moderate concurrency, background jobs, and caching |
| Basic Plus Linux VPS | 100–300 | 6,000–15,000 | Growing real-time app with frequent API calls or multi-user collaboration | Optimized for Phoenix LiveView, SSR-like rendering, and caching |
| Professional Linux VPS / Professional Plus | 300–600 | 15,000–50,000 | Medium production app, multi-user dashboards, or SaaS platform | High concurrency, multiple LiveView channels, Redis caching, background jobs |
| Advanced Linux VPS / Advanced Plus | 600–1,500 | 50,000–150,000 | Large-scale platform with high real-time demand and mission-critical workloads | Supports multiple Phoenix instances, independent DB, load balancing |
| Dedicated Server (Lite or higher) | 1500–5,000+ | 100,000–500,000+ | High-traffic enterprise SaaS, mission-critical real-time apps | Enterprise-grade performance, clustering, massive concurrency, full control |
Additional Notes on Plan Sizing & Performance
Choose a plan based on concurrent users, not just daily visits. High concurrency increases CPU, RAM, and database load, especially with Phoenix LiveView or WebSocket connections.
2. Daily Visits vs Peak Load
Daily visits indicate overall traffic, but sudden spikes can overload smaller plans. Advanced (Plus) or Dedicated Server plans handle traffic surges and high real-time demand more smoothly.
3. CPU & Memory Stability
CPU cores directly affect request throughput and parallel processing capacity. RAM determines caching efficiency, database buffering, and process stability. When memory utilization exceeds 75–80%, performance may degrade due to swapping or resource contention. Higher-tier VPS plans provide better stability under sustained load.
4. Real-Time & Background Workload
Phoenix applications using Channels, PubSub, or background jobs (e.g., Oban) place additional load on CPU and RAM. Choose plans with higher concurrency capacity if multiple LiveView channels or jobs run simultaneously.
5. When to Choose a Dedicated Server
Use a Dedicated Server if concurrent users exceed ~1,500, or CPU/RAM is saturated. Offers full resource isolation, scalability, and multiple Phoenix instances for enterprise-grade applications.
Server sizing recommendations are estimates based on typical Phoenix workload patterns. The listed concurrent user and daily visit numbers are approximate. Real-world performance may vary depending on LiveView complexity, API workload, caching, and database usage.
Phoenix VPS vs Dedicated Server: Choosing the Best Fit for You
| Feature | Phoenix VPS | Dedicated Phoenix Server | Note |
|---|---|---|---|
| CPU | Virtual CPU (2–16 cores depending on plan) | Full dedicated CPU (4–48 cores) | Dedicated CPU ensures stable Phoenix processes, LiveView channels, and background jobs |
| RAM | 4–32 GB | 16–256 GB | More RAM allows larger LiveView session storage, cache, and smoother concurrency |
| Storage | SSD 60–400 GB | SSD/NVMe/SATA 1TB–96TB | Dedicated servers support large DBs, logs, and persistent storage for assets |
| I/O Performance | Moderate | High | Dedicated disk I/O reduces latency for Ecto queries and static content delivery |
| Concurrent Users / Processes | 10–1,500 (depending on plan) | 1,500–5,000+ | More CPU cores support higher concurrent LiveView channels and API requests |
| Background Jobs | Light–Moderate Oban / async jobs | Heavy async jobs & multiple queues | Dedicated resources prevent background tasks from affecting LiveView or API performance |
| Database Hosting | Local or external PostgreSQL/MySQL | High-performance local DB or separate DB cluster | Dedicated servers handle higher DB transaction volume and multiple schemas |
| Caching | Redis / Memcached | Redis / Memcached with larger memory allocation | More memory allows larger caching (Redis/Memcached) for LiveView sessions and API responses |
| Uptime & Reliability | 99.9% uptime, isolated resources | 99.99% uptime, fully dedicated resources | Dedicated infrastructure improves long-term stability and predictable performance |
| Scalability | CPU up to 16 cores, RAM up to 32 GB, SSD up to 400GB | Full hardware control; can add CPU, RAM, storage | Dedicated servers are ideal for multi-instance Phoenix deployments and clustering |
| Cost | Lower | Higher | VPS is cost-efficient for small-to-medium Phoenix apps; dedicated is performance-focused |
Phoenix Hosting: Real-World Scenarios
Real-Time Dashboards
SaaS Platforms & Multi-User Sites
Team Collaboration & Internal Apps
Why Choose Our Phoenix Hosting Server?
Easily Scalable
Seamlessly scale CPU, RAM, and storage as your Phoenix application grows. Handle traffic spikes, increasing concurrent connections, and distributed deployments without performance bottlenecks.
Secure Developer Environment
USA-Based Data Centers
Full Root Access
High-Performance Hardware
Up to 1Gbps Network Speed

Production-Ready Phoenix Setup on Ubuntu 22.04 VPS
This guide walks you through a secure, professional phoenix setup for a phoenix production environment on Ubuntu 22.04 VPS.
Step 1: SSH Login and Switch to Root
Connect from your local terminal:
ssh administrator@your_server_ipUbuntu default username is administrator. Switch to root for initial setup:
sudo -i
whoamiOutput should be root. Note: Root should only be used for installation/configuration. Phoenix will run under a separate user.
Step 2: Update System
apt update && apt upgrade -y
apt install -y build-essential git curl unzip nginx ufwStep 3: Install Erlang and Elixir
apt install -y erlang elixirVerify:
elixir -v
erl -versionEnsure OTP version matches your Phoenix app.
Step 4: Install PostgreSQL Securely
apt install -y postgresql postgresql-contribCreate a dedicated PostgreSQL user and database:
sudo -u postgres createuser -P myapp_user
sudo -u postgres createdb -O myapp_user myapp_prodSecure PostgreSQL:
- Only listen on localhost:
nano /etc/postgresql/$(ls /etc/postgresql)/main/postgresql.confSet:
listen_addresses = 'localhost'- Edit
pg_hba.confto allow only local connections - Use a strong password for the
myapp_useraccount - Restart PostgreSQL:
systemctl restart postgresqlStep 5: Install Node.js (for asset compilation)
Recommended Node.js 18 LTS:
curl -fsSL https://deb.nodesource.com/setup_18.x | bash -
apt install -y nodejs
node -v
npm -vStep 6: Create Non-Root User for Phoenix
adduser --system --group --home /var/www/myapp myappStep 7: Deploy Application
mkdir -p /var/www
cd /var/www
git clone https://github.com/yourrepo/myapp.git
chown -R myapp:myapp myapp
cd myapp
sudo -u myapp -i
cd /var/www/myappStep 8: Install Dependencies
Install Hex and Rebar as the myapp user:
mix local.hex --force
mix local.rebar --forceThen:
mix deps.get --only prod
MIX_ENV=prod mix compileStep 9: Build Frontend Assets
cd assets
npm install
npm run deploy
cd ..
MIX_ENV=prod mix phx.digestStep 10: Generate Phoenix Production Release
MIX_ENV=prod mix releaseDo not use
mix phx.serverin production.
Step 11: Configure Environment Variables (Production Standard)
Create /etc/myapp.env:
nano /etc/myapp.envContent:
SECRET_KEY_BASE=your_64_byte_secret
DATABASE_URL=ecto://myapp_user:password@localhost/myapp_prod
PHX_SERVER=true
MIX_ENV=prod
RELEASE_DISTRIBUTION=myapp
ERL_AFLAGS="+K true +A 64"Make sure
SECRET_KEY_BASEis at least 64 bytes.
Step 12: Create Systemd Service
nano /etc/systemd/system/myapp.serviceContent:
[Unit]
Description=Phoenix Production App
After=network.target
[Service]
User=myapp
WorkingDirectory=/var/www/myapp
EnvironmentFile=/etc/myapp.env
ExecStart=/var/www/myapp/_build/prod/rel/myapp/bin/myapp start
Restart=always
RestartSec=5
LimitNOFILE=65536
StandardOutput=syslog
StandardError=syslog
[Install]
WantedBy=multi-user.targetEnable and start service:
systemctl daemon-reload
systemctl enable myapp
systemctl start myapp
journalctl -u myapp -fStep 13: Configure Nginx with WebSocket Support
nano /etc/nginx/sites-available/myappContent:
server {
listen 80;
server_name yourdomain.com;
location / {
proxy_pass http://127.0.0.1:4000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}Enable and restart Nginx:
ln -s /etc/nginx/sites-available/myapp /etc/nginx/sites-enabled/
nginx -t
systemctl restart nginxFor production, configure HTTPS via Certbot.
Step 14: Enable Firewall
ufw allow OpenSSH
ufw allow 'Nginx Full'
ufw enableStep 15: Production Optimizations
- BEAM tuning:
ERL_AFLAGS="+K true +A 64" - File descriptors:
LimitNOFILE=65536 - Run Phoenix under non-root user
- PostgreSQL restricted to localhost
- Enable HTTPS
- Consider monitoring CPU schedulers and application telemetry
FAQ for Phoenix VPS Hosting
What is Phoenix VPS Hosting?
How can I host Phoenix apps with full root access?
Is my Phoenix app secure on a VPS?
What support is available if I run into issues?
Is there any traffic limit or hidden fee?
Can I scale my hosting for Phoenix apps easily?




