How do we charge clients in our local currency or payment processor?

Bundled Stripe / PayPal / Braintree / Paystack / Razorpay / Offline. Paddle, Mollie, Adyen and others ship as one-class plugins against the Cashier contracts.

What is the operational shape — who runs this?

Typical 10-30 clients: part-time Laravel-fluent engineer + ops-shaped person. 100+ clients: engineer full-time, platform is the agency product.

For agencies & resellers

Run every client's campaigns. Under your own domain. Your own brand.

Q: Does the customer side of the admin look different from the agency side?

Yes — separate URL trees on the same install. /admin/* is the agency view; /dashboard/* is the customer view. Same Laravel app, same MySQL, two route groups with distinct middleware.

Q: What about deliverability across many clients sharing one IP?

Each Customer can be assigned its own SendingServer — separate SES identity, SendGrid sub-account, or Postal route. Reputation stays isolated per client.

AcelleMail's multi-tenant Customer + Plan model is what an agency reseller actually needs: each client account is gated by its own plan, sends through the agency's branded admin domain, and bills through whichever gateway the agency chose. Pay once for the software. Send unlimited volume through any SMTP backend you trust. Earn per-client recurring revenue without paying per-subscriber platform fees.

Buy Extended License — $199 See the developer docs →

What white-label actually means here

Five surfaces every agency wants to brand.

Custom domain

Your install runs on email.your-agency.com, not acelle.someone.io. Customers log in there, build campaigns there, see reports there. The email sender domain (DKIM / SPF / DMARC) is a separate setting per Customer — each end client's transactional mail goes out from their verified domain, not yours.

Branded admin UI

The admin Settings page covers logo, primary colour, login-page layout, and footer copy. Themes are first-class Laravel views in resources/views/refactor/; agencies that need full UI customisation can fork the theme into a plugin and ship a per-client variant — see UI injection.

Per-client plans

Free / Starter / Pro tiers; quota enforcement on contacts, campaigns, and monthly sends; daily caps; allowed feature subsets. Plan upgrades and downgrades flow through the bundled Cashier package or a payment-gateway plugin for regional vendors (Paddle, Razorpay, Paystack, Mollie, etc.).

Multiple sending servers

One sending server per client (or shared pool, your call). Amazon SES with separate IAM identities, SendGrid sub-accounts, custom Postal MTA — each client's campaigns route through the server you assigned, with per-server reputation isolated. New vendors ship as a one-class sending-driver plugin.

Customer self-service

End clients log in to the customer side of the admin and build their own campaigns, lists, automations, A/B tests. The agency admin watches the meta-view: per-client sending volume, plan utilisation, billing status, deliverability metrics. Two completely separate UIs sharing the same database — no hand-built portal required.

Reseller-grade observability

Per-client sending volume, bounce rate, complaint rate, open rate trends, top-domain failures. The admin observability page rolls up across every customer; per-customer drill-down shows the same data scoped to one tenant. Cron-driven daily rollup means the page renders cheaply even with hundreds of clients.

The margin math at agency scale

You charge the client. You pay only for sends. The margin is your software.

An agency with ten clients on a "$99/mo, up to 10,000 contacts, weekly campaign" plan collects $990/mo. The actual underlying cost — Amazon SES at $0.10/1,000 emails — is roughly $40/mo for those ten clients combined. The software cost is amortised once across the lifetime of the install. Per-client gross margin lands in the 90 %+ range from the first client onward, regardless of how many clients you onboard.

Compare to reselling SaaS-priced platforms: Mailchimp's 10,000-contact tier ($135 / client) consumes 60 % of a $99 plan's revenue before you account for support time. The math only works at the small end if your platform fees are zero.

Technical shape an agency cares about

One Laravel install. One MySQL. Many tenants.

AcelleMail is a single Laravel application with a customer table that gates every other table. Queue workers handle send-throughput; Redis caches per-tenant settings; MySQL holds subscribers, lists, campaigns, and tracking logs all keyed by customer_id. Scale-out is the standard Laravel scale-out: horizontal app servers behind a load balancer, a managed MySQL with read replicas for the report queries, queue workers fanned across hosts.

Agencies that want stricter isolation per client (separate database, separate filesystem) can run the same software multiple times — each install is its own tenant boundary. The license covers a single agency's deployment regardless of how many clients are inside it; need a second deployment for a separate brand, that's a second license. License terms →

Agency-specific FAQ

Real questions from agency owners.

Does the customer side of the admin look different from the agency side?

Yes — they are separate URL trees on the same install. /admin/* is the agency / reseller view; /dashboard/* is the customer view that an end client sees after logging in. Same Laravel app, same MySQL, two distinct route groups with distinct middleware. Agencies that want per-client custom branding inside the customer view can ship a UI-injection plugin that swaps the customer-side layout based on the active customer's tenant.

How do we charge clients in our local currency / payment processor?

Bundled gateways cover Stripe, Stripe Subscription, PayPal, Braintree, Paystack, Razorpay, and Offline (manual / wire). Anything else — Paddle, Mollie, Adyen, Square, regional providers — ships as a one-class plugin against the Cashier contracts. Payment gateways — the deep-dive covers Paddle as a worked example with the full contract and the five vendor-boundary discipline rules.

What about deliverability across many clients sharing one IP?

Each Customer can be assigned its own SendingServer record — that means each client's campaigns can route through a separate Amazon SES identity, a separate SendGrid sub-account, a separate Postal route. Reputation stays isolated per-client. The "shared pool" pattern works when clients are well-vetted and small; the "per-client server" pattern is the usual choice when one bad client could hurt the rest. Both are configurable from the admin Sending Servers page; switching is one config-field edit.

Can we resell AcelleMail itself as part of a service offering?

The Extended License grants commercial redistribution. Bundle the install with your service (build campaigns + run sends + provide deliverability consulting), charge clients accordingly, and you own the resulting service business. The license is one-time per deployment; updates are included for life. License grid →

What's the operational shape — who does the agency hire to run this?

A typical agency running AcelleMail at the 10-30 client scale needs a part-time Laravel-fluent engineer to handle hosting, upgrades, and the occasional bespoke plugin. A separate ops-shaped person — bounced-email triage, deliverability monitoring, client onboarding into the right plan — is usually the second hire. At 100+ clients the engineer is full-time and the platform itself is the agency's product. Compare to reselling someone else's SaaS, where the platform's outages become your support tickets without you having any leverage to fix them.

Pay once. Resell unlimited campaigns. Own the email layer your clients run on.

Extended License is $199 — covers commercial redistribution + the plugin SDK + lifetime updates. Try the live demo from the customer side and the admin side before you buy.

Buy Extended License — $199 Try Live Demo