
# Marketing automation on AWS

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

Canonical page: https://launchinyourcloud.com/clouds/aws/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: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

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

3 listings.


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






