Categories
Need a custom hosting configuration?
Now it’s easy (and insanely affordable)
to get help from an expert. Whatever you
need, our pros can handle it for you so
you can focus more on what matters …
growing your business.
Platforms
You dream it — we code it. Tap into 10+ years of Blesta, WHMCS & Paymenter development.
WordPress plugins are coming soon
WordPress add-ons are on the roadmap. Tell us what you need.
From custom embedded firmware to cloud
platforms and mobile apps — we design
and build complete IoT solutions
tailored to your needs.
Turn one AWS account into a resellable email service. Each client gets an isolated SES tenant with its own sending domains, SMTP and API credentials, templates, and suppression list. The suite counts every email, pauses a runaway sender, and bills the overage on the next invoice.
Provision SES tenants, verify domains, and bill usage from Blesta — no per-client work in the AWS console.
Every service gets its own SES tenant, configuration set, and IAM user. The IAM policy binds the user to its tenant, so one client can never send as another. Suspension disables the tenant and the key; cancellation removes everything the module created.
Clients add a sending domain, copy the DKIM, MAIL FROM, and DMARC records, and check the status. The Credentials tab shows the SMTP host, username, password, and required headers, with one-click key rotation and a test email.
Each package sets an included monthly volume and one overage price per 1,000 emails. Usage is counted every five minutes with CloudWatch or SQS. The overage line lands on the next invoice at month end, or on an early invoice at the package threshold.
A monthly volume cap and a burst rate cap protect you from a leaked key or a broken script. The plugin pauses the tenant in SES, emails the client and your staff, and shows the service on the staff dashboard. Staff reinstate with one click.
Clients create, preview, and delete SES templates for API sends and manage the suppression list of their tenant. Bounce and complaint rates appear on the Usage tab, and a package-level reputation policy tells SES how to react to a poor reputation.
A Tools page lists every service with sent, included, overage, and billed counts. Health checks alert your staff about a stale collector, low account quota headroom, or a count that drifts after billing. A connection test on the AWS account shows the live SES quota.
Blesta on PHP 8.1 or newer with the Blesta cron active, an AWS account with SES production access in the region you sell, and one IAM user for Blesta with the policy from the administrator guide. The suite ships as a module and a plugin; install both.
Yes, for testing. In the sandbox, SES sends only to verified addresses. Request production access from AWS before you sell to clients. The connection test on the AWS account row shows the sandbox or production state and the 24-hour quota.
Each package sets an included monthly volume and one overage price per 1,000 emails in the package pricing currency. The plugin counts the sent volume of each tenant and adds the overage line to the next invoice of the service at month end. When the unbilled overage reaches the package threshold, it creates an early invoice.
Two safety caps per package: a monthly volume cap and a burst rate cap in emails per second. When a client exceeds either cap, the plugin pauses the tenant in SES within five minutes, emails the client and your staff, and shows the service on the staff dashboard. A staff member reinstates it with one click.
SES requires a DMARC record for tenant sending, and mailbox providers rank mail with DKIM and DMARC higher. The Domains tab shows the exact records to publish and marks the domain ready only when DKIM is verified and the DMARC record exists.
Through SMTP with the credentials from the Credentials tab, or through the SES API with the access key. Every message carries the tenant and configuration set headers shown on that tab. API clients pass the same values as TenantName and ConfigurationSetName.
AWS charges about USD 0.30 per month for each CloudWatch metric, so one per tenant. The SQS collector has no fixed cost and counts the same events. You choose the collector per AWS account and can migrate between them later; the plugin handles the cutover.
The module removes the tenant, the configuration set, the IAM user, and the domain identities it created. Identities that existed in your account before, or that another service still uses, are only disassociated and never deleted.
United States [$]
United Kingdom [£]
Canada[$]
Greece[€]