---
title: Deploy Listmonk with AI on Blossom
url: "/deploy/listmonk/"
canonical_url: https://docs.blossom88.com/deploy/listmonk/
markdown_url: https://docs.blossom88.com/deploy/listmonk.md
summary: Deploy Listmonk with AI on Blossom. Manage newsletter subscribers and campaigns
  with managed PostgreSQL and S3-compatible media storage.
categories:
- deployment
- marketing
---

# Deploy Listmonk with AI on Blossom

[Listmonk](https://listmonk.app/) manages email newsletters, subscriber lists,
and campaigns. You write the message, choose a list, and send through your
SMTP provider.

It uses Go with a Vue interface and PostgreSQL for subscribers, campaigns,
and settings. Browse the [source on GitHub](https://github.com/knadh/listmonk).

This setup runs on regular App Capacity with managed PostgreSQL and newsletter
images in your S3-compatible bucket, such as Cloudflare R2.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent

> **Ask your AI agent:** Deploy Listmonk on Blossom with managed Postgres and R2 for newsletter images. Help me send a test newsletter.

> Follow this guide: https://docs.blossom88.com/deploy/listmonk/



Your agent checks the current
[deployment requirements](https://listmonk.app/docs/installation/), chooses a
maintained release, and saves the setup. Supply your SMTP credentials and
bucket access through a private file.

| Part | Purpose |
|---|---|
| Listmonk Service | Newsletter dashboard and campaign sender |
| Managed PostgreSQL | Subscribers, campaigns, settings, and accounts |
| Your S3-compatible bucket | Newsletter images |
| Your SMTP provider | Delivers email |

Keep administration behind **Blossom Account access** and require native
Listmonk sign-in. Allow the subscriber-facing subscription, unsubscribe, and
tracking routes through Blossom's access policy. Your agent can use
[Listmonk's route reference](https://listmonk.app/docs/configuration/#http-routes)
to keep administrative APIs private.

## Send a Test Newsletter

> **Ask your AI agent:** Create a sample list, import my test subscribers, and help me check a newsletter before sending it.

> Follow this guide: https://docs.blossom88.com/deploy/listmonk/



Use addresses you control. Upload an image, preview the message, and check its
unsubscribe link. Newsletter images need a stable delivery URL that recipients
can open without signing into Blossom. Use a bucket or public media domain
intended for those images; keep private documents elsewhere.

![Listmonk showing a completed sample newsletter campaign.](/assets/images/guides/listmonk/campaign.png)

For real delivery, configure your provider's verified sender, SPF, DKIM, and
bounce handling. Our deployment test used an internal SMTP capture service;
it verified message generation and receipt, rather than inbox deliverability.

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Create a prebuilt-image Environment, then create and link PostgreSQL:

    blossom app:create --data app.yml
    blossom environment:create --data environment.yml
    blossom database_instance:create --data postgres.yml --follow
    blossom environment_link:create --data database-link.yml
    blossom env_var:push --environment environment-100 --file .env.production
    blossom service:create --data listmonk-service.yml
    blossom environment:deploy --id environment-100 --follow

Map the linked database connection to Listmonk's database settings, preserving
its case-sensitive `LISTMONK_db__*` variable names. Use the private endpoint's
connection settings. Listen on `0.0.0.0:9000` and run with `--config ''` when
configuration comes from environment variables.

Run the selected release's idempotent install/upgrade commands in a **Release
Phase Hook**. Create a strong owner password privately, then configure the
public root URL, SMTP, and media storage in Listmonk's settings.

For R2, set the S3 API endpoint and region, bucket-scoped credentials, and a
public media delivery URL. Use the S3 provider's private bucket mode to avoid
sending an unsupported `public-read` object ACL; the separate media delivery
URL controls how recipients view the images.

For a stop-before-start update, wait for each command to finish:

    blossom service:scale --id service-100 --desired-size 0 --follow
    blossom environment:deploy --id environment-100 --follow
    blossom service:scale --id service-100 --desired-size 1 --follow

</details>

## Keep Your Newsletter Through Updates

> **Ask your AI agent:** Update Listmonk after my campaigns finish. Check that subscribers, campaign history, settings, and images remain.

> Follow this guide: https://docs.blossom88.com/deploy/listmonk/



Keep one active Listmonk campaign runner. Finish or pause campaigns and prevent
scheduled sends during an update; don't add replicas merely because media is
in R2. Use a stop-before-start update: scale the web Service to zero, wait for it to
stop, deploy the saved update, then scale back to one. This has a short outage.
Keep PostgreSQL and the bucket, then check the saved campaign and its image.

## What You Get

- A private newsletter dashboard
- Subscribers and campaign history in managed PostgreSQL
- Newsletter images delivered from your bucket
- Public subscription and unsubscribe pages
