White-label / Agency Mode (Custom Branding, CSS, Domains, Tracking)

[julianwitzel]

Feature Request: White-label / Agency Mode

Hi Plunk team 👋

First of all, great product – we’re currently using self-hosted Plunk and are very happy with it.

We’d like to propose a White-label / Agency Mode feature that would make Plunk significantly more attractive for agencies and service providers who operate Plunk for multiple customers or as part of their own platform.

---

Problem / Motivation

When using Plunk as an agency or embedded email infrastructure, it’s currently hard to:

• Present Plunk as part of our own branded service
• Offer a fully white-labeled experience to end customers
• Avoid exposing the “Plunk” brand in UI, DNS, tracking, or emails

Other tools in this space (e.g. Listmonk) already provide partial solutions for this, especially around UI customization.

---

Proposed Features

1. Custom Branding (UI)

• Replace Plunk logo with a custom logo
• Custom product / app name
• Optional “Powered by Plunk” toggle (on/off)

---

2. Custom CSS (Backend & Frontend)

• Ability to inject custom CSS for:
  • Admin dashboard
  • Public-facing pages (unsubscribe, preference center, etc.)
• Similar approach to Listmonk’s custom CSS support

---

3. Custom Domains (Email & Infrastructure)

• Support for custom TXT / MX / DKIM / SPF records under an agency or customer domain
• Avoid references to plunk in DNS or email headers
• Enables full white-label deliverability setup

---

4. Custom Tracking Domain

• Built-in support for configuring a custom tracking domain
  • Open tracking
  • Click tracking
• Ideally configurable inside Plunk
• Currently achievable via AWS + CloudFront, but native support would be much cleaner

---

5. Multi-Tenant / Agency Use Case (Optional / Future)

• One Plunk instance serving:
  • Multiple customers
  • Each with its own branding, domains, and tracking configuration
• Even a lightweight version would unlock many agency use cases

---

Why This Matters

• Makes Plunk a strong alternative for agencies building custom email infrastructure
• Increases adoption of self-hosted Plunk
• Reduces the need for custom forks or unsupported workarounds
• Opens up new commercial opportunities (agency plans, paid add-ons, etc.)

---

Willing to Contribute

If this aligns with the project direction, I’d be happy to:

• Help refine requirements
• Test early implementations
• Contribute documentation or code where possible

Thanks for considering this 🙌