How to deploy WordPress on a VPS without using SSH

Search for "install WordPress on a VPS" and you will find a tutorial that opens with ssh root@your-server-ip and continues for forty commands. Somewhere around configuring PHP-FPM pools you close the tab and go back to shared hosting.

That reaction is correct. The tutorial is not wrong, but it is describing manual labour that should have been automated a decade ago. This post shows the version where you never open a terminal.

What the terminal tutorial is actually doing

It helps to know what you are skipping, because it explains why "just use shared hosting" is not a free choice. A standard WordPress VPS setup involves:

• Creating a non-root user and locking down SSH to key-only authentication
• Configuring a firewall so only ports 22, 80, and 443 are reachable
• Installing nginx, PHP-FPM, and a database server
• Creating a database, a database user, and a secure password
• Downloading WordPress, setting file ownership and permissions correctly
• Writing an nginx server block for your domain
• Requesting a Let's Encrypt certificate and setting up auto-renewal
• Installing fail2ban and enabling unattended security updates
• Setting up a backup job and testing that it restores

Every one of those steps has a way to get it subtly wrong — permissions that let a plugin overwrite core files, a firewall rule that locks you out, a certificate that never renews. This is the real reason shared hosting persists: not that VPS hosting is expensive, but that it has historically demanded skills most site owners do not have and should not need.

The dashboard version

Step 1 — Create a server

Sign up, choose a region near your visitors, and pick a size. For a typical business site or blog, 2 vCPU and 4 GB of RAM is comfortable; you can start smaller and resize later. The server is provisioned and hardened automatically — firewall, fail2ban, SSH key authentication, automatic security updates, Docker, and nginx are all configured before it is handed to you. This takes about 90 seconds.

Step 2 — Run the WordPress installer

From your server, open Apps and choose Install WordPress. Enter a site title and an admin email. The installer sets up nginx, PHP-FPM with OPcache, MariaDB, WordPress itself, and WP-CLI, generates database credentials, and applies correct file permissions.

Your admin username and password are shown once when the install finishes. Save them to a password manager at that moment — they are not stored in plain text afterwards.

Step 3 — Point your domain and get HTTPS

Open Front Door, add a route, and enter your domain. Then, at your domain registrar, create an A record pointing to your server's IP address. When DNS resolves, Simplewala verifies the domain and issues a Let's Encrypt certificate automatically.

Renewal is handled for you, every 90 days, forever. If you want to understand what is happening underneath, SSL/TLS explained covers it.

Step 4 — Log in and build

Visit https://yourdomain.com/wp-admin and log in. From here it is ordinary WordPress: install your theme, add plugins, write posts. Nothing about the platform restricts which plugins you can run.

What you get that shared hosting does not give you

• Dedicated resources. Your CPU and RAM are yours. A traffic spike on someone else's site cannot slow yours down.
• No plugin blocklists. Shared hosts ban plugins that use too much CPU. Your own server does not.
• Real backups you can restore. Daily snapshots of files and database, restorable in one click.
• Root access if you ever want it. You are not locked out of your own machine.
• Email on the same server. Mailboxes on your own domain, without a per-seat bill.

The longer argument for moving off shared hosting is in VPS vs shared hosting and why you should host WordPress on your own server.

Things worth doing in the first week

1. Verify a restore. Take a backup, restore it, and confirm the site comes back. An untested backup is a hope, not a backup.
2. Set up email. If you are sending from a contact form, proper SPF and DKIM records keep you out of spam folders. See business email on your own domain.
3. Install a caching plugin. W3 Total Cache, WP Super Cache, or LiteSpeed Cache all work, and nginx FastCGI caching is available too.
4. Check the security basics. Most are already done for you — the server security checklist shows which ones and what is left to you.

Do I still need a developer?

For design and custom functionality, quite possibly — that is what developers are for. For routine server operations, no. Installing software, adding a domain, renewing a certificate, restoring a backup, and reading logs are all dashboard actions. That is the difference between paying someone for their expertise and paying someone because you cannot log in.

If you are moving an existing site rather than starting fresh, read how to migrate WordPress with zero downtime first — your current site stays live throughout.

Keep reading

WordPress hosting Nginx, PHP-FPM, MariaDB, SSL, and daily backups configured in one click. Migrate WordPress with zero downtime Move a live site to a new host without losing a visitor. Server security checklist The eight things that matter for a small business server. WordPress documentation Installer options, WP-CLI, caching, and multisite.