
# Content management & CMS on Hostinger

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

Canonical page: https://launchinyourcloud.com/clouds/hostinger/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: Hostinger account and VPS
- Provider group: vps-hosting
- Provider classification: The documented route uses a customer VPS and application administrator; the hosting provider operates its physical infrastructure. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-20).
- Network: Customer server networking, DNS and firewall rules
- Identity and access: Cloud account access, server root/SSH access and application administrators
- Installation guidance: Provision the documented Cloudron VPS template in your account, complete domain and administrator setup, then install and operate the reviewed application package.
- Guidance source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
- Guidance reviewed: 2026-11-13


### VPS hardening

The provider recommends SSH hardening, firewall configuration and patching for VPS hosts. A preinstalled application template does not transfer these operating responsibilities away from the customer.
Source: https://www.hostinger.com/tutorials/vps-security/ (reviewed 2026-11-14).

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

2 listings.


## Grav

Self-hosted flat-file content management system.

- Listing: https://launchinyourcloud.com/directory/grav/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: linode, aws, digitalocean, vultr, hostinger, lumadock
- 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: Cloudron package
- Architecture: Grav PHP application and persistent content, configuration and plugins.
- 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://getgrav.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

No relational database is required by the base system; plugins and themes can introduce their own dependencies and licences. Cloudron package and upstream versions can differ.

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

Grav PHP application and persistent content, configuration and plugins. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted flat-file content management system.

### Deployment boundaries


- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/grav.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (linode, aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/grav.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rhukster, flaviocopes, w00fz, 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/getgrav/grav/graphs/contributors

- Upstream project: https://github.com/getgrav/grav

### Sources

- Cloudron Store: https://www.cloudron.io/store/grav.html

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

- MIT LICENSE.txt: https://github.com/getgrav/grav/blob/develop/LICENSE.txt

- Releases v2.2.30: https://github.com/getgrav/grav/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/getgrav/grav/blob/develop/LICENSE.txt

### Infrastructure sources

- https://www.cloudron.io/store/grav.html


### 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. The Grav project documents the Trilby Media login-oauth2 plugin for third-party OAuth2 login, extending the core Login plugin with named and custom providers. Validate plugin/core compatibility and the intended login surface; the old announcement is not proof that every current Admin deployment supports every provider. Scope: Official project announcement plus maintained plugin implementation; OAuth2 Login integration. Source: https://getgrav.org/blog/oauth2-and-ldap-login-plugins (reviewed 2026-11-20). Supporting source: Login OAuth2 maintainer repository — https://github.com/trilbymedia/grav-plugin-login-oauth2.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide supplies version-addressable ZIP packages, Composer installation and source installation. The Admin package includes the Admin plugin. This establishes a deployable application artifact, not a cloud-infrastructure or HA template. Scope: Versioned Grav 1.7 guide; verify current major-version compatibility. Source: https://learn.getgrav.org/17/basics/installation (reviewed 2026-11-20). Deployment artifact: https://getgrav.org/downloads. Artifact reference: Choose a tagged Grav/Core-plus-Admin package; do not assume current downloads match 1.7 instructions.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/grav.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## Winter CMS

Self-hosted content management framework for websites and applications.

- Listing: https://launchinyourcloud.com/directory/wintercms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Winter CMS application, database, files and scheduled jobs.
- 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://wintercms.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Winter is a separate MIT project; do not transfer the commercial licensing or release cadence of October CMS.

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

Winter CMS application, database, files and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted content management framework for websites and applications.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/wintercms (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/wintercms
  Winter CMS application, database, files and scheduled jobs. Winter is a separate MIT project; do not transfer the commercial licensing or release cadence of October CMS.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes daftspunk, LukeTowers, bennothommo, 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/wintercms/winter/graphs/contributors

- Upstream project: https://github.com/wintercms/winter

### Sources

- Hostinger: https://www.hostinger.com/applications/wintercms

- Winter CMS Install Docs: https://wintercms.com/docs/v1.2/docs/setup/installation

- MIT LICENSE: https://raw.githubusercontent.com/wintercms/winter/1.2/LICENSE

- GitHub Releases (v1.2.15): https://github.com/wintercms/winter/releases

### Licensing sources

- https://raw.githubusercontent.com/wintercms/winter/1.2/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/wintercms


### 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 official Winter.SSO plugin adds backend OAuth through Laravel Socialite. It supports named providers and separately installed provider plugins, with optional SSO-only login. Validate the plugin/core versions and provider settings; this is not a claim of native SAML support. Scope: Upstream Winter CMS backend plugin and provider integrations. Source: https://raw.githubusercontent.com/wintercms/wn-sso-plugin/main/README.md (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 versioned installation guide documents Composer, a web installer and a Docker-image option. These install the CMS application; database/web-server configuration and production hardening remain customer work. Match the installer to the chosen Winter release. Scope: Winter 1.2 installation methods; not a provider-specific infrastructure template. Source: https://wintercms.com/docs/v1.2/docs/setup/installation (reviewed 2026-11-20). Deployment artifact: https://wintercms.com/docs/v1.2/docs/setup/installation. Artifact reference: Versioned 1.2 guide; choose compatible package and plugins.

- Minimum footprint / sizing: Sources checked — unresolved. The 1.2 guide lists software prerequisites and warns the installer may temporarily need up to 1.5 GB memory. That installation allowance does not establish a production CPU/RAM/storage floor or capacity for the running CMS. Scope: Installer memory and dependencies only; whole-system production sizing remains open. Source: https://wintercms.com/docs/v1.2/docs/setup/installation (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Winter CMS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/wintercms/winter/1.2/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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






