The problem
Every time I shipped a small PHP app, the code was the easy part. The afternoon disappeared into:
- Provisioning a VPS and picking a distro
- Installing and patching PHP, nginx, and MySQL by hand
- Generating and renewing my own TLS certs
- Writing a deploy script, then debugging that deploy script
- Finding out about downtime from a user, not a monitor
None of this is specific to my app. It's the same setup, every time, for every project.
What I built
phphost skips the server-configuration step entirely.
You give it code a folder, a zip, or a git repo and it gives you back a live, HTTPS URL.
The actual deploy looks like this:
\`
$ phphost deploy
Uploading your site… done
Setting up hosting… done
Securing with HTTPS… done
Going live… done
Live at https://yoursite.phphost.se ✓
`\
That's the whole thing. No hidden build step, no dashboard to babysit.
What's handled for you
- PHP runtime + web server config — set up automatically, whether it's a static site or a full PHP app
- HTTPS — applied the moment the site goes live
- Staging environments — a persistent pre-prod copy of your site that doesn't count against your site limit
- Cron jobs — scheduled tasks without a separate worker process
- .env variables — kept out of your code, settable per environment
- Deploy history — every deploy logged, roll back in a couple of clicks if something breaks
- Uptime monitoring — pings your site continuously and alerts you before a user has to
Who it's for
Mainly developers and freelancers who know PHP well and don't want a second job running Linux. If you're already comfortable managing your own infra, this probably isn't for you and that's fine.
Pricing
Flat monthly plans, starting at $9/mo for one site (5K visitors/mo). No free tier, but no surprise overage shutoffs either — bandwidth/visitor overages are billed at a flat per-unit rate.
Try it
https://phphost.se — happy to answer questions about how it's built or why certain decisions were made.

Top comments (0)