A WordPress site.Without a server to patch.

A WordPress site in one step.

Fortly installs WordPress 7.1.3 into a new project and publishes it at its own address. You choose the site title, the admin username, an admin email and a password of at least eight characters; the title defaults to My WordPress Site and the username to admin. Fortly creates the project’s PostgreSQL database, generates WordPress’s security keys and salts, runs the WordPress installer against the database, and adds a schedule that keeps wp-cron running every fifteen minutes. An install takes a little over a minute.

1. Open Apps in the console and choose WordPress, or start from New project and Browse apps.
2. Fill in the four fields. Generate offers a strong admin password; Show lets you copy it before you continue.
3. Deploy and sign in. Open the site, then go to /wp-admin with the email and password you chose.

PHP on the Workers runtime, data in PostgreSQL.

The site runs on Fortly’s PHP runtime: WordPress’s own PHP code, executed by a WebAssembly interpreter on the Workers runtime. There is no PHP-FPM pool and no virtual machine to keep running. A quiet site uses nothing between visits, and its pages, assets and theme files are served from the release Fortly published.

Posts, pages, users, settings and comments are stored in the project’s PostgreSQL database rather than MySQL. A database bridge translates WordPress’s queries, so the site uses the same managed database as every other Fortly project: continuous backups, a full export at any time and, on paid plans, restore to any minute from the console.

Know the limits before you move a site.

The release is a bundled copy of WordPress, and code changes made from the dashboard are not kept between requests. Installing or updating themes, plugins or WordPress core from wp-admin is therefore not supported, and the console says so before you install. Content you write in the editor is stored in the database and stays.

The dashboard’s media uploader is not supported either. Upload images and files through the project’s Storage workspace instead, and insert their public addresses into your posts. If your site depends on a specific plugin or a MySQL-only feature, check it against this template before you plan a migration.

After it is live.

Add your own domain on the Domains tab, follow requests and PHP output on Observability, and query the WordPress tables directly from the Database tab’s SQL editor. A blog that needs its own analytics can sit next to a one-click Umami project, and both stay on the same account and bill.

Because the content is ordinary PostgreSQL tables, such as wp_posts and wp_users, you can export the whole database at any time, read it from your own tools through the data API, or restore the site to an earlier minute after a bad edit, without touching the WordPress code at all.