
# Marketing automation on Railway

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

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

7 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.







## erxes

Customer-operated business and customer engagement platform.

- Listing: https://launchinyourcloud.com/directory/erxes/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Custom source-available application terms with separately licensed Enterprise components.
- Licensing model: source-available
- Installation: Application platform deployment
- Architecture: erxes XOS application services, database, search and supporting microservices 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://erxes.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.

Custom source-available application terms with separately licensed Enterprise components.

erxes XOS application services, database, search and supporting microservices on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Customer-operated business and customer engagement platform.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/erxes
  erxes XOS application services, database, search and supporting microservices on Railway. The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

- GitHub LICENSE.md (AGPL-3.0 + SaaS restriction): https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md

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

### Licensing sources

- https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md

### Infrastructure sources

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


### 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 published 3.4.25 Google-login button has an empty click handler. Its OAuth client/authorization-server features and password or SaaS magic-link flows do not establish a working self-hosted external identity-provider login. Confirm an implemented callback, account/role mapping and edition/version before claiming Google or generic SAML/OIDC SSO. Scope: Published self-hosted core UI; a placeholder or OAuth server is not proof of external user federation. Source: https://github.com/erxes/erxes/blob/3.4.25/frontend/core-ui/src/modules/auth/login/components/GoogleOAuthButton.tsx (reviewed 2026-11-20). Supporting source: Published core authentication mutations — https://github.com/erxes/erxes/blob/3.4.25/backend/core-api/src/modules/auth/graphql/resolvers/mutations.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published 3.4.25 README and installer deploy selected plugins with Docker Compose and offer an explicit --version option. Review and pin the installer/release, domain/TLS, generated secrets and plugin versions; the Linux installer checks x86_64/AVX requirements for its current images and MongoDB. Source development through pnpm is separate. Scope: Published self-hosted installer, distinct from a Railway package or developer checkout. Source: https://github.com/erxes/erxes/blob/3.4.25/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/erxes/erxes/blob/3.4.25/scripts/install.sh. Artifact reference: 3.4.25 (select explicit deployment version; installer otherwise chooses a newer release).

- Minimum footprint / sizing: Sources checked — unresolved. The installer identifies Docker services and plugin-dependent infrastructure but does not supply a complete production CPU/RAM/storage minimum. The local guide's 4096 MiB Node heap troubleshooting option is per process, not host sizing. Confirm plugin counts, MongoDB/Redis, active users, attachments and HA; current Linux image architecture constraints also apply. Scope: Published installer and local-development guidance; whole-stack production sizing remains unconfirmed. Source: https://github.com/erxes/erxes/blob/3.4.25/scripts/install.sh (reviewed 2026-11-20). Supporting source: Local setup and per-process heap guidance — https://erxes.io/docs/local-setup.

- License pricing: Documented. Custom source-available application terms with separately licensed Enterprise components. Scope: erxes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## EspoCRM Self-Hosted

Self-hosted CRM with sales records, customer-service features and email campaign management.

- Listing: https://launchinyourcloud.com/directory/espocrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; commercial extensions use separate restricted terms
- Licensing model: open-source
- Installation: Official Docker, installation script or manual PHP server installation
- Architecture: Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services.
- Operations: Customer maintains application/database containers or servers, scheduled work, email services, backups, upgrades and selected extension compatibility.
- Product website: https://www.espocrm.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The core includes campaign management. The feature matrix places BPM and workflows in Advanced Pack, while sales/inventory functions are in Sales Pack. These paid extensions have separate license terms and should not be assumed to be part of the AGPL core. EspoCRM 10.1.2 fixes OAuth Server access tokens being rejected when 2FA is enabled and an administrator temporarily losing access to scopes after another administrator views that user's record access. Operators using OAuth or 2FA should update.

The downloadable core is GNU AGPL version 3. Advanced Pack and other commercial extensions use a separate license restricting redistribution and limiting installation/use. The directory groups open-source and open-core offerings under one filter.

Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services. EspoCRM 10.1 drops support for MariaDB 10.3–10.5, so upgrades require a supported database version.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, leads and sales opportunities; broader ERP functions are not established for the base application.

- marketing-automation: Segmented campaign email, target lists and campaign tracking; workflow/BPM automation is separately offered in Advanced Pack.

### Deployment boundaries


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


### Cloud deployment evidence

- EspoCRM self-hosted deployment on Railway (railway): https://railway.com/deploy/espocrm
  The community template deploys the official espocrm/espocrm image with PostgreSQL and persistent application files in the customer project. Review the selected release, background job configuration, email and backups. Paid workflow or other commercial extensions are not established by this core application deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release feed publishes EspoCRM 10.1.2 dated November 16, 2026. The vendor documents named Red Cross implementations, including the Armenian Red Cross Society and Slovak Red Cross, with links to institutional sources. Those implementations demonstrate adoption without establishing one common hosting model or extension set.

Reviewed 2026-11-16.

- Current maintained download and release: https://www.espocrm.com/download/

- Named institutional adoption examples: https://www.espocrm.com/blog/nonprofits-espocrm/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Sources

- Self-hosted installation, current release and core license: https://www.espocrm.com/download/

- Core and extension feature boundaries: https://www.espocrm.com/features/

- Campaign configuration and email delivery: https://docs.espocrm.com/user-guide/campaigns/

- Open-source application license: https://www.espocrm.com/espocrm-open-source-license/

- Commercial extension restrictions: https://www.espocrm.com/extension-license-agreement/

- Named nonprofit implementations: https://www.espocrm.com/blog/nonprofits-espocrm/

- Application architecture and database requirements: https://github.com/espocrm/espocrm

- EspoCRM 10.1 compatibility changes: https://www.espocrm.com/blog/espocrm-v10-1-released/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Licensing sources

- https://www.espocrm.com/espocrm-open-source-license/

- https://www.espocrm.com/extension-license-agreement/

- https://www.espocrm.com/features/

### Infrastructure sources

- https://www.espocrm.com/download/

- https://github.com/espocrm/espocrm

- https://www.espocrm.com/blog/espocrm-v10-1-released/


### 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. EspoCRM supports external OpenID Connect providers from version 7.3, with optional user creation and team mapping. Portal OIDC is documented from 7.4. Provider MFA and supported client-authentication methods must be checked separately. Scope: Self-hosted EspoCRM; version-specific OIDC and portal configuration. Source: https://docs.espocrm.com/administration/oidc/ (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 vendor Docker repository distinguishes a production prebuilt image from development builds and includes database, daemon and websocket configuration. Replace example database credentials and retain persistent volumes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/espocrm/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/espocrm/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The server guide specifies supported PHP/database versions and recommends a VPS or dedicated server for production. It does not establish a quantitative whole-host CPU/RAM/storage minimum or an HA profile for the proposed workload. Scope: EspoCRM application, database and scheduled/background work; shared-hosting capability is not a capacity guarantee. Source: https://docs.espocrm.com/administration/server-configuration/ (reviewed 2026-11-20).

- License pricing: Documented. EspoCRM core is distributed under AGPLv3. That licence does not include separately sold extensions, hosting or professional support, and it should not be treated as a quote for those services. Scope: Reviewed open-source core; commercial extensions and services are separate. Source: https://www.espocrm.com/espocrm-open-source-license/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 10.1.2, published 2026-11-16. 10.1.2 adds OAuth/2FA and administrator-scope fixes; check the 10.1 database compatibility requirements before upgrading. This is a dated release snapshot, not a support or future-cadence promise. Scope: Upstream espocrm/espocrm release record; commercial editions and deployment packages may differ. Source: https://github.com/espocrm/espocrm/releases/tag/10.1.2 (reviewed 2026-11-16).







## SendPortal

Self-hosted email marketing, subscriber and campaign management.

- Listing: https://launchinyourcloud.com/directory/sendportal/
- 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: Laravel application, PostgreSQL, Redis, queues and scheduler 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://sendportal.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.

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

Laravel application, PostgreSQL, Redis, queues and scheduler on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted email marketing, subscriber and campaign management.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/sendportal
  Laravel application, PostgreSQL, Redis, queues and scheduler on Railway. An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes JonoB, dljfield, mauricius, 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/mettle/sendportal/graphs/contributors

- Upstream project: https://github.com/mettle/sendportal

### Sources

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

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/mettle/sendportal/master/LICENSE

- GitHub Releases: https://github.com/mettle/sendportal/releases

### Licensing sources

- https://raw.githubusercontent.com/mettle/sendportal/master/LICENSE

### Infrastructure sources

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


### 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 v4.0.0.1 standalone application configures a local session guard and API-token guard. The vendor also permits embedding SendPortal in another Laravel application, but that does not establish a supported SAML/OIDC integration for the standalone product or provider template. Confirm the actual authentication package, callback and user/workspace mapping. Scope: Published standalone authentication versus an integration/customization possibility. Source: https://github.com/mettle/sendportal/blob/v4.0.0.1/config/auth.php (reviewed 2026-11-20). Supporting source: Embedding as a Laravel package — https://sendportal.io/docs/v4/getting-started/package-installation.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v4 guide installs the standalone application from its release branch, runs Composer, then configures its web server and application settings. Embedding it as a Laravel package is a separate path. Pin the v4.0.0.1 application and compatible runtime/dependencies, then configure database, email services, secrets, scheduled tasks and TLS. Scope: Versioned standalone installation; not a complete preconfigured provider image. Source: https://sendportal.io/docs/v4/getting-started/installation (reviewed 2026-11-20). Deployment artifact: https://github.com/mettle/sendportal/tree/v4.0.0.1. Artifact reference: v4.0.0.1.

- Minimum footprint / sizing: Sources checked — unresolved. The v4 installation guide lists PHP, Composer, web-server and database requirements but no numeric whole-stack CPU/RAM/storage minimum. Size campaigns, subscriber volume, queues, delivery rate, retention and redundancy; PHP compatibility and an application package do not establish a 1 TB HA deployment footprint. Scope: Versioned runtime requirements; complete production sizing remains unconfirmed. Source: https://sendportal.io/docs/v4/getting-started/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## SuiteCRM Self-Hosted

Open-source, customer-operated CRM with marketing campaigns and configurable record workflows.

- Listing: https://launchinyourcloud.com/directory/suitecrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 application; separately selected extensions and services have their own terms
- Licensing model: open-source
- Installation: Official prebuilt SuiteCRM 8 package and server installation guide
- Architecture: Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.
- Operations: Customer configures and maintains the web/database stack, scheduled and background work, email transport, backups and software security updates.
- Product website: https://suitecrm.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the downloadable self-hosted CRM. Campaigns and workflow configuration are documented, but external email delivery and optional integrations need their own operational arrangements. Confirm compatibility requirements before upgrading; community extensions are separately scoped.

The downloadable application core is GNU AGPL version 3. Paid hosting, implementation and support do not change the listed core license; review any separate extension licenses.

Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, opportunities, quotes and service processes; this is CRM rather than a complete financial ERP.

- marketing-automation: Targeted email campaigns and configurable workflows around CRM records; campaign delivery requires configured email and background jobs.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/suitecrm (checked 2026-11-12). Source: https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- SuiteCRM 8 community deployment on Railway (railway): https://railway.com/deploy/suitecrm
  The community recipe deploys SuiteCRM 8.10 with PHP/Apache, its scheduler and asynchronous worker, plus MariaDB and persistent application storage. The build downloads the upstream SuiteCRM release. Review current versions, initial administrator credentials, mail integration and backups; this does not include separately licensed extensions or vendor-hosted service.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the SuiteCRM Railway image (railway): https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile
  The inspected image downloads SuiteCRM-Core v8.10.2 from the upstream release repository and uses PHP 8.3. Confirm the compatibility matrix and update the release and database together when maintaining the deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release notes document SuiteCRM 8.10.2 security and maintenance work released July 31, 2026, and credit community contributors. The vendor case study describes Humanetics Innovative Solutions using SuiteCRM for customer visibility, sales workflows and targeted campaigns; the study does not establish the hosting model of every adopter.

Reviewed 2026-11-10.

- Security maintenance and contributor acknowledgements: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Named customer implementation: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Sources

- SuiteCRM 8 installation: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/

- Self-hosting and paid service scope: https://suitecrm.com/pricing/

- Marketing campaigns: https://docs.suitecrm.com/8.x/user/marketing-outreach/campaigns-overview/

- Configurable workflows: https://docs.suitecrm.com/admin/administration-panel/workflow/

- Application license: https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- Current security and maintenance releases: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Humanetics implementation case study: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Licensing sources

- https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- https://suitecrm.com/pricing/

### Infrastructure sources

- https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/


### 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 SuiteCRM 8.7.0+ guide documents SAML configuration and explicitly notes that IdP-initiated logout and POST binding to the logout service are unsupported. Review the stated session-timeout behavior and user mappings. Scope: SuiteCRM 8.7.0+ SAML; logout limitations do not imply login is unsupported. Source: https://docs.suitecrm.com/8.x/admin/configuration/saml/8.7.0-saml-configuration/ (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 SuiteCRM 8 guide documents downloading the prebuilt application package and completing server installation. Configure the compatible PHP/database stack, permissions and scheduled jobs for the selected release. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The SuiteCRM 8 installation and compatibility guides establish supported web/PHP/database combinations and recommend the pre-built installation package for production. They do not establish a quantitative whole-stack resource floor or an HA sizing profile. Scope: SuiteCRM 8 application, database and background processing; PHP limits are not whole-host memory requirements. Source: https://docs.suitecrm.com/8.x/admin/compatibility-matrix/ (reviewed 2026-11-20). Supporting source: Production installation package — https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/.

- License pricing: Documented. The vendor states there are no per-user software licence fees for SuiteCRM. Hosting, setup and support are paid services and must be budgeted separately from the open-source software. Scope: Self-hosted SuiteCRM core; managed hosting and optional services are not included. Source: https://suitecrm.com/pricing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## 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).






