Introducing the Community Apps Marketplace: WordPress, n8n, and 6 More Apps in One Click

If you have ever spent an afternoon fighting a WordPress install — wrong PHP version, a plugin that needs a writable directory nginx won't allow, a MySQL connection string typed wrong twice — the Community Apps Marketplace is built to remove that afternoon entirely. Today we are opening a curated catalog of self-hosted apps that deploy in one click, each running on a platform-maintained image, each wired to a managed database automatically when it needs one.

Why a marketplace, and why now#

The Arabic-language web runs on WordPress. W3Techs' content-language breakdown puts WordPress at 61.6% of Arabic-content sites, well above the 41.5% global share — it is the default choice for agencies, freelancers, and small businesses building for readers in the region, and it has been the single most requested one-click install since the cPanel era. We were not going to launch a serious managed-cloud platform for this region without WordPress hosting built in.

n8n tells a different but equally regional story. It is the fastest-growing self-host of the last two years, and a real agency scene across the Gulf already resells hosted n8n to clients running Arabic-language AI and business-process automation. Beyond those two, freelancers and small agencies watching client sites need Uptime Kuma; teams keeping shared credentials in the region want Vaultwarden; agencies running analytics or BI per client want Umami and Metabase without standing up a server for every account. The pattern across the whole catalog is the same: run the apps developers already choose, on infrastructure you did not have to build yourself.

The launch catalog: 7 apps#

• WordPress (CMS) — the region's default content platform, content in managed MySQL, a persistent volume for uploads and themes.
• n8n (automation) — visual workflow automation; starts with its own embedded storage, no database setup required.
• Uptime Kuma (monitoring) — the small, fast uptime monitor agencies run per client.
• Vaultwarden (security) — a self-hosted, Bitwarden-compatible password manager, admin panel disabled by default.
• Umami (analytics) — privacy-first, cookie-free analytics, backed by managed PostgreSQL.
• Metabase (BI) — dashboards and reports over your managed PostgreSQL or MySQL data.
• Gitea (dev tools) — lightweight, self-hosted Git, for teams that want their code in the region.

That is the catalog we are opening with. It is deliberately not the entire self-hosted universe — every app on it had to earn its place under a real security constraint, which is the next part of the story.

The safety model: why not just any Docker image#

Every container on the platform, marketplace or not, runs under the same isolation contract: non-root user, read-only root filesystem, every Linux capability dropped. Most "official" self-hosted images assume they can run as root and write anywhere on disk — that assumption breaks a large share of what you will find on Docker Hub, and we are not going to relax the contract just to fit more logos on a page.

So every marketplace app is either a Docker Official Image, an image from a vendor-verified publisher, or — where the upstream image genuinely needs it, as with WordPress — a small platform-built derivative that only repositions ports and writable paths to fit the same contract every other container on the platform runs under. Every reference is pinned to a digest, not a floating tag, so what you deploy today is exactly what keeps running tomorrow unless you choose to move.

That pinning cuts both ways, on purpose. A marketplace app has no deploy surface — you cannot push a new image, change the tag, or point it at a private registry, because the whole point is that we picked, verified, and locked the image so you do not have to. When we ship a version bump, it lands as a new, reviewed catalog entry, never a silent change to what is already running under you. Everything else about the app — environment variables, scaling, logs, metrics, a custom domain — works exactly like it would for any other container you deploy yourself.

How the one-click deploy actually works#

Open the Marketplace tab, pick an app, and name it. If the app needs a database, we provision managed MySQL or PostgreSQL in the same project and connect it automatically — no connection string to copy, no separate database dashboard to configure first. Apps that ship their own embedded storage, like n8n or Uptime Kuma, start immediately with a persistent volume and nothing else to wire up. Either way, you get a running app with a URL in about the time it takes a normal container to boot, not the time it takes to read a WordPress installation guide.

If you have already read our guide to running WordPress with a custom image, the marketplace packages that same non-root architecture — content in managed MySQL, uploads and everything you install on a persistent volume — without you ever writing the Dockerfile. The image itself is stock WordPress: no plugins or themes baked in, you install them from wp-admin exactly as you would anywhere else.

Get started#

The Community Apps Marketplace is live in the portal now, alongside Container Apps and Deploy Center: 6 of its 7 launch apps deploy today, and WordPress, the flagship, is rolling out right behind them — it shows as coming soon in the portal until it goes live. See the full catalog on the marketplace product page, or compare it with building your own image if you would rather start from a Dockerfile. Start free with a $5 trial credit, no card required.