Granular/Per-Server SMTP Allocation & Usage Tracking instead of Global Account-Level Activation
Currently, the SMTP add-on is applied globally across the entire account. However, managing infrastructure across dozens of independent client instances makes this setup quite restrictive.
In my current setup, I run over 40 distinct production environments under a single umbrella account. Because SMTP limits and costs are pooled together at the top level, attributing precise delivery volumes and expenses to specific projects has become a major administrative headache.
It would be significantly more practical to assign SMTP quotas and monitor bandwidth per instance or per sub-account. For example, assigning a strict cap of 15,000 monthly sends to Server A while allowing 80,000 to Server B. This level of granularity would simplify internal billing, give accurate cost breakdown per client, and prevent one rogue server from consuming the shared pool.
Is per-service/per-instance SMTP provisioning on the product roadmap anytime soon?
Ask by https://feedback.cloudways.com/forums/203824-product-improvements-flexible sprunky
cuhn kedrik
shared this idea