
# Content management & CMS on Railway

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

Canonical page: https://launchinyourcloud.com/clouds/railway/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: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

2 listings.


## Cockpit CMS

Self-hosted structured content and API management application.

- Listing: https://launchinyourcloud.com/directory/cockpit-cms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- 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: Cockpit Core application with persistent SQLite database and storage on Railway.
- 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://getcockpit.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.

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

Cockpit Core application with persistent SQLite database and storage on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted structured content and API management application.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/cockpit (checked 2026-11-19). 


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/cockpit
  Cockpit Core application with persistent SQLite database and storage on Railway. Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes aheinze, raffaelj, filipmiik, 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/Cockpit-HQ/Cockpit/graphs/contributors

- Upstream project: https://github.com/Cockpit-HQ/Cockpit

### Sources

- Railway Template: https://railway.com/deploy/cockpit

- MIT LICENSE: https://github.com/Cockpit-HQ/Cockpit/blob/develop/LICENSE

- Releases v2.14.1: https://github.com/Cockpit-HQ/Cockpit/releases

### Licensing sources

- https://github.com/Cockpit-HQ/Cockpit/blob/develop/LICENSE

### Infrastructure sources

- https://railway.com/deploy/cockpit


### 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: Documented. The CMS authentication guide documents OIDC through the Identi module, including provider discovery, PKCE, claim/role mapping and provider examples. Confirm module packaging and entitlement for the selected build; this is Cockpit CMS, not the unrelated Linux Cockpit administration tool. Scope: Current Cockpit-HQ CMS Identi module; package/version compatibility remains deployment-specific. Source: https://getcockpit.com/documentation/core/concepts/authentication (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 project supplies a downloadable CMS ZIP and a container run command with persistent storage. Its example uses a moving core-latest image; pin a compatible release and configure the web server, permissions, backups and secrets. This is an application artifact, not HA IaC. Scope: Current Cockpit-HQ CMS quick start; upstream Core application packaging. Source: https://github.com/Cockpit-HQ/Cockpit (reviewed 2026-11-20). Deployment artifact: https://github.com/Cockpit-HQ/Cockpit/releases. Artifact reference: Choose a release ZIP or pinned compatible container; reviewed quick start uses core-latest.

- Minimum footprint / sizing: Sources checked — unresolved. The upstream requirements list PHP 8.3+, SQLite or MongoDB, a compatible web server and writable application storage. They do not establish a quantitative CPU/RAM/disk production floor for the chosen CMS and database topology. Scope: Current CMS software prerequisites; numeric production sizing remains open. Source: https://github.com/Cockpit-HQ/Cockpit (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Directus Self-Hosted

Self-hosted content and data management with APIs over your SQL database.

- Listing: https://launchinyourcloud.com/directory/directus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Source-available MSCL-1.0-GPL; free Core tier and licensed capabilities; qualifying Open Innovation Grant
- Licensing model: source-available
- Installation: Version-pinned Docker image/Compose with database and optional Redis/cache
- Architecture: Customer-operated API and management Studio with database and asset storage
- Operations: Customer operates containers, database, caching, asset storage, monitoring, backups and upgrades.
- Product website: https://directus.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current Directus 12 uses MSCL-1.0-GPL, replacing older BSL terms. Core has limits; higher limits and advanced features require a paid license or qualifying grant. Verify licensing against the actual release and do not assume all source-available features are unrestricted. This entry excludes Directus Cloud.

Current Directus 12 uses MSCL-1.0-GPL with competing-use and protected-license-functionality restrictions. The free Core tier or qualifying grant does not make the current core OSI-licensed; older releases had different terms.

The reviewed option runs a long-lived Directus container, SQL persistence and optional Redis/storage services. Storage adapters do not establish customer-account deployment support for a named hyperscaler.


### Category fit

- content-management: Configurable content/data backend with management Studio, REST/GraphQL APIs and flows over SQL data.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/directus-1 (checked 2026-11-12). 


### Cloud deployment evidence

- Directus 12 community deployment on Railway (railway): https://railway.com/deploy/directus-1
  The inspected community template uses the official Directus 12.6.1 image pinned by digest, PostgreSQL, Redis and bucket storage in a customer Railway project. Confirm current license/tier limits, image compatibility, initial credentials and email configuration; this is not Directus Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker deployment and persistence: https://directus.com/docs/self-hosting/deploying

- Self-hosting overview and licensing: https://directus.com/docs/self-hosting/overview

- Current official license: https://github.com/directus/directus/blob/main/license

- Core and licensed tier overview: https://directus.com/start

### Licensing sources

- https://github.com/directus/directus/blob/main/license

- https://directus.com/docs/self-hosting/overview

### Infrastructure sources

- https://directus.com/docs/self-hosting/deploying


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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: Documented. Self-hosted authentication configuration supports OAuth 2.0, OpenID, LDAP and SAML providers. Configure callback URLs and provider settings; this documents protocols, not an independent commercial-license entitlement. Scope: Self-hosted Directus authentication configuration. Source: https://directus.com/docs/configuration/auth-sso (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The deployment guide supplies Compose examples with database, Redis and persistent application storage. Replace placeholder credentials and select compatible image tags; the example is not a complete cloud provisioning template. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://directus.com/docs/self-hosting/deploying (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosting guide gives a container minimum of 0.25 vCPU and 512 MB RAM and a larger recommended configuration. Database, storage, replicas and workload require separate capacity planning. Scope: Directus container baseline only. Source: https://directus.com/docs/self-hosting/requirements (reviewed 2026-11-14).

- License pricing: Documented. The current self-hosting guide identifies MSCL, a free Core tier and paid higher limits/features. Eligible individuals and small organizations can apply for an Open Innovation Grant. Infrastructure, databases and operational labor are separate; do not apply older BSL revenue rules to the current license. Scope: Current MSCL self-hosting guidance; eligibility and feature limits require the current license terms. Source: https://directus.com/docs/self-hosting/overview (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v12.6.1, published 2026-11-04. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream directus/directus release record; commercial editions and deployment packages may differ. Source: https://github.com/directus/directus/releases/tag/v12.6.1 (reviewed 2026-11-14).






