CONTENT & PUBLISHING
WordPress
A familiar editor for a blog or website, with content stored in the project’s PostgreSQL database.
ONE-CLICK APPS
Install WordPress, n8n or Umami without a server to configure. Each app gets its own database, secrets and address, managed like any other project.
Three apps ready to deploy. Every one runs on your own project and database.
| App | Runs on | Database |
|---|---|---|
| WordPress | PHP runtime | PostgreSQL |
| n8n | Node.js process | PostgreSQL |
| Umami | Workers runtime | PostgreSQL |
Every install is its own project · Own database, secrets and address
A one-click app is an open-source application Fortly installs into a new project for you. There is no code to upload and no server to configure: choose the app, answer the one or two questions it needs, and Fortly creates the project, the database and secrets the app expects, then publishes it at its own address.
CONTENT & PUBLISHING
A familiar editor for a blog or website, with content stored in the project’s PostgreSQL database.
WORKFLOW AUTOMATION
A visual workflow editor that connects triggers and services, with workflows and credentials kept in the project’s database.
PRIVACY-FIRST ANALYTICS
Cookie-free website analytics: visitors, pages, referrers and countries, stored in the project’s own database.
Nothing about a one-click app is a special case once it is running. It has the same address, domains, logs, schedules, secrets, backups and team access as a project you deployed from your own repository, and you manage it from the same console. Delete it and the app, its database and its files go with it.
| App | Runs on | You choose at install | Fortly creates |
|---|---|---|---|
| WordPress | Fortly’s PHP runtime on Workers | Site title, admin username, email and password | PostgreSQL database, WordPress keys and salts, a wp-cron schedule |
| n8n | The Workers runtime | Nothing | Its own database and storage, and the credential encryption key |
| Umami | The Workers runtime | An admin password | PostgreSQL database, Umami’s tables and the login signing secret |
Every install also adds its own address under fortly.com. Add a domain you own on the project’s Domains tab whenever you are ready, for example blog.example.com for WordPress or stats.example.com for Umami.
All three run on Fortly’s Workers runtime, not on a Node.js or PHP server kept awake for them. Umami and WordPress, whose PHP runs inside a WebAssembly interpreter, run only while a request needs them: a quiet project costs almost nothing to keep, and the first request after a quiet spell starts the app again in about a second. Each reaches its own PostgreSQL database, and nothing else on Fortly’s network.
n8n runs in a Workers runtime process of its own, because its engine keeps schedules and executions going between requests. It keeps its workflows in its own database, saved to the project’s storage each time it starts. Like any project with a process, it stops after a quiet spell and starts again in about three seconds on the next request; its timers do not fire while it is stopped, and the n8n page explains how to schedule workflows with a webhook and a Fortly schedule.
The console also previews Shopify Storefront, Ghost, Strapi, Directus, Metabase, Appsmith, Plausible and Uptime Kuma. Those do not have one-click installers yet, and a preview never creates a project. An app is marked Ready to deploy only after its installer has installed it and loaded its first page on a live Fortly node. You can still deploy any supported application from your own repository.
Before you build
No. It is an ordinary project with the same domains, logs, schedules, backups and team access, and you can delete it the same way.
Yes, within your plan’s project allowance. An app counts as one project; check plans and capacity before installing several.
They are catalogue previews for now. An app becomes Ready to deploy only after its installer has passed a live installation check.