
# Marketing automation

Campaigns, contact segmentation and marketing workflows.

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


Campaigns, contact segmentation and marketing workflows.

12 listings.


## Apache Unomi

Apache customer-data platform for event profiles, segmentation and personalization.

- Listing: https://launchinyourcloud.com/directory/apache-unomi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Unomi Java services and search datastore in a cloudimg Azure VM.
- 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/apache/unomi
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This entry concerns customer profiles and segmentation; it is not itself a complete campaign delivery or email service.

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

Unomi Java services and search datastore in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Apache customer-data platform for event profiles, segmentation and personalization.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04
  Unomi Java services and search datastore in a cloudimg Azure VM. This entry concerns customer profiles and segmentation; it is not itself a complete campaign delivery or email service.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes sergehuber, jkevan, jsinovassin, 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/apache/unomi/graphs/contributors

- Upstream project: https://github.com/apache/unomi

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/apache/unomi/master/LICENSE

- GitHub Releases: https://github.com/apache/unomi/releases

- GitHub Commits: https://github.com/apache/unomi/commits/master

- Official upstream releases: https://unomi.apache.org/download.html

### Licensing sources

- https://raw.githubusercontent.com/apache/unomi/master/LICENSE

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04


### Buyer diligence


Research coverage: 7/12 fields (58%); 5 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Apache Unomi selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-unomi-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.apache-unomi-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.apache-unomi-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.apache-unomi-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-unomi-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The versioned server guide documents HTTP Basic authentication, Karaf accounts and protected API access. Sending a customer-profile login/identify event from another SSO system does not authenticate an operator to Unomi. A supported external SAML/OIDC operator-login integration and role mapping remain unconfirmed. Scope: Unomi 3.1 headless server/operator authentication, distinct from tracked visitor identity. Source: https://unomi.apache.org/manual/3_1_x/index.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. Apache publishes the Unomi 3.1.0 binary distribution with signatures/checksums. The versioned manual documents Java/Karaf startup and a compatible Elasticsearch service. Use the selected release distribution and verify dependencies; some Docker quickstart snippets still show older image versions and must not be copied as a version-matched production stack. Scope: Current official 3.1.0 server binary; upstream application and third-party Azure image are separate releases. Source: https://unomi.apache.org/download.html (reviewed 2026-11-20). Deployment artifact: https://www.apache.org/dyn/closer.lua/unomi/3.1.0/unomi-3.1.0-bin.tar.gz. Artifact reference: 3.1.0 official binary distribution; verify Apache signature and SHA512. Supporting source: Versioned 3.1 installation and operations manual — https://unomi.apache.org/manual/3_1_x/index.html.

- Minimum footprint / sizing: Sources checked — unresolved. The 3.1 manual establishes Java/Karaf and Elasticsearch dependencies, clustering and heap tuning but no whole-stack CPU/RAM/storage minimum for this workload. A JVM heap example is not physical server capacity; size profile/event throughput, retention, search storage and redundancy separately. Scope: Unomi 3.1 application/search topology; workload-specific production sizing remains unconfirmed. Source: https://unomi.apache.org/manual/3_1_x/index.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The official Apache download page identifies Unomi 3.1.0, released 2026-11-19. This updates the earlier 3.0.1 snapshot. The server and JavaScript tracker have separate releases; confirm the third-party Azure image version independently. This does not establish support duration or a future cadence. Scope: Official upstream server release, distinct from tracker and provider-image versions. Source: https://unomi.apache.org/download.html (reviewed 2026-11-20).







## BillionMail

Customer-operated mail server and marketing application.

- Listing: https://launchinyourcloud.com/directory/billionmail/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- 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: VM image
- Architecture: BillionMail container services and persistent mail data in a cloudimg Azure VM.
- 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://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Operating a mail server also requires DNS, reverse DNS, deliverability and provider port approval; a VM image does not guarantee inbox placement.

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

BillionMail container services and persistent mail data in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Customer-operated mail server and marketing application.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04
  BillionMail container services and persistent mail data in a cloudimg Azure VM. Operating a mail server also requires DNS, reverse DNS, deliverability and provider port approval; a VM image does not guarantee inbox placement.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lotkmm, aaPanel, dreambladeflag, 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/Billionmail/BillionMail/graphs/contributors

- Upstream project: https://github.com/Billionmail/BillionMail

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/aaPanel/BillionMail/main/LICENSE

- GitHub Commits: https://github.com/aaPanel/BillionMail/commits/main

### Licensing sources

- https://raw.githubusercontent.com/aaPanel/BillionMail/main/LICENSE

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: BillionMail selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.billionmail-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.billionmail-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.billionmail-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.billionmail-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.billionmail-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed v4.9 dashboard authentication code documents application login and tokens, without establishing an external SAML/OIDC identity-provider integration. Dovecot mail-authentication backends and SMTP/IMAP accounts are separate from administrator SSO. Confirm a supported dashboard integration and account/role mapping. Scope: Published management-dashboard authentication; mail protocol identities are separate. Source: https://github.com/Billionmail/BillionMail/blob/v4.9/core/api/rbac/v1/auth.go (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 project supplies an installation script and Docker Compose recipe; the v4.9 README explains script/Compose setup, domain verification and DNS. Review and pin the selected source/images, secrets and persistent data. Configure mail ports, delivery/relay policy, reverse DNS and TLS; this is a mail-server deployment as well as an application. Scope: Published upstream deployment recipe; distinct from the third-party Azure image. Source: https://github.com/Billionmail/BillionMail/blob/v4.9/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/Billionmail/BillionMail/blob/v4.9/docker-compose.yml. Artifact reference: v4.9. Supporting source: Official preparation and mail-port guidance — https://www.billionmail.com/start/preparation.html.

- Minimum footprint / sizing: Documented. The official quickstart lists a minimum of 1 CPU core, 1 GB RAM and 20 GB disk on a compatible Linux host. That startup baseline does not size 1 TB of retained data, concurrent campaigns or HA; include database, mail queues, mailbox/attachment growth, backups and replica capacity separately. Scope: Vendor-published installation minimum; not a throughput benchmark or HA sizing guarantee. Source: https://www.billionmail.com/start/preparation.html (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: BillionMail; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/aaPanel/BillionMail/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







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







## MailWizz

Commercial self-hosted email marketing application.

- Listing: https://launchinyourcloud.com/directory/mailwizz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS.
- 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.mailwizz.com/integrations/vps-providers/amazon-aws/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Commercial self-hosted email marketing application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/amazon-aws/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/digitalocean/ (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.mailwizz.com/integrations/vps-providers/linode/ (checked 2026-11-19). 


### Cloud deployment evidence

- MailWizz AWS (aws): https://www.mailwizz.com/integrations/vps-providers/amazon-aws/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- MailWizz DO (digitalocean): https://www.mailwizz.com/integrations/vps-providers/digitalocean/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- MailWizz Linode (linode): https://www.mailwizz.com/integrations/vps-providers/linode/
  PHP application, MySQL or MariaDB, web server and scheduled jobs on a customer VPS. The vendor names and describes application installation on AWS, DigitalOcean and Linode. Older VPS price/free-tier examples and delivery credits are not current pricing evidence.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- MailWizz AWS: https://www.mailwizz.com/integrations/vps-providers/amazon-aws/

- MailWizz DO: https://www.mailwizz.com/integrations/vps-providers/digitalocean/

- MailWizz Linode: https://www.mailwizz.com/integrations/vps-providers/linode/

- MailWizz License: https://www.mailwizz.com/legal/regular-license/

- MailWizz Blog: https://www.mailwizz.com/blog/

### Licensing sources

- https://www.mailwizz.com/legal/regular-license/

### Infrastructure sources

- https://www.mailwizz.com/integrations/vps-providers/amazon-aws/

- https://www.mailwizz.com/integrations/vps-providers/digitalocean/

- https://www.mailwizz.com/integrations/vps-providers/linode/


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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. A vendor staff reply suggests developing an OpenID Connect integration or using a third-party SSO provider, rather than documenting a shipped integration. The current public material reviewed does not establish a version-matched SAML/OIDC login setup, entitlement or user/role mapping for MailWizz. Keep this as an integration question. Scope: Vendor staff discussion dated 2023-12-12; not proof of current built-in SSO. Source: https://forum.mailwizz.com/threads/single-sign-on-sso-to-mailwizz.8853/ (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 install guide deploys the licensed application archive to a PHP web host and completes its web installer, then removes the install directory. Configure database, secrets, cron jobs and delivery/bounce services. The application archive is a licensed artifact, not a public Terraform/Helm bundle; select a supported release through the vendor channel. Scope: Commercial application-package installation; no public versioned IaC bundle established. Source: https://www.mailwizz.com/kb/install-steps/ (reviewed 2026-11-20). Supporting source: Application and mail-processing setup — https://www.mailwizz.com/kb/getting-started-steps/.

- Minimum footprint / sizing: Sources checked — unresolved. The vendor lists Linux, PHP, a web server, MySQL/MariaDB and OS cron access, recommending a properly configured VPS. It does not specify a numeric whole-stack CPU/RAM/storage minimum. Confirm campaign/send rate, subscribers, delivery services, database growth and redundancy before estimating the requested HA workload. Scope: Current vendor runtime guidance; workload-specific host sizing remains unconfirmed. Source: https://www.mailwizz.com/faq/what-kind-of-hosting-do-i-need/ (reviewed 2026-11-20).

- License pricing: Documented. MailWizz offers proprietary Regular and Extended licences, each for one installation; the vendor requires Extended for a paid SaaS email-marketing service. Additional installations need separate licences. Confirm the applicable agreement, support/update term and HA/staging entitlements; hosting and message-delivery charges are separate, and no current numeric licence quote is recorded here. Scope: Current commercial licence units and use restrictions, refining the earlier generic software-terms fact. Source: https://www.mailwizz.com/kb/what-license-do-i-need/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Mautic Self-Hosted

Self-hosted marketing automation for email campaigns, lead nurturing, forms and landing pages.

- Listing: https://launchinyourcloud.com/directory/mautic/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3-or-later core; separately selected integrations, hosting and support may carry their own terms
- Licensing model: open-source
- Installation: Production package or Composer installation on a PHP web server
- Architecture: Customer-operated PHP application, database and scheduled background jobs
- Operations: Customer manages the web/database servers, scheduled jobs, updates, backups and email-delivery integration.
- Product website: https://mautic.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Install the production package or documented Composer distribution rather than the GitHub development checkout. Email marketing still requires configured delivery infrastructure or an external provider. Self-hosting does not by itself establish privacy compliance, consent or deliverability.

The listed self-hosted Mautic core is GPLv3-or-later. External delivery services, managed hosting, implementation and support can be paid without changing the core software licensing model; separately installed components retain their own terms.

The installation requires a persistent web server, supported database server and configured email transport; scheduled cron processing handles queued activity.


### Category fit

- marketing-automation: Email campaigns, forms, landing pages, lead nurturing and marketing automation; delivery services and consent processes remain the operator's responsibility.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html (checked 2026-11-12). 


### Cloud deployment evidence

- Mautic production and staging instances on AWS EC2 (aws, digitalocean, linode): https://kb.mautic.org/article/how-to-set-up-a-staging-server-to-test-new-mautic-releases.html
  The official project guide names AWS, DigitalOcean and Linode as hosts of the Mautic production application, then describes cloning that application to staging; the worked snapshot examples use EC2 and a DigitalOcean Droplet. This is a project hosting compatibility statement rather than a storage integration. Follow current Mautic, PHP/database and production security requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production installation: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html

- Marketing automation capabilities: https://mautic.org/features/

- Core license: https://raw.githubusercontent.com/mautic/mautic/7.x/LICENSE.txt

### Licensing sources

- https://raw.githubusercontent.com/mautic/mautic/7.x/LICENSE.txt

- https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html

### Infrastructure sources

- https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html


### 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 versioned Mautic 7 guide documents SAML login and login-time user creation. Configure provider metadata, claim mappings and a restricted default role; this is not evidence of SCIM lifecycle provisioning. Scope: Mautic 7 SAML integration. Source: https://docs.mautic.org/en/7.0/authentication/authentication.html (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 Mautic 7 guide documents a production release package or Composer installation. Configure the supported PHP/database stack, writable directories and scheduled tasks; uploading a package alone does not complete operations. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The versioned installation guide checks PHP/database compatibility, disk space and PHP resource limits, but does not establish a complete production CPU/RAM/storage baseline. PHP memory_limit is a process allowance, not whole-server capacity; size contacts, campaign traffic, queues, database growth and HA separately. Scope: Versioned Mautic 7 installation checks; whole-stack sizing remains unconfirmed. Source: https://docs.mautic.org/en/7.0/getting_started/how_to_install_mautic.html (reviewed 2026-11-20).

- License pricing: Documented. Mautic core is available under GPLv3 without a core subscription fee. Hosting, delivery providers, third-party plugins, professional support and any extended-support service have their own charges and terms; the source licence does not include those services. Scope: Published Mautic 7.2.2 core licence; not a hosted-service or operating-cost price. Source: https://github.com/mautic/mautic/blob/7.2.2/LICENSE.txt (reviewed 2026-11-20). Supporting source: Official ways to run Mautic — https://mautic.org/getting-started/.

- Operating cost estimate: Not researched.

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







## phpList

Customer-operated mailing list and email campaign manager.

- Listing: https://launchinyourcloud.com/directory/phplist/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- 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: VM image
- Architecture: TurnKey Debian appliance with phpList, database 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://www.phplist.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

TurnKey 19.0.3 is a packaging version. Release candidates such as phpList 3.7.0-RC5 must not be labelled stable; delivery limits and infrastructure costs remain separate.

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

TurnKey Debian appliance with phpList, database and mail configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Customer-operated mailing list and email campaign manager.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza
  TurnKey Debian appliance with phpList, database and mail configuration. TurnKey 19.0.3 is a packaging version. Release candidates such as phpList 3.7.0-RC5 must not be labelled stable; delivery limits and infrastructure costs remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes michield, bramley, xh3n1, 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/phpList/phplist3/graphs/contributors

- Upstream project: https://github.com/phpList/phplist3

### Sources

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza

- GitHub COPYING (AGPL-3.0): https://raw.githubusercontent.com/phpList/phplist3/main/COPYING

- GitHub Releases: https://github.com/phpList/phplist3/releases

### Licensing sources

- https://raw.githubusercontent.com/phpList/phplist3/main/COPYING

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: phpList selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza (reviewed 2026-11-19). Offer prodview-xyvhxrbphruza: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-xyvhxrbphruza.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official 3.7.0 announcement adds SAML authentication for administrator login. Use that release or a verified later package and configure the IdP, account mapping and access policy; this is not established for the earlier 3.6.17 snapshot or every marketplace image. Subscriber identity and community-forum login are separate. Scope: Upstream 3.7.0 administrator SAML capability; packaged-version compatibility must be checked. Source: https://www.phplist.org/newslist/phplist-3-7-0-release-notes/ (reviewed 2026-11-20). Supporting source: Current official 3.7.0 download and release date — https://www.phplist.org/download-phplist/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official guide installs a phpList release archive on a PHP/database web host, configures the database in config.php, then completes web setup and scheduled processing. The current download page selects 3.7.0 and links archive/Docker distribution channels. Pin the chosen package and configure delivery credentials, cron, TLS and backups; provider images are separately versioned. Scope: Official manual installation and current distribution channels. Source: https://www.phplist.org/manual/books/phplist-manual/page/installing-phplist-manually (reviewed 2026-11-20). Deployment artifact: https://www.phplist.org/download-phplist/. Artifact reference: 3.7.0 at the reviewed download page (moving distribution landing page).

- Minimum footprint / sizing: Sources checked — unresolved. The official requirements list PHP/extensions, a web server and database but do not establish numeric whole-host CPU/RAM/storage for this workload. Subscriber count, campaign frequency, send rate, bounce handling and retention determine sizing; delivery-service limits and HA need a separate plan. Scope: Upstream application dependencies; complete production sizing remains unconfirmed. Source: https://resources.phplist.com/system/start (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: phpList; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/phpList/phplist3/main/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The official download page identifies phpList 3.7.0, released 2026-08-10; the announcement describes administrator SAML and security changes. This supersedes the earlier GitHub-only 3.6.17 snapshot. Verify the provider image/application version separately; this is not a future cadence or support-duration promise. Scope: Official upstream phpList distribution, distinct from independently packaged images. Source: https://www.phplist.org/download-phplist/ (reviewed 2026-11-20). Supporting source: Official 3.7.0 release announcement — https://www.phplist.org/newslist/phplist-3-7-0-release-notes/.







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






