
# Project management on Hostinger

Compare documented Project management deployments on Hostinger, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/hostinger/project-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.

3 listings.


## Solidtime

Self-hosted project time tracking and billing records.

- Listing: https://launchinyourcloud.com/directory/solidtime/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Solidtime application, database, workers and persistent files.
- 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.solidtime.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Time tracking and billing are its core scope; it is not a full project planning or payroll system. Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build.

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

Solidtime application, database, workers and persistent files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted project time tracking and billing records.

### Deployment boundaries


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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/solidtime
  Solidtime application, database, workers and persistent files. Time tracking and billing are its core scope; it is not a full project planning or payroll system.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Onatcer, korridor, TheSpyder, 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/solidtime-io/solidtime/graphs/contributors

- Upstream project: https://github.com/solidtime-io/solidtime

### Sources

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

- AGPL-3.0 LICENSE.md: https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

- GitHub Releases: https://github.com/solidtime-io/solidtime/releases

- Solidtime PHP runtime security release: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1

### Licensing sources

- https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

### Infrastructure sources

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


### 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. The self-hosting guide supports company OIDC identity providers and explicitly requires On-Premise Business. Configure the public URL, proxy/HTTPS settings, IdP callback and access rules, with a working super-admin account for recovery. Scope: Current commercial self-hosted SSO feature; not established for the AGPL core v0.22.1 package alone. Source: https://docs.solidtime.io/self-hosting/single-sign-on (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting repository supplies separate application, scheduler and queue-worker services plus PostgreSQL, persistent storage and health checks. Generate keys and configure environment, email, URL/proxy and backup settings; choose matching application images instead of relying on latest. Scope: Upstream self-hosted Compose topology; Business SSO entitlement is separate. Source: https://docs.solidtime.io/self-hosting/guides/docker (reviewed 2026-11-21). Deployment artifact: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml. Artifact reference: main (moving branch); SOLIDTIME_IMAGE_TAG defaults to latest.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose example identifies application, scheduler, queue worker and database roles with persistent storage, but no production CPU/RAM or concurrency baseline was established. Their combined capacity, retention, database size and HA arrangement need workload-specific sizing. Scope: Service topology confirmed; quantitative production hardware sizing remains unconfirmed. Source: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml (reviewed 2026-11-21).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Solidtime; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Solidtime PHP runtime security release (security-advisory): Solidtime 0.22.1 updates PHP to 8.3.36 for two critical runtime issues. Scope: CVE-2026-109618 and CVE-2026-109619 in the PHP runtime; the release updates FrankenPHP as well. Conditions: Custom installations must inspect their own PHP/runtime build; no application-wide vulnerable range is invented. Action: Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build. Source: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1; reviewed 2026-11-19.




## Taiga

Open-source agile project, issue and team planning application.

- Listing: https://launchinyourcloud.com/directory/taiga/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Taiga frontend, backend, database, task workers and persistent media.
- 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://github.com/taigaio/taiga-back
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.

Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Taiga frontend, backend, database, task workers and persistent media. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source agile project, issue and team planning application.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/taiga.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.

- Railway (railway): https://railway.com/deploy/taiga
  Taiga frontend, backend, database, task workers and persistent media. Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes bameda, superalex, jespino, 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/taigaio/taiga-back/graphs/contributors

- Upstream project: https://github.com/taigaio/taiga-back

### Sources

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

- Railway: https://railway.com/deploy/taiga

- MPL-2.0 LICENSE: https://github.com/taigaio/taiga-back/blob/main/LICENSE

- Releases v6.10.2: https://github.com/taigaio/taiga-back/releases

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

### Licensing sources

- https://github.com/taigaio/taiga-back/blob/main/LICENSE

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 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 upstream self-hosting guide documents GitHub and GitLab OAuth user login, disabled by default. Both backend and frontend settings, registered OAuth clients and public-registration settings must align. This establishes those social/provider login paths, not general SAML/OIDC or Cloudron-package SSO support. Scope: Upstream Taiga user login configuration; packaged distributions may differ. Source: https://docs.taiga.io/setup-production.html (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 official taiga-docker repository supplies Compose, initialization configuration and environment settings for application, async worker, database, events and supporting services. Configure secrets, TLS, email and persistent volumes, and align all component image versions before use. Scope: Official self-hosted Compose stack; not the source-development quickstart. Source: https://docs.taiga.io/setup-production.html (reviewed 2026-11-20). Deployment artifact: https://github.com/taigaio/taiga-docker/blob/main/docker-compose.yml. Artifact reference: main (moving branch); choose compatible component release tags.

- Minimum footprint / sizing: Documented. The Cloudron package declares 300MB 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/taiga.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Taiga; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/taigaio/taiga-back/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Tududi

Self-hosted task, project and personal productivity application.

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

### Scope and qualifications

CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.

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

Tududi application and persistent database and files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted task, project and personal productivity application.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes chrisvel, antanst, rome-xi, 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/chrisvel/tududi/graphs/contributors

- Upstream project: https://github.com/chrisvel/tududi

### Sources

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

- Railway: https://railway.com/deploy/tududi

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

- GitHub Releases (v2.1.1): https://github.com/chrisvel/tududi/releases

### Licensing sources

- https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

### Infrastructure sources

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

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


### 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 v2.1.1 OIDC guide documents one or multiple identity providers, installation callbacks, account linking and optional just-in-time provisioning. Automatic provisioning and admin-domain rules require deliberate IdP access restrictions; personal API tokens and CalDAV Basic authentication are separate paths. Scope: Versioned self-hosted application-user OIDC login. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docs/10-oidc-sso.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 v2.1.1 Compose example runs Tududi with PostgreSQL 16, database health checks and persistent database/uploads/backups storage. Supply environment secrets and replace the moving latest application image with the intended released version; optional local dumps still need off-host backup. Scope: Versioned Compose example; PostgreSQL-backed v2.x is different from older SQLite installations. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml. Artifact reference: v2.1.1 (file snapshot; example application image still uses latest).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed v2.1.1 README and Compose stack establish a PostgreSQL-backed application with persistent uploads and backups, but no production CPU/RAM or concurrency baseline was confirmed. The sample has no resource requests/limits that could substantiate a host minimum. Scope: Deployment topology confirmed; production/HA sizing for the reference workload remains unconfirmed. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Supporting source: Versioned installation prerequisites — https://github.com/chrisvel/tududi/blob/v2.1.1/README.md.

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

- Operating cost estimate: Not researched.

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






