
# Content management & CMS on Northflank

Compare documented Content management & CMS deployments on Northflank, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/northflank/content-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Northflank team and project; hosted platform or a separately connected customer cluster
- Provider group: application-platform
- Provider classification: The published Northflank recipes use its hosted platform. Northflank also offers connected customer clusters; those require separate application-specific evidence. Source: https://northflank.com/docs/v1/application/getting-started/create-a-project (checked 2026-11-20).
- Network: Private project services with explicitly exposed public ports
- Identity and access: Team/project roles, API tokens and secret groups
- Installation guidance: Deploy builds, containers, jobs and database add-ons in a project. The hosted platform is separate from Northflank BYOC: confirm the underlying account, cluster ownership and operating agreement for that option.
- Guidance source: https://northflank.com/docs/v1/application/getting-started/create-a-project
- Guidance reviewed: 2026-11-12


### Private and VPC ingress

Project-internal ports, public ingress and VPC ingress are distinct paths. Confirm the deployment mode and private-load-balancer availability; hosted-project documentation does not establish a customer-owned VPC deployment.
Source: https://northflank.com/docs/v1/application/network/networking-on-northflank (reviewed 2026-11-14).

The listings below have evidence for Northflank. Read each cloud evidence note for the applicable package, edition and support qualifications.

2 listings.


## Joomla!

Customer-operated content management and website publishing platform.

- Listing: https://launchinyourcloud.com/directory/joomla/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci, digitalocean, linode, vultr, northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Joomla web application, database, web server and persistent site assets.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.joomla.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Joomla web application, database, web server and persistent site assets. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Customer-operated content management and website publishing platform.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/joomla-with-mds/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/openlitespeed-joomla (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application (checked 2026-11-19). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-joomla-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Architecture (oci): https://docs.oracle.com/en/solutions/joomla-with-mds/
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/openlitespeed-joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/joomla
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Vultr Docs (vultr): https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Northflank Guide (northflank): https://northflank.com/guides/deploy-joomla-on-northflank
  Joomla web application, database, web server and persistent site assets. The Oracle architecture, provider marketplace packages and Northflank recipe are separate paths. Joomla stable versions, release candidates and extension releases must be distinguished.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes brianteeman, wilsonge, infograf768, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/joomla/joomla-cms/graphs/contributors

- Upstream project: https://github.com/joomla/joomla-cms

### Sources

- OCI Architecture: https://docs.oracle.com/en/solutions/joomla-with-mds/

- DO Marketplace: https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- Vultr Docs: https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- Northflank Guide: https://northflank.com/guides/deploy-joomla-on-northflank

- GPL-2.0 LICENSE.txt: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

- Releases v6.2.1-rc1: https://github.com/joomla/joomla-cms/releases

### Licensing sources

- https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt

### Infrastructure sources

- https://docs.oracle.com/en/solutions/joomla-with-mds/

- https://marketplace.digitalocean.com/apps/openlitespeed-joomla

- https://techdocs.akamai.com/quick-deploy-apps/docs/joomla

- https://docs.vultr.com/how-to-use-vultrs-joomla-marketplace-application

- https://northflank.com/guides/deploy-joomla-on-northflank


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. miniOrange publishes a SAML service-provider extension and explicitly states Joomla 3/4/5/6 compatibility. This is a third-party extension with its own plan and support terms, not an included Joomla-core feature; validate the exact site version, provider and purchased plugin capabilities. Scope: Extension vendor documentation for Joomla 6-compatible SAML; not upstream Joomla support. Source: https://plugins.miniorange.com/joomla-single-sign-on-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Akamai documents deploying its Joomla Quick Deploy application through Cloud Manager, API, CLI or Terraform using StackScript 985372. This is a provider-maintained package/recipe; verify the installed Joomla version and upgrade path separately from the upstream release. Scope: Akamai/Linode Joomla application deployment recipe; not a Joomla upstream HA template. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla (reviewed 2026-11-20). Deployment artifact: https://techdocs.akamai.com/quick-deploy-apps/docs/joomla. Artifact reference: Current provider StackScript 985372 examples; package/application versions can differ.

- Minimum footprint / sizing: Sources checked — unresolved. The current Joomla 6.x technical requirements recommend a PHP memory limit of at least 256 MB and specify supported PHP, database and web-server versions. That limit is per PHP process, not a VM/RAM or HA capacity floor; whole-deployment sizing remains unconfirmed. Scope: Joomla 6.x software requirements; no complete host footprint established. Source: https://manual.joomla.org/docs/next/get-started/technical-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Joomla!; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/joomla/joomla-cms/blob/6.2-dev/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 6.2.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Joomla! upstream application; verify compatibility with the selected package. Source: https://github.com/joomla/joomla-cms/releases/tag/6.2.0 (reviewed 2026-11-19).







## KeystoneJS (Keystone 6)

Self-hosted content backend with a configurable GraphQL API and administration interface.

- Listing: https://launchinyourcloud.com/directory/keystonejs/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: northflank
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Keystone 6 application and PostgreSQL using the Northflank template.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://keystonejs.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Keystone is a developer framework that requires a project schema and application configuration; it is not a ready-made editorial website.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Keystone 6 application and PostgreSQL using the Northflank template. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content backend with a configurable GraphQL API and administration interface.

- backend-platforms: Self-hosted content backend with a configurable GraphQL API and administration interface.

### Deployment boundaries


- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://northflank.com/guides/deploy-keystonejs-on-northflank (checked 2026-11-19). 


### Cloud deployment evidence

- Northflank Guide (northflank): https://northflank.com/guides/deploy-keystonejs-on-northflank
  Keystone 6 application and PostgreSQL using the Northflank template. Keystone is a developer framework that requires a project schema and application configuration; it is not a ready-made editorial website.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes timleslie, emmatown, jesstelford, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/keystonejs/keystone/graphs/contributors

- Upstream project: https://github.com/keystonejs/keystone

### Sources

- Northflank Guide: https://northflank.com/guides/deploy-keystonejs-on-northflank

- MIT LICENSE: https://github.com/keystonejs/keystone/blob/main/LICENSE

- Releases 2026-11: https://github.com/keystonejs/keystone/releases

### Licensing sources

- https://github.com/keystonejs/keystone/blob/main/LICENSE

### Infrastructure sources

- https://northflank.com/guides/deploy-keystonejs-on-northflank


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed guide provides session APIs and an opinionated auth package for custom Keystone applications. This alone does not establish a supported turnkey SAML/OIDC integration or its entitlement; confirm the application-specific identity implementation. Scope: Keystone 6 framework authentication APIs; not a packaged SSO feature. Source: https://keystonejs.com/docs/guides/auth-and-access-control (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream CLI guide documents building the application with keystone build, applying Prisma migrations and running keystone start. These commands deploy a custom Keystone project; they are not a prebuilt turnkey CMS image or cloud infrastructure template. Scope: Keystone 6 application build/start and Prisma migration workflow. Source: https://keystonejs.com/docs/guides/cli (reviewed 2026-11-20). Deployment artifact: https://keystonejs.com/docs/guides/cli. Artifact reference: Current CLI instructions; pin the project and database dependencies.

- Minimum footprint / sizing: Sources checked — unresolved. The CLI and first-project guides establish an application build, Node runtime and database-backed project, but no quantitative production CPU/RAM/storage baseline was established. Size the actual schema, database, uploads and concurrency rather than treating the tutorial as HA capacity. Scope: Custom Keystone 6 application; deployment-specific production sizing. Source: https://keystonejs.com/docs/guides/cli (reviewed 2026-11-20). Supporting source: Official first-project walkthrough — https://keystonejs.com/docs/walkthroughs/lesson-1.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: KeystoneJS (Keystone 6); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/keystonejs/keystone/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The 2026-11-03 monorepo release includes @keystone-6/core 8.3.0. Package versions differ within the Keystone 6 family; the date tag is a release bundle rather than one application semantic version. Scope: Keystone 6 monorepo package release bundle; selected project dependencies must be pinned separately. Source: https://github.com/keystonejs/keystone/releases/tag/2026-11-03 (reviewed 2026-11-19).






