
# Marketing automation on Hostinger

Compare documented Marketing automation deployments on Hostinger, including operating responsibility, licensing and deployment evidence.

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


## Dittofeed

Self-hosted customer engagement and messaging orchestration platform.

- Listing: https://launchinyourcloud.com/directory/dittofeed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: render, railway, 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: Application platform deployment; Docker / Compose
- Architecture: Dittofeed application, PostgreSQL, ClickHouse and supporting services.
- 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://dittofeed.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.

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

Dittofeed application, PostgreSQL, ClickHouse and supporting services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted customer engagement and messaging orchestration platform.

### Deployment boundaries


- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.dittofeed.com/deployment/self-hosted/render.md (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil (render): https://docs.dittofeed.com/deployment/self-hosted/render.md
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/dittofeed-2
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/dittofeed
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes maxgurewitz, chandlercraig, neo773, 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/dittofeed/dittofeed/graphs/contributors

- Upstream project: https://github.com/dittofeed/dittofeed

### Sources

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil: https://docs.dittofeed.com/deployment/self-hosted/render.md

- Railway: https://railway.com/deploy/dittofeed-2

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

- Render Guide: https://docs.dittofeed.com/deployment/self-hosted/render

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

- GitHub Releases: https://github.com/dittofeed/dittofeed/releases

### Licensing sources

- https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE

### Infrastructure sources

- https://docs.dittofeed.com/deployment/self-hosted/render.md

- https://railway.com/deploy/dittofeed-2

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


### 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: Edition-dependent. OIDC-based multi-tenant authentication is documented, but the detailed guide restricts that mode to dittofeed-ee and Dittofeed Cloud. The community lite deployment instead offers a shared-password single-tenant mode. Obtain the Enterprise image/entitlement and configure provider claims and workspace access; anonymous demo mode is unsuitable for production. Scope: Self-hosted Enterprise OIDC versus community/lite authentication; detailed mode restrictions override the general overview. Source: https://docs.dittofeed.com/deployment/self-hosted/auth-modes/multi-tenant.md (reviewed 2026-11-20). Supporting source: Authentication-mode overview — https://docs.dittofeed.com/deployment/self-hosted/auth-modes.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide links the lite Compose stack and documents replacing default credentials, secrets and dashboard URLs. It includes PostgreSQL, ClickHouse and workflow services; the vendor also publishes a Helm chart. Choose a compatible pinned release and configure storage, TLS, authentication and backups; Enterprise uses a separately entitled image. Scope: Vendor community/lite deployment recipe, distinct from Enterprise image delivery. Source: https://docs.dittofeed.com/deployment/self-hosted/docker-compose.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dittofeed/dittofeed/blob/main/docker-compose.lite.yaml. Artifact reference: main (moving branch; pin compatible application and dependency versions). Supporting source: Official Kubernetes/Helm recipe — https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md.

- Minimum footprint / sizing: Documented. The Helm guide lists application-container requests/limits of 1 CPU and 512 MiB RAM and ClickHouse memory requests/limits of 1 GiB. These are component configuration defaults, not a whole-stack minimum: PostgreSQL, Temporal, storage, replicas and traffic need separate capacity. They do not size 100 users, 1 TB or HA. Scope: Documented chart component allocations, not total host or production capacity. Source: https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Typebot

Self-hosted visual conversation and form builder.

- Listing: https://launchinyourcloud.com/directory/typebot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.
- Licensing model: source-available
- Installation: Application platform deployment; Docker / Compose
- Architecture: Typebot builder and viewer, database, object storage and mail configuration.
- 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://typebot.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.

FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.

Typebot builder and viewer, database, object storage and mail configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted visual conversation and form builder.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder (checked 2026-11-19). 

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

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production (checked 2026-11-19). 


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/typebot
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- Railway: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production

- GitHub LICENSE (FSL-1.1-Apache-2.0): https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

- GitHub Releases: https://github.com/baptisteArno/typebot.io/releases

### Licensing sources

- https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production


### 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. Self-hosted builder authentication supports named social providers, Microsoft Entra ID, Keycloak and a custom OIDC provider. Published v3.19.1 code registers these providers with its login/session flow. Configure issuer/callback URLs, trusted identity/email and workspace admission policy; this authenticates editors, not every bot respondent, and does not establish SCIM. Scope: Self-hosted builder/editor login, checked against published v3.19.1 implementation. Source: https://docs.typebot.com/self-hosting/configuration.md (reviewed 2026-11-20). Supporting source: Published provider configuration — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/providers.ts. Supporting source: Published authentication/session wiring — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/nextAuth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide links a Compose stack for separate builder/viewer applications, PostgreSQL and Redis. The v3.19.1 file still selects latest application images and a sample database password; pin compatible images, replace credentials, and configure the encryption secret, login provider, URLs, TLS and optional object storage. Scope: Vendor Docker recipe with versioned source; source-file tag alone does not pin container images. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/baptisteArno/typebot.io/blob/v3.19.1/docker-compose.yml. Artifact reference: v3.19.1 (recipe uses moving latest application image tags).

- Minimum footprint / sizing: Sources checked — unresolved. The Docker guide establishes builder, viewer, database and cache roles, with optional object storage, but does not specify whole-stack production CPU/RAM/storage minima. Size editor sessions, concurrent conversations, uploads and integrations separately; provider tutorial/demo allocations do not validate a 100-user, 1 TB HA deployment. Scope: Current upstream deployment topology; numeric workload and HA sizing remains unconfirmed. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20).

- License pricing: Documented. FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion. Scope: Typebot; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## useSend

Self-hosted email campaign and transactional messaging application.

- Listing: https://launchinyourcloud.com/directory/usesend/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- 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: Application platform deployment; Docker / Compose
- Architecture: useSend application, PostgreSQL, queues and AWS SES/SNS integration.
- 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://useSend.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.

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

useSend application, PostgreSQL, queues and AWS SES/SNS integration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted email campaign and transactional messaging application.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes KMKoushik, harshsbhat, magicspon, 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/usesend/useSend/graphs/contributors

- Upstream project: https://github.com/usesend/useSend

### Sources

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

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

- GitHub Releases: https://github.com/usesend/useSend/releases

### Licensing sources

- https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

### Infrastructure sources

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

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


### 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 self-hosting guide documents GitHub login; published v1.10.4 code also registers Google when configured. The code permits an initial bootstrap account, then requires an existing account or team invitation. Configure provider credentials, trusted email/account linking and callbacks. Email codes, SES credentials and API/SMTP tokens are separate; generic SAML/OIDC federation is not established. Scope: Named external login providers for the self-hosted application, with published account-admission behavior. Source: https://docs.usesend.com/self-hosting/overview.md (reviewed 2026-11-20). Supporting source: Published v1.10.4 provider and account-admission code — https://github.com/usesend/useSend/blob/v1.10.4/apps/web/src/server/auth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official production Docker guide links a Compose stack; the v1.10.4 recipe includes the app, PostgreSQL, Redis and RustFS image storage. Pin the application image instead of latest and configure provider login, secrets, persistent data and TLS. AWS SES/SNS delivery and optional public image URLs require separate configuration; the SMTP proxy is a different service. Scope: Published application stack, distinct from the separate SMTP-server Compose example. Source: https://docs.usesend.com/get-started/set-up-docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/usesend/useSend/blob/v1.10.4/docker/prod/compose.yml. Artifact reference: v1.10.4 (application image tag is latest; pin a compatible deployment version). Supporting source: Official self-hosting dependencies and settings — https://docs.usesend.com/self-hosting/overview.md.

- Minimum footprint / sizing: Sources checked — unresolved. The official guide establishes an app, PostgreSQL, Redis, SES/SNS and optional image-storage topology but no complete production CPU/RAM/storage minimum. Size campaign volume, queue concurrency, email-content retention and storage before selecting instances; 100 internal users and 1 TB alone do not specify delivery throughput or HA capacity. Scope: Current self-hosted topology; whole-system production sizing remains unconfirmed. Source: https://docs.usesend.com/self-hosting/overview.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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






