EDM (sproutsend) — email marketing platform
Context
EDM is Aspire's email-marketing platform (EDM = Electronic Direct Mail). Originally codenamed "sproutsend", fully rebranded to "EDM" in the customer-facing layer 2026-04-26. Lives at edm.goldroom.io.
Architecture
graph LR
EDM["EDM (sproutsend)<br/>edm.goldroom.io"] --> SG["SendGrid (delivery)"]
EDM --> DB[("Postgres<br/>db name: sproutsend")]
classDef app fill:#715EE3,color:#fff,stroke:#291F50;
class EDM app;
Detail
Deployment
- URL:
edm.goldroom.io - Local path:
projects/edm/ - GitLab:
aspire/webapps/edm(project id 213) - Coolify webhook re-wired 2026-05-02 (URL only in Coolify UI, not exposed via API)
Rename note (important for grep/debugging)
- Full
sproutsend → edmrename complete 2026-04-26 - BUT the internal
postgres_dbis still namedsproutsend(intentional — noDATABASE_URLchange needed). Don't "fix" this; it's deliberate to avoid a risky DB migration.
Stack
- Postgres-backed (DB name
sproutsend) - Coolify deploy
- SendGrid for actual email delivery (per the org email standard)
Relationship to other tools
- Sits under the Goldroom brand (
goldroom.iodomain) — Goldroom is the marketing agency - Distinct from SendGrid (the delivery infra) — EDM is the campaign-building UI layer on top
- Distinct from Postiz (social media scheduling) — EDM is email, Postiz is social
Email infrastructure cross-cutting note
Aspire's email standard is SendGrid:
- DKIM CNAMEs must be added, then the in-page "Verify" button clicked manually (auto-verify is unreliable, can sit pending for days — per MEMORY.md
feedback_sendgrid_manual_verify) - Example:
em9332.myalby.com.ausat pending 7 days, resolved instantly on manual click 2026-05-09
Open questions
- EDM vs Postiz boundary — does EDM handle only email, Postiz only social, or is there overlap?
- Should EDM integrate with BizDB (bizdb) for audience targeting?
- Multi-brand sending — one EDM instance for all Aspire brands, or per-brand?
Related
- brand-tokens — EDM is under the Goldroom brand
- bizdb — potential audience-data source
- coolify-multi-server-topology — deploy platform
🔗 Relationships
graph LR
edm_sproutsend["edm-sproutsend"]:::self
edm_sproutsend --> bizdb["bizdb"]
edm_sproutsend --> brand_tokens["brand-tokens"]
edm_sproutsend --> coolify_multi_server_topology["coolify-multi-server-topology"]
classDef self fill:#715EE3,color:#fff,stroke:#291F50;