Self hosted WordPress. We will run the server.

One thing this page does not claim, because it is not true here: WordPress does not boot with an administrator already seeded. It ships an open install screen, which is how WordPress works everywhere, and claiming it immediately is the first item in the limitations below.

We are not a managed WordPress platform and we do not price like one. No staging environment, no WordPress-aware cache, no automatic core updates. What there is instead is a machine with no tiers on it: every plugin, every theme, SFTP, the database, as many sites as it will carry, at one flat hourly rate.

No requests-per-second figure appears here, because we have no first-party measurement of this template and a made-up number is the kind of claim that gets corrected later.

If your credit balance reaches zero the server stops and the site goes offline. Data is retained while the server exists, so topping up brings it back as it was. A server that is deleted takes its backup images with it, which is why a WXR export or an SSH copy kept somewhere else is worth the five minutes. Signing up adds $5 in free credit, no card needed.

• Every service is health-checked every 60 seconds. The sweep is observational: restarting is done from the console rather than automatically.
• A stalled deploy is retried automatically, not abandoned.
• A deploy is never reported done until the URL actually answers.
• Your versions do not move. WordPress 7.1.0 and MariaDB 11.8 are pinned. A floating latest tag is how a live WordPress gets dragged onto a new major and runs an irreversible database migration nobody asked for.
• The template deploys in about six minutes, which is the platform's own budget for a light template, not an estimate.

The line WordPress.com draws is no longer at plugins, it is at the server. Plugins and themes start at $9 a month. SFTP, SSH and WP-CLI start at $40. A European 4 GB server here is $15.18 a month and comes with root, the file system and the database, because the machine is yours rather than a tenancy on theirs.

What you do not give up is the thing people fear giving up. Root SSH is included, the file system is yours, and mysqldump works exactly as it does on a machine you built. This is the same VPS with the boring hours already spent.

• Claim the install screen immediately. WordPress leaves /wp-admin/install.php open until somebody completes it, and whoever completes it becomes the administrator of a site that can execute PHP. This is how WordPress works everywhere, not something this deployment adds, and most hosts never mention it. Open the generated HTTPS address as soon as the console says the deployment is live, and finish the first-run screen before you do anything else.
• No email until you add a plugin. WordPress sends no mail on its own here, so password resets, comment notifications and contact forms will not deliver until you install an SMTP plugin and point it at a mail provider. Nothing in the deployment blocks that; it simply is not configured, because the credentials would have to be yours.
• Media lives on the server disk. Uploads go into the wordpress-files volume on the machine, not into object storage. That keeps it simple and it is included in the server price, but it means a media-heavy site grows the disk rather than a separate bill, and the disk is what you size for.
• A careless plugin can undo the proxy fix. A plugin that rewrites wp-config.php or hardcodes http:// will reintroduce the redirect loop our configuration prevents. If wp-admin starts looping after you install something, that is the cause, and removing the plugin restores it.

What does not come across: plugin licence keys usually need reactivating on the new domain, and anything your old host provided as a platform feature rather than a plugin, their cache, their CDN, their staging copy, has no equivalent to import because it was never part of WordPress. We do not perform the migration: there is no migration service and no import API, and both routes are things you run.