☁️ 🐘
PHP cloud hosting for the rest of us
Managed PHP hosting since 2012. Git deploys, MySQL, SSL and backups, no server to maintain.
Built with
Built what
Built how
PHP cloud hosting means whatever the seller needs it to mean. Shared hosters put the words on the same oversold box they always sold. The hyperscalers mean a menu of 200 services you assemble yourself. What we mean is narrower: a managed platform that runs PHP, and nothing else.
We operate the PHP versions, the MySQL, the SSL certs, and the backups. You push code. That has been the deal since 2012.
Start a free trial — no credit cardFor the rest of us
The big clouds assume a platform engineer on the team. Shared hosting assumes nobody will ever open a terminal. In between is everyone else: the freelancer with 11 client sites, the two-person agency, the developer who wants a staging environment without also wanting Kubernetes.
If you are good with Git and Composer and would rather not own an operating system, this fits. If you want a control panel with a one-click WordPress button, it does not, and we would rather say so now than take the money.
What a month costs
The smallest app is €2.50. A small production site with a database lands at €5–€10. Nothing is bundled — PHP, MySQL, storage, traffic, backups, and jobs are booked separately and scaled separately, so a database that outgrows its size does not drag the PHP component up with it.
Billing runs in arrears, by the day. Book a component for three days, pay for three days. Delete an environment and it stops costing money that afternoon. No annual plan to escape from.
Every new app starts on a seven-day trial: all components, all sizes, no credit card. The pricing page has the full matrix.
git push is the deploy
Composer runs inside the build. Either the build succeeds and the release goes live, or it fails and the old version keeps serving — there is no half-deployed state to clean up afterwards. Deploy on merge through the GitHub integration.
SSH and SFTP are open for CLI commands and cron jobs. Not for installing things: the shell is jailed, there is no root, and a Node toolchain or FFmpeg will not run there. That trade is the point. Somebody has to patch the operating system, and if that somebody were you, this would be a VPS.
An app holds as many environments as it needs, each one isolated and scaled on its own. Production and staging, same code, different sizes. The architecture page shows how the pieces sit together.
Things we don't do
Listed here because these are the usual reasons to walk away, and finding out after the migration is worse.
- No 1-click installers. A fresh Laravel or Craft CMS install is an empty shell anyway. Composer-first keeps the repository as the source of truth.
- No automatic updates to the software you brought. That call is yours.
- No free migrations. A migration somebody else performed leaves nobody who understands it.
- No phone number and no enterprise tier. Support is chat, the same chat for everyone.
What people run here
Craft CMS, WordPress, Statamic, Kirby, TYPO3, Drupal. Laravel, Symfony, Tempest, CodeIgniter, Yii. Anything on PHP 8 with a LAMP-shaped stack will run — the software pages carry the per-stack notes.
Pick a region when the app is created: Ireland for the EU, or the US.
Coming from somewhere else
The migration guide covers the general path, and the comparison pages have cutover notes for the provider you are leaving. Do it on the trial: run a copy here, look at it, and only then touch DNS.
